Matt Bedynek wrote to All <=-
It removes the busy file but the process never stops running. I would figure that as long as I try to stop it as the same user it is running
I should not need to issue the stop as super user?
It removes the busy file but the process never stops running. I
would figure that as long as I try to stop it as the same user it
is running I should not need to issue the stop as super user?
I always start and stop as the superuser.
It removes the busy file but the process never stops running. I
would figure that as long as I try to stop it as the same user
it is running I should not need to issue the stop as super user?
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.
Mystic automatically forks to the unpriviledged user that the
executable is owned by when started as root.
Mystic automatically forks to the unpriviledged user that the
executable is owned by when started as root.
Matt Bedynek wrote to Tony Langdon <=-
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.
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 o non-privleged ports (i.e. 2222) then forward 22 to that.
MIS and MIS2 actually drop privileges to the user/group that owns the binari so they're safe to start as root, provided root doesn't own them.
Robert Wolfe wrote to Tony Langdon <=-
But any Linux admin worth their salt knows that in case like this you NEVER want to use root -- but use sudo instead.
Tony Langdon wrote to Robert Wolfe <=-
But any Linux admin worth their salt knows that in case like this you NEVER want to use root -- but use sudo instead.
We're talking about starting from a startup script. Most daemons are started as root, and drop privileges. Sudo isn't normally used that
way.
Tony Langdon wrote to Robert Wolfe <=-
But any Linux admin worth their salt knows that in case like this you
NEVER want to use root -- but use sudo instead.
We're talking about starting from a startup script. Most daemons are
started as root, and drop privileges. Sudo isn't normally used that
way.
Ah, ok, that's a different story, then. I was thinking mis2 was being started once the system started up. My error.
Robert Wolfe wrote to Tony Langdon <=-
Ah, ok, that's a different story, then. I was thinking mis2 was being started once the system started up. My error.
All,
I run mystic under its own user name. I am able to start mis2
succssfully and it appears to fuction but I am not able to stop it.
Sysop: | digital man |
---|---|
Location: | Riverside County, California |
Users: | 1,041 |
Nodes: | 15 (1 / 14) |
Uptime: | 86:45:44 |
Calls: | 236,118 |
Calls today: | 8 |
Files: | 60,371 |
D/L today: |
77 files (87,441K bytes) |
Messages: | 289,799 |
Posted today: | 1 |