Mike - EMAIL IGNORED wrote:
> On Tue, 07 Aug 2007 16:27:20 -0500, Mikkel L. Ellertson wrote:
> [...]
>
>> For example, random.init has these three lines:
>> # chkconfig: 2345 20 80
>> # description: Saves and restores system entropy pool for \
>> # higher quality random number generation.
>> This says that the random script should be started in levels
>> 2, 3, 4, and 5, that its start priority should be 20, and
>> that its stop priority should be 80. You should be able to
>> figure out what the description says; the \ causes the line
>> to be continued. The extra space in front of the line is
>> ignored.
>>
>> Mikkel
> [...]
>
> Yes, but what about my original problem? How can a process
> tell when the system has begun to shut down down?
>
Sorry about getting sidetracked. Because the K01<name> link is being
created, the next thing is to be sure that the initscript does a
proper kill command. If you created the initscript yourself, you may
want to read the sysvinitfiles documentation I pointed out. It
describes the functions in /etc/init.d/functions that can be sourced
by your script and used for things like killing the process.
killproc program [signal]
Sends a signal to the program; by default it sends a SIGTERM,
and if the process doesn't die, it sends a SIGKILL a few
seconds later.
It also tries to remove the pidfile, if it finds one.
Without seeing your script, it is hard to say what is going on.
> BTW, in looking around, I found:
>
> [root@mbrc32]# runlevel
> N 3
>
> Now this surprises me; it was run from a KDE Shell Konsole.
> While I start my system at level 3, I then type startx.
> I thought that the GUI runs at level 5. Am I wrong about
> this?
>
The run lever is the run lever you boot in. You are starting in run
level 3. When you run startx, you start the X server, but you do not
change the run level. With run level 5, you get a GUI login on VT7,
as well as the CLI logins on VT1 through VT76. (By default - this is
configurable.) The use of run level 5 for GUI logins, and run level
3 for CLI logins in an accepted convention, but it can be changed.
If you are interested, you can run "man init" for a better
description of runlevels.
From your questions, I suspect that you do not really understand how
the init scripts and run levels work. So I suspect that your problem
is that your script in not sending a kill signal to your process, so
it is not killed until the cleanup the kills all running processes.
You should probably read the documentation I pointed you to, or post
your init script and let us try and fix it. At this point, we do not
have enough information to properly solve your problem. I think you
have a more basic problem then when the init script is run with the
stop command.
Mikkel
--
Do not meddle in the affairs of dragons,
for thou art crunchy and taste good with Ketchup!
Attachment:
signature.asc
Description: OpenPGP digital signature
-- fedora-list mailing list fedora-list@xxxxxxxxxx To unsubscribe: https://www.redhat.com/mailman/listinfo/fedora-list
