[opensuse] halt / reboot waiting time
I have a "small" problem, when the system goes for shutdown or reboot, the waiting time is too short for a process. I run a VMware on the system, it can take up to 7-10 minutes to shut down all VMs properly, and the system is too eager to shut down. So, before VMware has finished its shutdown properly, SUSE kills the processes which results in heavily screwed up disks in the VMs. How can I extend the waiting time for shutdown/reboot so that VMware can exit properly? -- Anders Norrbring Norrbring Consulting
Anders Norrbring wrote:
I have a "small" problem, when the system goes for shutdown or reboot, the waiting time is too short for a process.
I run a VMware on the system, it can take up to 7-10 minutes to shut down all VMs properly, and the system is too eager to shut down. So, before VMware has finished its shutdown properly, SUSE kills the processes which results in heavily screwed up disks in the VMs.
How can I extend the waiting time for shutdown/reboot so that VMware can exit properly?
man shutdown: -t sec Tell init(8) to wait sec seconds between sending processes the warning and the kill signal, before changing to another runlevel. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
Thomas Hertweck skrev:
Anders Norrbring wrote:
I have a "small" problem, when the system goes for shutdown or reboot, the waiting time is too short for a process.
I run a VMware on the system, it can take up to 7-10 minutes to shut down all VMs properly, and the system is too eager to shut down. So, before VMware has finished its shutdown properly, SUSE kills the processes which results in heavily screwed up disks in the VMs.
How can I extend the waiting time for shutdown/reboot so that VMware can exit properly?
man shutdown:
-t sec Tell init(8) to wait sec seconds between sending processes the warning and the kill signal, before changing to another runlevel.
Well.. Not really. I want the scripts to actually WAIT until VMware has exited. The -t option to shutdown is used to set the time the system waits from sending the shutdown message to screen until it starts the shutdown process. I need to set the waiting time IN the script for a process to end. VMware simply takes too long for the script to wait, it thinks that VMware is stuck, and kills it instead of waiting for it to end. -- Anders Norrbring Norrbring Consulting
Anders Norrbring wrote:
[...] Well.. Not really. I want the scripts to actually WAIT until VMware has exited. The -t option to shutdown is used to set the time the system waits from sending the shutdown message to screen until it starts the shutdown process.
No. It should be the time between sending a SIGTERM and a SIGKILL signal. The time when to start the shutdown process is given as a shutdown argument, not an option. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
Thomas Hertweck skrev:
Anders Norrbring wrote:
[...] Well.. Not really. I want the scripts to actually WAIT until VMware has exited. The -t option to shutdown is used to set the time the system waits from sending the shutdown message to screen until it starts the shutdown process.
No. It should be the time between sending a SIGTERM and a SIGKILL signal.
The time when to start the shutdown process is given as a shutdown argument, not an option.
My mistake, sorry. Anyway, what's the default time? I can't see any option to find out.. -- Anders Norrbring Norrbring Consulting
Anders Norrbring wrote:
No. It should be the time between sending a SIGTERM and a SIGKILL signal.
can't you make a script sending a SIGTERM to all vmware sessions before invoking shutdown (with a "wait" between? jdd -- http://www.dodin.net Lucien Dodin, inventeur http://lucien.dodin.net/index.shtml -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
jdd skrev:
Anders Norrbring wrote:
No. It should be the time between sending a SIGTERM and a SIGKILL signal.
can't you make a script sending a SIGTERM to all vmware sessions before invoking shutdown (with a "wait" between?
jdd
I'm actually thinking about it... However, I'm not sure how the UPS software will handle that. Of course, I can rename the "halt", "reboot" and "shutdown", then add new scripts and links. I'm looking in /etc/init.d/rc as well to see if I can find something out from there.. -- Anders Norrbring Norrbring Consulting
Anders Norrbring skrev:
jdd skrev:
Anders Norrbring wrote:
No. It should be the time between sending a SIGTERM and a SIGKILL signal.
can't you make a script sending a SIGTERM to all vmware sessions before invoking shutdown (with a "wait" between?
jdd
I wonder if it should help to disable the parallell processing of the rc scripts.... -- Anders Norrbring Norrbring Consulting
Anders Norrbring wrote:
Thomas Hertweck skrev:
[...] No. It should be the time between sending a SIGTERM and a SIGKILL signal.
The time when to start the shutdown process is given as a shutdown argument, not an option.
My mistake, sorry. Anyway, what's the default time? I can't see any option to find out..
You should really familiarise yourself with the manual pages... :) man init: When init is requested to change the runlevel, it sends the warning signal SIGTERM to all processes that are undefined in the new runlevel. It then waits 5 seconds before forcibly terminating these processes via the SIGKILL signal.[...] telinit can also tell init how long it should wait between sending processes the SIGTERM and SIGKILL signals. The default is 5 seconds, but this can be changed with the -t sec option. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
Thomas Hertweck skrev:
Anders Norrbring wrote:
Thomas Hertweck skrev:
[...] No. It should be the time between sending a SIGTERM and a SIGKILL signal.
The time when to start the shutdown process is given as a shutdown argument, not an option. My mistake, sorry. Anyway, what's the default time? I can't see any option to find out..
You should really familiarise yourself with the manual pages... :)
man init:
When init is requested to change the runlevel, it sends the warning signal SIGTERM to all processes that are undefined in the new runlevel. It then waits 5 seconds before forcibly terminating these processes via the SIGKILL signal.[...] telinit can also tell init how long it should wait between sending processes the SIGTERM and SIGKILL signals. The default is 5 seconds, but this can be changed with the -t sec option.
Yeah.. But that 5 second period is happening far away from the rc master script that controls the processes. The VMware processes are started and stopped via its rc script /etc/init.d/vmware, so the "problem" isn't in the end of everything, the problem is that the halt (shutdown) is called even though the stop script has not finished. I hope you follow my thoughts now, so you understand what I'm writing about. -- Anders Norrbring Norrbring Consulting
On Sun, 2007-03-11 at 16:02 +0100, Anders Norrbring wrote:
Yeah.. But that 5 second period is happening far away from the rc master script that controls the processes. The VMware processes are started and stopped via its rc script /etc/init.d/vmware, so the "problem" isn't in the end of everything, the problem is that the halt (shutdown) is called even though the stop script has not finished.
I hope you follow my thoughts now, so you understand what I'm writing about.
I don't use vmware, but had similar issue with Zoneminder closing it's mySQL db on time. I made zm script last-to-start and first-to-kill which solved the problem. Tom in NM -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
Tom Patton skrev:
On Sun, 2007-03-11 at 16:02 +0100, Anders Norrbring wrote:
Yeah.. But that 5 second period is happening far away from the rc master script that controls the processes. The VMware processes are started and stopped via its rc script /etc/init.d/vmware, so the "problem" isn't in the end of everything, the problem is that the halt (shutdown) is called even though the stop script has not finished.
I hope you follow my thoughts now, so you understand what I'm writing about.
I don't use vmware, but had similar issue with Zoneminder closing it's mySQL db on time. I made zm script last-to-start and first-to-kill which solved the problem.
Tom in NM
Yeah.. But my VMware is actually the first to stop, but as it takes up to 10 minutes to finish, the system kills it prematurely. -- Anders Norrbring Norrbring Consulting
Anders Norrbring wrote:
Yeah.. But my VMware is actually the first to stop, but as it takes up to 10 minutes to finish, the system kills it prematurely.
may be this is the problem? why does it takes so long? may be some config could avoid this. I used vmware time ago and never got so long time (the drives where smaller, then, but the HW slower also) jdd -- http://www.dodin.net Lucien Dodin, inventeur http://lucien.dodin.net/index.shtml -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
jdd skrev:
Anders Norrbring wrote:
Yeah.. But my VMware is actually the first to stop, but as it takes up to 10 minutes to finish, the system kills it prematurely.
may be this is the problem? why does it takes so long? may be some config could avoid this. I used vmware time ago and never got so long time (the drives where smaller, then, but the HW slower also)
jdd
I don't think it's a long time, after all, it has to shut down 17 VMs before exiting.. ;) I'm certain it can be solved somehow, I just don't see it ATM.. I'll keep looking at it. -- Anders Norrbring Norrbring Consulting
On Sunday 11 March 2007 12:14, Anders Norrbring wrote:
...
I don't think it's a long time, after all, it has to shut down 17 VMs before exiting.. ;) I'm certain it can be solved somehow, I just don't see it ATM.. I'll keep looking at it.
It's easy enough to write a script that does not return until no instances of a given executable are running, especially if the executable is a unique one, which VMware's executive is ("vmware-vmx", at least as of version 5.5 under a Linux host OS). A simple while loop using pidof is enough: while pidof vmware-vmx >/dev/null 2>&1; do echo vmware-vmx still running sleep 2 done The next part, getting the shutdown process to wait might be a little trickier. I recommend studying the manual pages for init and inittab. I think in essence adding a wait-style action (i.e., one with "wait" in its third field) for run level 0 that invokes the wait-for-VMware-to-exit script should suffice. Good luck. Let us know what you come up with. I occasionally shut down without remembering to stop my VMware process ('cause I tend to keep the window minimized and often forget that's running). Randall Schulz -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
Randall R Schulz skrev:
On Sunday 11 March 2007 12:14, Anders Norrbring wrote:
...
I don't think it's a long time, after all, it has to shut down 17 VMs before exiting.. ;) I'm certain it can be solved somehow, I just don't see it ATM.. I'll keep looking at it.
It's easy enough to write a script that does not return until no instances of a given executable are running, especially if the executable is a unique one, which VMware's executive is ("vmware-vmx", at least as of version 5.5 under a Linux host OS). A simple while loop using pidof is enough:
while pidof vmware-vmx >/dev/null 2>&1; do echo vmware-vmx still running sleep 2 done
The next part, getting the shutdown process to wait might be a little trickier. I recommend studying the manual pages for init and inittab. I think in essence adding a wait-style action (i.e., one with "wait" in its third field) for run level 0 that invokes the wait-for-VMware-to-exit script should suffice.
Good luck. Let us know what you come up with. I occasionally shut down without remembering to stop my VMware process ('cause I tend to keep the window minimized and often forget that's running).
Randall Schulz
I don't see how that would make any real difference.. The /etc/init.d/vmware script does NOT exit until all vmware-vmx processes are stopped. The problem as I see it is that the master process (init) gets sick of waiting for the script to exit, it thinks its stuck somewhere and simply kill it and continues to shut down.. Or it may not even kill it, it just goes on to kill the server. -- Anders Norrbring Norrbring Consulting
On Monday 12 March 2007 01:39, Anders Norrbring wrote:
...
I don't see how that would make any real difference.. The /etc/init.d/vmware script does NOT exit until all vmware-vmx processes are stopped. The problem as I see it is that the master process (init) gets sick of waiting for the script to exit, it thinks its stuck somewhere and simply kill it and continues to shut down.. Or it may not even kill it, it just goes on to kill the server.
Well, then target the master script with the "wait for completion" script and use that in a "wait"-mode run-level 0 entry in inittab. In a cursory examination, I don't see any mention of a timeout in the init or inittab manual pages. Of course, I could have missed it or it may exist and not be mentioned there. I'd give it a try, though. Randall Schulz -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 The Monday 2007-03-12 at 08:17 -0700, Randall R Schulz wrote:
Well, then target the master script with the "wait for completion" script and use that in a "wait"-mode run-level 0 entry in inittab. In a cursory examination, I don't see any mention of a timeout in the init or inittab manual pages. Of course, I could have missed it or it may exist and not be mentioned there.
Yes, it is there. Look: if test "$RUN_PARALLEL" = "yes" ; then # # Stop/Start services in parallel with make behaviour of startpar # startopt="-p4 -t 30 -T 3 $(splashmake)" eval $(startpar $startopt -M stop -P $PREVLEVEL -R $RUNLEVEL) failed="${failed:+$failed }$failed_service" skipped="${skipped:+$skipped }$skipped_service" And "startpar" is a command. Man says: NAME startpar - start runlevel scripts in parallel SYNOPSIS startpar [-p par] [-t timeout] [-T global_timeout] [-a arg] prg1 prg2 ... startpar [-p par] [-t timeout] [-T global_timeout] -M [ boot|start|stop] As the options are in «startopt="-p4 -t 30 -T 3 $(splashmake)"», it has a timeout of 30 seconds, and global timeout of 3... what? Minutes, seconds? You'd better look at the man page, it is not so simple. - -- Cheers, Carlos E. R. -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.5 (GNU/Linux) Comment: Made with pgp4pine 1.76 iD8DBQFF9XGvtTMYHG2NR9URAncHAJ41ZTtLoM6AG62d/WS9zCm5PHr37QCff10y O6YIcvc3hUMAiCKNvgVsimQ= =UtQ8 -----END PGP SIGNATURE-----
Anders Norrbring wrote:
I don't think it's a long time, after all, it has to shut down 17 VMs before exiting.. ;) I'm certain it can be solved somehow, I just don't see it ATM.. I'll keep looking at it.
How about adding vmware to a Required-Stop line in a proper init script, i.e. syslog. This should require vmware to stop before allowing syslog to stop, and everything that depends on it. HTH. -- Joe Morris Registered Linux user 231871 running openSUSE 10.2 x86_64 -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
Joe Morris (NTM) skrev:
Anders Norrbring wrote:
I don't think it's a long time, after all, it has to shut down 17 VMs before exiting.. ;) I'm certain it can be solved somehow, I just don't see it ATM.. I'll keep looking at it.
How about adding vmware to a Required-Stop line in a proper init script, i.e. syslog. This should require vmware to stop before allowing syslog to stop, and everything that depends on it. HTH.
Just the opposite.. The "Required-Stop" line is used to tell which service(s) should still be running for the script to stop. Anyway, I'll try to add $syslog and $network to the VMware server script to see what happens. ;) Thanks for the idea! -- Anders Norrbring Norrbring Consulting
Anders Norrbring skrev:
Joe Morris (NTM) skrev:
Anders Norrbring wrote:
I don't think it's a long time, after all, it has to shut down 17 VMs before exiting.. ;) I'm certain it can be solved somehow, I just don't see it ATM.. I'll keep looking at it.
How about adding vmware to a Required-Stop line in a proper init script, i.e. syslog. This should require vmware to stop before allowing syslog to stop, and everything that depends on it. HTH.
Just the opposite.. The "Required-Stop" line is used to tell which service(s) should still be running for the script to stop. Anyway, I'll try to add $syslog and $network to the VMware server script to see what happens. ;) Thanks for the idea!
Also, I just saw in the insserv manpage; Please note, that the Required-Stop, Should-Stop, and Default-Stop are ignored in SuSE Linux, because the SuSE boot script concept uses a differential link scheme But I guess it was a great thought... -- Anders Norrbring Norrbring Consulting
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 The Sunday 2007-03-11 at 16:02 +0100, Anders Norrbring wrote: ...
Yeah.. But that 5 second period is happening far away from the rc master script that controls the processes. The VMware processes are started and stopped via its rc script /etc/init.d/vmware, so the "problem" isn't in the end of everything, the problem is that the halt (shutdown) is called even though the stop script has not finished.
I hope you follow my thoughts now, so you understand what I'm writing about.
Why don't you simply define you own halt script, that calls "rcvmware stop", waits for it to return (successfully?), then it calls init 6 or halt? If the problem is that it doesn't wait for vmware to stop, then stop it separately. Otherwise, you'd have to hack "/etc/init.d/rc", which is not so simple nowdays; I don't see where to put this logic from a cursory glance at it. P.S.: Could you switch to a shorter crypt signature, a standard pgp one, for instance, please? A PKCS7 is good, certainly, but... it adds 3.3KiB to all your messages, which usually end at 11 KiB, double than normal. - -- Cheers, Carlos E. R. -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.5 (GNU/Linux) Comment: Made with pgp4pine 1.76 iD8DBQFF9S7stTMYHG2NR9URAs3wAKCXQcuXDmIwxc5slYxooNYj2kBoKwCfafHU lo/CKEWqFiXDs+W0z60I3ME= =AOaP -----END PGP SIGNATURE----- -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
Carlos E. R. skrev:
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1
The Sunday 2007-03-11 at 16:02 +0100, Anders Norrbring wrote:
...
Yeah.. But that 5 second period is happening far away from the rc master script that controls the processes. The VMware processes are started and stopped via its rc script /etc/init.d/vmware, so the "problem" isn't in the end of everything, the problem is that the halt (shutdown) is called even though the stop script has not finished.
I hope you follow my thoughts now, so you understand what I'm writing about.
Why don't you simply define you own halt script, that calls "rcvmware stop", waits for it to return (successfully?), then it calls init 6 or halt?
If the problem is that it doesn't wait for vmware to stop, then stop it separately.
Otherwise, you'd have to hack "/etc/init.d/rc", which is not so simple nowdays; I don't see where to put this logic from a cursory glance at it.
P.S.: Could you switch to a shorter crypt signature, a standard pgp one, for instance, please? A PKCS7 is good, certainly, but... it adds 3.3KiB to all your messages, which usually end at 11 KiB, double than normal.
- -- Cheers, Carlos E. R.
I switched off the cert, no real need for it on the list account.. ;) I peeked in rc as well, and didn't think it looked a bit funny. Anyway, I've made a small thing in /etc/inittab for now, just to test. I edited the level 0 entry to look like this: l0:0:wait:/etc/haltit where 'haltit' script contains first a call to stop VMware, then it calls rc 0, seems to work. But what if I issue a 'halt' command on the command line, it calls /sbin/halt - and I'm not sure if it uses inittab.. -- Anders Norrbring Norrbring Consulting -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
Anders Norrbring skrev:
Carlos E. R. skrev:
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1
The Sunday 2007-03-11 at 16:02 +0100, Anders Norrbring wrote:
...
Yeah.. But that 5 second period is happening far away from the rc master script that controls the processes. The VMware processes are started and stopped via its rc script /etc/init.d/vmware, so the "problem" isn't in the end of everything, the problem is that the halt (shutdown) is called even though the stop script has not finished.
I hope you follow my thoughts now, so you understand what I'm writing about.
Why don't you simply define you own halt script, that calls "rcvmware stop", waits for it to return (successfully?), then it calls init 6 or halt?
If the problem is that it doesn't wait for vmware to stop, then stop it separately.
Otherwise, you'd have to hack "/etc/init.d/rc", which is not so simple nowdays; I don't see where to put this logic from a cursory glance at it.
P.S.: Could you switch to a shorter crypt signature, a standard pgp one, for instance, please? A PKCS7 is good, certainly, but... it adds 3.3KiB to all your messages, which usually end at 11 KiB, double than normal.
- -- Cheers, Carlos E. R.
I switched off the cert, no real need for it on the list account.. ;)
I peeked in rc as well, and didn't think it looked a bit funny. Anyway, I've made a small thing in /etc/inittab for now, just to test.
I edited the level 0 entry to look like this: l0:0:wait:/etc/haltit where 'haltit' script contains first a call to stop VMware, then it calls rc 0, seems to work.
But what if I issue a 'halt' command on the command line, it calls /sbin/halt - and I'm not sure if it uses inittab..
Thinking about it, does anybody know if it works in inittab to combine commands, like this: l0:0:wait:/etc/init.d/vmware stop && /etc/init.d/rc 0 Should be a nice touch... -- Anders Norrbring Norrbring Consulting -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
Anders Norrbring skrev:
Anders Norrbring skrev:
Carlos E. R. skrev:
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1
The Sunday 2007-03-11 at 16:02 +0100, Anders Norrbring wrote:
...
Yeah.. But that 5 second period is happening far away from the rc master script that controls the processes. The VMware processes are started and stopped via its rc script /etc/init.d/vmware, so the "problem" isn't in the end of everything, the problem is that the halt (shutdown) is called even though the stop script has not finished.
I hope you follow my thoughts now, so you understand what I'm writing about.
Why don't you simply define you own halt script, that calls "rcvmware stop", waits for it to return (successfully?), then it calls init 6 or halt?
If the problem is that it doesn't wait for vmware to stop, then stop it separately.
Otherwise, you'd have to hack "/etc/init.d/rc", which is not so simple nowdays; I don't see where to put this logic from a cursory glance at it.
P.S.: Could you switch to a shorter crypt signature, a standard pgp one, for instance, please? A PKCS7 is good, certainly, but... it adds 3.3KiB to all your messages, which usually end at 11 KiB, double than normal.
- -- Cheers, Carlos E. R.
I switched off the cert, no real need for it on the list account.. ;)
I peeked in rc as well, and didn't think it looked a bit funny. Anyway, I've made a small thing in /etc/inittab for now, just to test.
I edited the level 0 entry to look like this: l0:0:wait:/etc/haltit where 'haltit' script contains first a call to stop VMware, then it calls rc 0, seems to work.
But what if I issue a 'halt' command on the command line, it calls /sbin/halt - and I'm not sure if it uses inittab..
Thinking about it, does anybody know if it works in inittab to combine commands, like this: l0:0:wait:/etc/init.d/vmware stop && /etc/init.d/rc 0
Should be a nice touch...
I'll answer that myself.. Nope, it doesn't work.. -- Anders Norrbring Norrbring Consulting -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 The Monday 2007-03-12 at 14:10 +0100, Anders Norrbring wrote:
I switched off the cert, no real need for it on the list account.. ;)
Thanks :-) (I use a pgp sign because we had a chap impersonating people in the Spanish list to insult others; so I "have" to... but pgp is smaller).
I peeked in rc as well, and didn't think it looked a bit funny. Anyway, I've made a small thing in /etc/inittab for now, just to test.
I edited the level 0 entry to look like this: l0:0:wait:/etc/haltit where 'haltit' script contains first a call to stop VMware, then it calls rc 0, seems to work.
Nice touch.
But what if I issue a 'halt' command on the command line, it calls /sbin/halt - and I'm not sure if it uses inittab..
I think it does. It is not crystal clear looking at the man page, but it must do, because the several rc scripts are called to stop their respective services.
Thinking about it, does anybody know if it works in inittab to combine commands, like this: l0:0:wait:/etc/init.d/vmware stop && /etc/init.d/rc 0
Should be a nice touch...
I wouldn't think so...
I'll answer that myself.. Nope, it doesn't work..
It's better with your script, IMO. - -- Cheers, Carlos E. R. -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.5 (GNU/Linux) Comment: Made with pgp4pine 1.76 iD8DBQFF9VlTtTMYHG2NR9URAukmAJ9mMeT5TE66i0fd/rRhRH+ki/xv4gCeIWkF c/VjmrEyUK+5Itfvc0Es/7s= =0CFq -----END PGP SIGNATURE----- -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
Carlos E. R. skrev:
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1
The Monday 2007-03-12 at 14:10 +0100, Anders Norrbring wrote:
I switched off the cert, no real need for it on the list account.. ;)
Thanks :-)
(I use a pgp sign because we had a chap impersonating people in the Spanish list to insult others; so I "have" to... but pgp is smaller).
I peeked in rc as well, and didn't think it looked a bit funny. Anyway, I've made a small thing in /etc/inittab for now, just to test.
I edited the level 0 entry to look like this: l0:0:wait:/etc/haltit where 'haltit' script contains first a call to stop VMware, then it calls rc 0, seems to work.
Nice touch.
But what if I issue a 'halt' command on the command line, it calls /sbin/halt - and I'm not sure if it uses inittab..
I think it does. It is not crystal clear looking at the man page, but it must do, because the several rc scripts are called to stop their respective services.
Verified, when using /sbin/halt, it makes use of the settings in inittab and consequently my little addition to it.. ;) -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
On Sunday 11 March 2007 07:50:58 am Thomas Hertweck wrote:
Anders Norrbring wrote:
Thomas Hertweck skrev:
[...] No. It should be the time between sending a SIGTERM and a SIGKILL signal.
The time when to start the shutdown process is given as a shutdown argument, not an option.
My mistake, sorry. Anyway, what's the default time? I can't see any option to find out..
You should really familiarise yourself with the manual pages... :)
man init:
That's funny! -- k -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
participants (8)
-
Anders Norrbring -
Carlos E. R. -
jdd -
Joe Morris (NTM) -
Kai Ponte -
Randall R Schulz -
Thomas Hertweck -
Tom Patton