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> 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>
> 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?
>> ___________________
>> Nolug mailing list
>> nolug@nolug.org
>>
>
>
>
> --
> Chris Jones
> http://www.industrialarmy.com
-- Chris Jones http://www.industrialarmy.com ___________________ Nolug mailing list nolug@nolug.orgReceived on 05/14/08
This archive was generated by hypermail 2.2.0 : 12/19/08 EST