Thanks guys, No, no specific reason. Just concerned about losing contact with a remote system, should sshd stop for whatever reason.
/Lennart On Tue, Sep 22, 2015 at 11:59 AM, Gustavo Carneiro <gjcarne...@gmail.com> wrote: > I agree with Mikko that your main sshd should probably be left alone. But > if for some reason you need to start a second sshd instance, listening on a > different port and with different config file, it's pretty easy: > > [program:my_sshd] > command = /usr/sbin/sshd -D -f /my/sshd_config > redirect_stderr=true > stopasgroup=true > killasgroup=true > > > > On 22 September 2015 at 10:44, Mikko Ohtamaa <mi...@redinnovation.com> > wrote: > >> >> >>> Currently my sshd is started via a script executed by etc/init.d/rcS >>> Would it be wise to instead let supervisord start sshd? >>> (I assume it must be started by supervisord, or it can't be supervised.) >>> >> >> Unless you know any specific reason why you would do this, stick to the >> distribution policy. >> >> >> -- >> Mikko Ohtamaa >> http://opensourcehacker.com >> http://twitter.com/moo9000 >> >> >> _______________________________________________ >> Supervisor-users mailing list >> Supervisor-users@lists.supervisord.org >> https://lists.supervisord.org/mailman/listinfo/supervisor-users >> >> > > > -- > Gustavo J. A. M. Carneiro > Gambit Research > "The universe is always one step beyond logic." -- Frank Herbert >
_______________________________________________ Supervisor-users mailing list Supervisor-users@lists.supervisord.org https://lists.supervisord.org/mailman/listinfo/supervisor-users
