Take the 2-minute tour ×
Ask Ubuntu is a question and answer site for Ubuntu users and developers. It's 100% free, no registration required.

I'm using last upstart version for ubuntu 10.4 LTS. upstart is launched with --debug kernel flag.

I'm making a custom job configuration for nzbget daemon. Basically, this job has a pre-start script that mounts a filesystem, a post-start script that unmounts the filesystem and an exec nzbget -D line.

The problem is that the nzbget daemon needs to run as a non privilleged user. This feature is already included in nzbget. Indeed, when I run from console sudo nzbget -D the process runs as a non privileged user. But when I start the upstart job with the exec nzbget -D line, the process nzbget -D runs as root. As said in the upstart cookbook, I tried to use su -c "nzbget -D" user and also start-stop-daemon both without the expect stanza as adviced. But for both commands, as upstart tracks the wrong PID I guess, it sees the main process as killed (owing to upstart logs) at the end of start process and thus, it launches the post-process script which I don't want.

=> How can I do it right? How is it that exec nzbget -D upstart command makes the process run as root whereas sudo nzbget -D command makes it run as non privilleged user?

share|improve this question
add comment

2 Answers 2

Progress was made for this just yesterday with the release of version 1.4 .

New “setuid” and “setgid” stanzas to allow system jobs to be run under the specified uid/gid corresponding to the given name/group.

You can grab it from their LaunchPad page but (strangely) I can't see a PPA so you might have to compile it yourself.

Otherwise, use su or sudo in your exec command like so:

su -c "<commands>" <username>
sudo -u <username> <commands>

They both do pretty much the same thing so pick whichever you're happiest with. So using your example command:

exec sudo -u me "nzbget -D"
share|improve this answer
    
domain name upstart.at is undead –  Prof. Falken Feb 4 '13 at 14:59
    
Thanks for this! Wasn't clear to me in the Upstart docs if I should be using Session Init/Jobs etc. –  Luke Hoersten Dec 15 '13 at 3:33
add comment

I suggest using sudo with the following syntax:

sudo -u foouser foocommand

this runs the command foocommand as user foouser.

share|improve this answer
add comment

Your Answer

 
discard

By posting your answer, you agree to the privacy policy and terms of service.

Not the answer you're looking for? Browse other questions tagged or ask your own question.