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