My program does fork(), could that have anything to do with why upstart is not able to respawn it? If so, how can I get around this?
----- Original Message ----- From: "Harald Hoyer" <har...@redhat.com> To: "Omon Edeki (Nowell, Inc)" <omon.ed...@nowellgroup.com> Cc: <upstart-devel@lists.ubuntu.com> Sent: Wednesday, December 10, 2008 7:45 AM Subject: Re: /etc/inittab respawn daemon entry > Look in the tty files: > > # cyclone > # > > start on stopped rc2 > start on stopped rc3 > start on stopped rc4 > start on started prefdm > > stop on runlevel 0 > stop on runlevel 1 > stop on runlevel 6 > > respawn > exec /etc/spyforce/cyclone > > > Omon Edeki (Nowell, Inc) wrote: >> Also I am using upstart 0.3.9 >> >> >> ----- Original Message ----- >> From: "Omon Edeki (Nowell, Inc)" <omon.ed...@nowellgroup.com> >> To: "Garrett Cooper" <yaneg...@gmail.com> >> Cc: <upstart-devel@lists.ubuntu.com> >> Sent: Tuesday, December 09, 2008 8:14 AM >> Subject: Re: /etc/inittab respawn daemon entry >> >> >>> Greetings again. Here is the content of my file called 'syncjenius_win' >>> that >>> I placed in the /etc/event.d directory (Is this the right directory?) on >>> Fedora 10 >>> >>> # cyclone >>> # >>> # This service is started automatically by init >>> # >>> >>> description "cyclone daemon" >>> author "Nowell, Inc" >>> >>> start on startup >>> >>> start on runlevel 2 >>> start on runlevel 3 >>> start on runlevel 4 >>> start on runlevel 5 >>> >>> >>> stop on runlevel 0 >>> stop on runlevel 1 >>> stop on runlevel 6 >>> >>> respawn >>> exec /etc/spyforce/cyclone >>> >>> [END] >>> >>> -The program does start on boot (good) >>> -We ran a test to see if will actually restart if terminated. >>> - When you send the /etc/spyforce/cyclone the kill signal it DOES NOT >>> restart >>> -We want it such that if for any reason the program is stopped or >>> terminated >>> it MUST restart as it was in earlier versions of linux when we used >>> inittab >>> >>> Please if anyone can help Ill appreciate it. Also am I placing my file >>> in >>> the right directory? Currently I have it placed in /etc/event.d >>> >>> Thanks >>> >>> Omon >>> >>> >>> ----- Original Message ----- >>> From: "Garrett Cooper" <yaneg...@gmail.com> >>> To: "Omon Edeki (Nowell, Inc)" <omon.ed...@nowellgroup.com> >>> Cc: <upstart-devel@lists.ubuntu.com> >>> Sent: Monday, December 08, 2008 10:17 PM >>> Subject: Re: /etc/inittab respawn daemon entry >>> >>> >>>> On Mon, Dec 8, 2008 at 6:24 PM, Omon Edeki (Nowell, Inc) >>>> <omon.ed...@nowellgroup.com> wrote: >>>>> Greetings everyone, >>>>> >>>>> I have a SPECIFIC question. We are migrating our server application >>>>> daemon/service from an earlier version on Linux to Fedora 10. Fedora >>>>> 10 >>>>> appears to use a program called upstart. >>>>> >>>>> Our older program used the /etc/inittab to bootup and it had this >>>>> entry >>>>> >>>>> cyc:2345:respawn:/etc/spyforce/cyclone >>>>> >>>>> Essentially when the system booted up, the program cyclone would run >>>>> and >>>>> if >>>>> it every died or was killed, init would seamlessly restart it. >>>>> >>>>> My question is how exactly do I replicate this process with the >>>>> upstart >>>>> design for Fedora 10? Also I tried entering some commands in a file in >>>>> the >>>>> Fedora 10 /etc/event.d directory. I created a file and tried but I >>>>> could >>>>> not >>>>> replicate the formed init respawn process. Can I get some advice or >>>>> documentation about specifically how to do this? >>>>> >>>>> Respectfully, >>>>> >>>>> Omon >>>> Omon, >>>> >>>> 1. F10 comes with Upstart 0.3.9. Not sure when they'll be able to >>>> upgrade to 0.5.0 >>>> 2. If you were using 0.5.0, you'd do something like the following: >>>> >>>> # Start me when rc[2-5] startup. >>>> start on started rc2 rc3 rc4 rc5 >>>> # Bring me back to life if I die! >>>> respawn >>>> # Let me rest in peace if I die >>>> respawn limit 2 10 >>>> >>>> exec /etc/spyforce/cyclone >>>> >>>> Some documentation to peruse (again, for 0.5.0 -- not 0.3.9): >>>> http://upstart.ubuntu.com/wiki/Stanzas . Make sure to hit the kill and >>>> normal exit stanzas as well. >>>> >>>> -Garrett >>> >>> -- >>> upstart-devel mailing list >>> upstart-devel@lists.ubuntu.com >>> Modify settings or unsubscribe at: >>> https://lists.ubuntu.com/mailman/listinfo/upstart-devel >> >> > > > -- > upstart-devel mailing list > upstart-devel@lists.ubuntu.com > Modify settings or unsubscribe at: > https://lists.ubuntu.com/mailman/listinfo/upstart-devel -- upstart-devel mailing list upstart-devel@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/upstart-devel
