OK - resubmitted with suggested approach.
Cheers
James
On 20/06/13 19:14, Ben Pfaff wrote:
I think it might be sufficient to check that the parent pid changed,
rather than being picky about the new parent pid or the name of the
process associated with that new parent pid.
On Thu, Jun 20, 2013
I think it might be sufficient to check that the parent pid changed,
rather than being picky about the new parent pid or the name of the
process associated with that new parent pid.
On Thu, Jun 20, 2013 at 07:11:51PM +0100, James Page wrote:
> Meh - I need to test this better; not working reliably
Meh - I need to test this better; not working reliably everywhere.
On 20/06/13 18:44, James Page wrote:
On Ubuntu Saucy based desktops, upstart runs with user sessions
enabled which means that the init process under which a daemon
might run is not always pid = 1.
Check for a process with cmd na
On Ubuntu Saucy based desktops, upstart runs with user sessions
enabled which means that the init process under which a daemon
might run is not always pid = 1.
Check for a process with cmd name of 'init' instead.
Signed-off-by: James Page
---
tests/daemon-py.at | 10 ++
tests/daemon.at
