See rP2fedb6f941d8. We might need a more general version of this since we do some sudo stuff elsewhere, but at least on my machine sudo -n exits with code 0 when the target user exists but needs a password.
Details
Details
- Reviewers
btrahan - Commits
- Restricted Diffusion Commit
rPb3394c53d8e9: Detect goofy `sudo -n` output under OSX
- Tried to run daemons as root, with no automatic sudo to root. Got a bad result before (phd believed it had executed the daemons) and a good result afterward (phd recognized that sudo failed).
- Tried to run daemons from root, as a non-root user. Got a good result in both cases.
Diff Detail
Diff Detail
- Repository
- rP Phabricator
- Branch
- phdosx
- Lint
Lint Passed - Unit
No Test Coverage - Build Status
Buildable 3328 Build 3335: [Placeholder Plan] Wait for 30 Seconds
Event Timeline
Comment Actions
"a password is required" might be a locale specific string. (I've seen users have german text there).
Just checking for sudo: however might match some pam warnings that start the daemon anyway which might result in two daemons.. :(
Comment Actions
Yeah, I don't see a very good way around that. Most OSX installs of Phabricator are run by developers working on it, though, so I think it's OK that this isn't perfect.
Comment Actions
Yeah i've got no real idea there either. Might be a good idea to move the whole 'run things as another user' stuff into the ExecFuture (or have an SudoExecFuture) and try to handle it centrally in the future.
Comment Actions
Thanks for the code changes here.
For my own setup, should I be running some command on the _phd user so it can be su'd to? Note this now basically works in that I hit the "just run this as the active user" codepath successfully now so we can also just drop this if everyone wants. :D
Comment Actions
You can do a few things:
- If you run phd as root, it should be able to sudo as _phd (since root can always sudo without a password, normally). You could switch to root with su, or likely run sudo phd start.
- If you run phd as _phd, it shouldn't need to sudo.
- If you want to be able to sudo from btrahan to _phd directly, without going through root, you'd need to edit /etc/sudoers and put some black magic in there. I don't know it offhand but you can google around, it's something like btrahan ALL=(_phd) NOPASSWD: