[CentOS] Migrating CentOS 5 -> 6: where to put /etc/inittab respawn scripts?
Les Mikesell
lesmikesell at gmail.comWed Oct 5 17:22:50 UTC 2011
- Previous message: [CentOS] Migrating CentOS 5 -> 6: where to put /etc/inittab respawn scripts?
- Next message: [CentOS] Migrating CentOS 5 -> 6: where to put /etc/inittab respawn scripts?
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
On Wed, Oct 5, 2011 at 12:04 PM, Alexander Farber <alexander.farber at gmail.com> wrote: > My script has 2 pecularities: > > 1) When it gets SIGTERM or SIGINT, it writes some data into PostgreSQL > and this takes 10-15 seconds > > 2) When it is started numerous times, > then the subsequent runs > will fail immediately, because only the 1st instance > will be able to listen at the TCP-port 8080 > > And in /var/log/messages I see: > > ... > 17:44:25 static init: pref main process ended, respawning > 17:44:26 static init: pref main process (2128) terminated with status 98 > 17:44:26 static init: pref main process ended, respawning > 17:44:26 static init: pref main process (2133) terminated with status 98 > 17:44:26 static init: pref respawning too fast, stopped > > is that all maybe the reason and is there something I could do? > (maybe somehow delay the subsequent spawns?) Can you make it sleep a bit and retry the socket open a few times if it fails due to the previous process not releasing the port yet? -- Les Mikesell lesmikesell at gmail.com
- Previous message: [CentOS] Migrating CentOS 5 -> 6: where to put /etc/inittab respawn scripts?
- Next message: [CentOS] Migrating CentOS 5 -> 6: where to put /etc/inittab respawn scripts?
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
More information about the CentOS mailing list