ssh-agent subprocess parentage

Daniel Kahn Gillmor dkg at
Tue May 10 07:22:33 EST 2011

On 05/09/2011 05:16 PM, Ángel González wrote:
> Note that you could supervise it by running the commands in the shell.
> So instead of
> $ supervise ssh-agent bash
> you can do
> $ bash
> bash$ eval $(supervise ssh-agent)
> Or even
> bash -c 'eval $(supervise ssh-agent); exec bash'

so yes -- i can certainly supervise it if i don't supply a subcommand at
all; but in this case, i want it to run a subcommand.

For concreteness' sake, imagine a daemon that stays in the foreground,
but needs to talk to an ssh-agent which handles its keys.  If either the
agent or the daemon dies, you'd like the supervising process to restart
the whole chain.

With the documented behavior, this would work fine.

With the existing actual behavior, if the agent dies (for whatever
reason), the supervising process has no way of knowing.

> When you login into a system, the shell is the ancestor of everything.
> Thus it looks
> more natural that it is the same for ssh-agent, too. But your view may
> be completely
> different :)

i'd expect that the first process invoked is the ancestor of everything,
which in this case would be ssh-agent :)


-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 1030 bytes
Desc: OpenPGP digital signature
URL: <>

More information about the openssh-unix-dev mailing list