Re: [Nolug] Specifying what user a linux daemon should run as?

Here's some good info I came across for udev... I've never needed to mess
with it before, so this was a great read.

http://www.reactivated.net/writing_udev_rules.html

It says persistant names are already built in, and I did see this yesterday
when looking at the system, just wasn't 100% sure if this would be usable by
vmware. Inside /dev/disk/by-id/ there are symbolic links already set up
that are linked to the device at boot, and this document also shows how to
set up your own symbolic link, using something simple like lto3drive or
whatever. I think that's exactly what I need. As I stated before, the
kernel is automatically recognizing it as a tape drive at boot, so it is
setting the owner to root:tape. I simply set the user that vmware is
running as, to be a member of the tape group, and that part works. Now, I
just need to set it up using the persistant udev naming, and I shouldn't
have to worry about the generic scsi id jumping around every time it
reboots. But still, for future reference, can anybody tell me where you go
to specify what user a daemon is supposed to run as? If I remember
correctly, it seems that the vmware daemon itself is running as root, but
the vm's each run as their own process, and that is run with the non-root
privledges of my standard user, for some reason. I guess it is somehow tied
to whatever user creates the virtual machine itself. I haven't seen any
setting anywhere inside vmware to change this, however.

On 5/14/08, Ron Johnson <ron.l.johnson@cox.net> wrote:
>
> -----BEGIN PGP SIGNED MESSAGE-----
> Hash: SHA1
>
>
> Sure it might. You need to create a udev rule to map the tape drive
> to /dev/SonyDAT or some such other meaningful name, and also set the
> group and privs.
>
> On 05/14/08 15:20, Chris Jones wrote:
> > Actually, this is weird. I think I figured out what is going on.
> >
> > It was /dev/sg0, but after a reboot it is now /dev/sg3, with owner of
> > root/tape. So, I added my user into the tape group and remapped vmware
> > to use /dev/sg3, and now it seems to be working. I'm not sure why it
> > switched from sg0 to sg3, other than the system update that ran.
> > Hopefully that's why the ID changed. Kind of scary though, hopefully
> > the generic scsi ID won't be jumping around every time the server
> reboots.
> >
> > On Wed, May 14, 2008 at 3:07 PM, Chris Jones <techmaster@gmail.com
> > <mailto:techmaster@gmail.com>> wrote:
> >
> > I'm not seeing a vmware user on the system. How can you see what
> > user a process is running as?
> >
> >
> > On Wed, May 14, 2008 at 2:55 PM, Petri Laihonen
> > <pietu@weblizards.net <mailto:pietu@weblizards.net>> wrote:
> >
> > Try adding a vmware user into the root group.
> > If I remember correctly, vmaware runs as it's own user.....
> >
> > Petri
> >
> > Chris Jones wrote:
> > > In linux, how do you tell it what user you want a daemon to
> > run as?
> > >
> > > I'm having issues with vmware in linux, with a tape drive. I
> > need to
> > > map a scsi tape drive into a vm, but the vm doesn't have access
> to
> > > /dev/sg0. I can go chmod 777 the /dev/sg0 and it works
> > perfect, but
> > > as soon as I reboot it goes back to 660 and an owner of
> root/root.
> > > So, how can I ensure that vmware is either running as root
> (yeah,
> > > probably a bad idea) or make sure that the permissions stick
> > for that
> > > device?
>
> - --
> Ron Johnson, Jr.
> Jefferson LA USA
>
> We want... a Shrubbery!!
> -----BEGIN PGP SIGNATURE-----
> Version: GnuPG v1.4.6 (GNU/Linux)
>
> iD8DBQFIK0z4S9HxQb37XmcRAtjHAKCD1jqBRpofezxMCz0tulda8fVfegCg679N
> MGFWhj6p3xw10FgPND41j4U=
> =I+N3
> -----END PGP SIGNATURE-----
> ___________________
> Nolug mailing list
> nolug@nolug.org
>

-- 
Chris Jones
http://www.industrialarmy.com
___________________
Nolug mailing list
nolug@nolug.org