The time it is run from startup is very important. You must make sure that any dependent communications service have been run successfully prior to the running of your service. This is done via the Snn symlink. The higher the number the later on boot that this will start. On 17 Sep 2002 at 22:32, Ofer Biran wrote:
I have a java service set exactly according to init.d/skelton (this is on Suse 7.2 for 390). When init.d/myservice is run outside boot - it's OK. When run during boot - it starts OK (get to the printout of listen on ServerSocket)- but then it is killed !
Then... I tried a very simple shell script service that just echo (i=1,2,3...) and sleep between. It works of course forever outside boot - but in boot, it prints (into a file - I used startproc -l) till 3 and killed !!
So what's the story here ??? I tried all combination of startproc / direct exec / various rc.3/Sxxmyservice - no change - the process starts OK but doesn't survive the boot. It's also reported among failed services in run level 3 - but [desparately] I added sleep after the startproc - then it runs some more... and killed... just this time without being reported among the failed services.
Any help / idea will be appreciated !
Ofer Biran
_________________________________________________________________ Send and receive Hotmail on your mobile device: http://mobile.msn.com
-- To unsubscribe, email: suse-programming-e-unsubscribe@suse.com For additional commands, email: suse-programming-e-help@suse.com Archives can be found at: http://lists/archive/suse-programming-e
--
Jerry Feldman