Hi, On Mon, Aug 04, 2003 at 09:47:36AM -0700, ToniB wrote: > --- Ryan Underwood <[EMAIL PROTECTED]> wrote: > > > The problem occurs when: > > 1) The daemon is run with root privileges > > 2) The daemon's init script is run through a `sudo`. > > > > DOSEMU checks to the "real" uid, drops privileges to the > > real uid, and then can no longer access the files which have root > > permissions. So it fails starting the user's requested program for > > > > 'man sudoers' explains how you can add a line > to allow users to exec a file or cmd line. > > You might want to give access to all users, > to the command (that ony root can exec now), > by adding a line like > > USERS-LIST BBS-HOST=cmdline > > to your sudoers file.
Thanks for the reply. I'm still having trouble seeing how that would affect the issue. The problem is not that people are not able to run sudo; it is that when sudo is used to run the init script, when dosemu eventually becomes a child process of (a child process of) the init script, it sees that "hm, this program is running as root, but the real uid of the person who started it is not root", and drops the root privileges that were afforded to it by sudo. When a "real" root login runs the init script, then dosemu sees that the real uid matches the effective uid, and doesn't drop privileges. Do you see what I mean? -- Ryan Underwood, <nemesis at icequake.net>, icq=10317253 - To unsubscribe from this list: send the line "unsubscribe linux-msdos" in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html
