On Sat, 2009-10-03 at 15:10 +0000, Daniel Hahler wrote:
> A good workaround for this might be pidfile handling, where upstart
> would use a given pidfile for monitoring the job.
>
Ugh, god no.
Do you know how many bugs there are with a system of requiring
applications to write the correct pid to a file? Do you know how many
major problems you introduce if they get it wrong?
The "solution" is to use something like cgroups or the proc_connector to
track multiple processes.
Scott
--
Have you ever, ever felt like this?
Had strange things happen? Are you going round the twist?
On Sat, 2009-10-03 at 15:10 +0000, Daniel Hahler wrote:
> A good workaround for this might be pidfile handling, where upstart
> would use a given pidfile for monitoring the job.
>
Ugh, god no.
Do you know how many bugs there are with a system of requiring
applications to write the correct pid to a file? Do you know how many
major problems you introduce if they get it wrong?
The "solution" is to use something like cgroups or the proc_connector to
track multiple processes.
Scott
--
Have you ever, ever felt like this?
Had strange things happen? Are you going round the twist?