[wplug] runlevel question
William Powell
billpwl1 at attbi.com
Tue Jan 7 16:15:22 EST 2003
Well, as I understand runlevels, the only time a run level would change
is if you use run-level 3 with only a command line log-in screen for
each user. The user would use "startx" if they wanted to work in the
the GUI of their choice. Each user starting the X-Server in this
fashion will not switch run-levels.
If the system however starts in Run-level 5, there will be a graphical
login determined by the xdm (display manager) that the system is using
and the runlevel will not change as users log in and out.
So, if your "?talkd" is started as part of one of the init scripts,
unless a user specifically changes the run-level, which should not be
neccesary, it should continue to run without problems.
Bill
Doug Green wrote:
>I'm not sure that I know how to monitor a process while switching
>runlevels in this case. Let me be more specific- I want to run
>netatalk/atalkd, which (according to the docs) does NOT like to restart.
>In short, I need keep it running and avoid it from restarting despite
>switching runlevels as users log in/out of the machine. I guess I should
>keep it starting in runlevel 3 then?? Thanks,
>Doug
>
>
>On Tue, 2003-01-07 at 14:44, Alexandros Papadopoulos wrote:
>
>
>>-----BEGIN PGP SIGNED MESSAGE-----
>>Hash: SHA1
>>
>>On Tuesday 07 January 2003 14:27, Doug Green wrote:
>>
>>
>>>Hi all-
>>>I am using RH8.0, and there is a very nice tool to edit what services
>>>are associated with a given runlevel. My question is simple: if I set
>>>a service for runlevel 3 does that mean it is present in runlevel 5
>>>as well, or is it shutdown when the system enters a different
>>>runlevel? It makes sense that runlevel 5 processes will shut down in
>>>the transition to runlevel 3, but I don't know about the reverse.
>>>
>>>
>>All runlevels have start and stop scripts, so leaving runlevel 5 should
>>stop its runlevel-specific services (like xdm, obviously). But why
>>don't you just try it?
>>
>>Activate something like xinetd for a given runlevel, and then switch
>>back and forth, monitoring the process status as you go along. Pretty
>>simple to establish what's happening. Hey, this is UNIX :-)
>>
>>- -A
>>- --
>>http://andrew.cmu.edu/~apapadop/pub_key.asc
>>3DAD 8435 DB52 F17B 640F D78C 8260 0CC1 0B75 8265
>>-----BEGIN PGP SIGNATURE-----
>>Version: GnuPG v1.2.1 (GNU/Linux)
>>
>>iD8DBQE+Gy4tgmAMwQt1gmURAuQUAJ9cSyb8N3FT8l71N/o+yFB42mphgACeO8sY
>>FKMalzFSxrj0tpZerfPZr+0=
>>=cVwX
>>-----END PGP SIGNATURE-----
>>
>>_______________________________________________
>>wplug mailing list
>>wplug at wplug.org
>>http://www.wplug.org/mailman/listinfo/wplug
>>
>>
More information about the wplug
mailing list