ssh -f and pid

Damien Miller djm at
Fri Feb 5 16:49:17 EST 2010

On Thu, 4 Feb 2010, Ming wrote:

> > It isn't necessary. You can tear down ssh connections from the control
> > socket and learn the PID of a running SSH, see the commands listed
> > under -O in ssh(1).
> >
> A individual can do an number of things with a understanding of and beyond
> the man page, but how do you get ssh to play nicely in a ecosystem of
> monitoring software?

It isn't above and beyond the manpage, checking the state of a running
connection is a clearly documented feature.

> Say the os has bunch of ssh processes active.  How the monitoring software
> in a standard way which ones it created -- and thus track -- and which ones
> it hasn't?

It can request separate control sockets if it likes.

> ControlPath has to be specified for -O and command line query required?  How
> is ssh suppose to plug and play with monitoring software?

I think the monitoring software needs to support ssh and not the other
way around. There are lots of ways one might monitor ssh, and I don't think
we could even be "plug and play" with all of them.


More information about the openssh-unix-dev mailing list