Re: xdm: init script's execution can be terminated prematurely if invoke-rc.d run from child process of xdm
Maybe remove the pid file before killing, not after? If it resists our best attempts at killing. including -9, that would be a different bug, and leaving a pid file would be useless anyway? Just a guess.
Re: xdm: init script's execution can be terminated prematurely if invoke-rc.d run from child process of xdm
I recall prepending a nohup: [EMAIL PROTECTED] nohup invoke-rc.d xdm stop solved the problem. So maybe a nohup or trap inside /etc/init.d/xdm would be what you want. The only problem left then would be cleaning up the nohup.out created. This could also be done for other /etc/init.d/?dm's.
Re: xdm: init script's execution can be terminated prematurely if invoke-rc.d run from child process of xdm
Dan Jacobson [EMAIL PROTECTED] writes: I recall prepending a nohup: [EMAIL PROTECTED] nohup invoke-rc.d xdm stop solved the problem. So maybe a nohup or trap inside /etc/init.d/xdm would be what you want. The only problem left then would be cleaning up the nohup.out created. This could also be done for other /etc/init.d/?dm's. Thats the users responsibility. You can also use screen or simply with a properly configured shell. If the scripts start to fork off they would all be run in parallel at boot time and one couldn't ctrl-c them anymore if they run wild. Also /etc/init.d/foobar stop; /etc/init.d/foobar start wouldn't work. The stop would still be running in the background. Overall, bad idea. MfG Goswin
