On Sat, Mar 17, 2012 at 2:42 PM, Steve Langasek <[email protected]>wrote:
> On Sat, Mar 17, 2012 at 09:09:11AM -0400, Evan Huus wrote: > > The cookbook has the answer [1] :) > > > TLDR: If you're running upstart 1.4 or later, you can use the 'setuid' > and > > 'setgid' stanzas. Otherwise you'll have to use su, sudo or > > start-stop-daemon. Start-stop-daemon is recommended, because su and sudo > do > > a bunch of extra stuff to the PAM session that is probably unnecessary > for > > a daemon process. > > It's not that it's "probably unnecessary", it's that it's actively harmful > to run PAM sessions for most daemons. You don't want every daemon on your > system to show up as an active session to consolekit. I didn't realize that (PAM interactions are not something I know much about). The cookbook should probably be reworded to make this point clearer then, since right now it's just 'generally advised' not to use su or sudo. Thanks, Evan
-- upstart-devel mailing list [email protected] Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/upstart-devel
