[PLUG] umask issues with VirtualBox Machine files
Russell Senior
seniorr at aracnet.com
Wed Jun 2 10:06:47 UTC 2010
>>>>> "Ken" == Ken Stephens <kens at cad2cam.com> writes:
Russell> I am setting up a Ubuntu machine on which multiple people
Russell> share VirtualBox guest machines. When guest machines are
Russell> closed, various files, particularly in the Machines tree, get
Russell> stored with the wrong permissions (0600, rather than 0660
Russell> that is needed). The group ownership is set up so that newly
Russell> created files are owned correctly. Setting umask to 002
Russell> doesn't seem to help.
Russell> Anybody with experience in this kind of situation? Potential
Russell> solutions?
Ken> Did you mean to set the parent directory with the GUID bit set?
Ken> If you want files inside the directory, then chmod the parent
Ken> directory to 02770. This will set the unix permissions to
>> chmod 02770 . ls -la
Ken> drwxrws--- owner group 4895 . Note the s in place of the x in
Ken> the group triplet.
Ken> So when a file is created by a member of group group, the
Ken> permisisons are set 660.
Ken> -rw-rw---- member group 463764 newfile
Ken> Caveats: member is member of group group.
Yeah, I set the GUID bit, and that handles the group ownership part,
but not the permissions part. Apparently, somewhere in the bowels of
VirtualBox, the umask for the process is being set to 022 which means
that created files get 0600 permissions (maybe for a good reason),
which is not lenient enough. I am reading more deeply into the
VirtualBox user manual to see if there is a preferred way to handle
this scenario, or if I just need to hack together somekind of cronjob
to patch things up for me.
So close, and yet so far.
--
Russell Senior ``I have nine fingers; you have ten.''
seniorr at aracnet.com
More information about the PLUG
mailing list