Subj : mis2
To   : Tony Langdon
From : Matt Bedynek
Date : Fri Oct 06 2017 19:11:44

Tony,

Friday October 06 2017 17:44, you wrote to me:

 MB>> It removes the busy file but the process never stops running.  I
 MB>> would figure that as long as I try to stop it as the same user it
 MB>> is running I should not need to issue the stop as super user?

 TL> I always start and stop as the superuser.

I haven't tested this but since I dont see a configurable option to fork to 
unprivleged user that this means always running as root.  In the "industry" 
this is viewed as not good.  What I do is configure my instances to listen on 
non-privleged ports (i.e. 2222) then forward 22 to that.

Take care,

Matt

---
 * Origin: The Byte Museum - www.bytemuseum.org (1:19/10)

.