umask ignored on save state files? (bug 1260)

[chemame]

Not finding any new info on bug 1260, which is now causing great grief in my setup. Details appear to be precisely as stated in the original bug report. I have one shared area for VirtualBox machines & hard disks, with perms set for group rw. However, each "SAVE MACHINE STATE" action produces a new file with rw for owner only, completely ignoring my umask.

Any advice? Thanks.

[solanum]

I agree, this is extremely annoying and makes it impossible to share a vm between users, which makes it useless for my purposes, I may have to go back to vmware.

Bug 1260 was opened a year ago and I would have thought it is a very simple bug to fix (not that I'm a programmer...).

[dimasfs]

I also have this problem, I was hoping to get rid of it on the newest releases but until now, nothing!

Did you see that this problem is rated as "minor"? Well, it can be... but still ONE YEAR?

Please guys, at least a workaround is needed...

[Max Rebo]

I also have this problem, I was hoping to get rid of it on the newest releases but until now, nothing!

Did you see that this problem is rated as "minor"? Well, it can be... but still ONE YEAR?

Please guys, at least a workaround is needed...

Just butting in... umask implies a linux host. As a workaround you can have a cron job running the following:

Code: Select all

find /folder-for-save-states -name "*.sav" -user vboxUserName -maxdepth 0 -execdir chmod 664 {} \;

Set the above to run once a minute. Will that work for you? Change the /folder-for-save-states to the proper path and change the name parameter to the proper file name. I set maxdepth to 0 folders so the cron job would not spend time wandering but you might remove this parameter and value if you want to perform the search/permissions change on the whole ~/.VirtualBox/ folder.

Just a suggestion. I like VirtualBox a lot and like to see it get used.

HTH!

[dimasfs]

Hi Max Rebo,

thank you for your suggestion. I actually got another workaround.

Since the files I save on a windows guest are to be shared over samba on the linux host, I used the "force user" option of samba to be sure that whoever try to read the file, will be access the file with the vbox credentials.

My problem is that in any other case, I could not read the file at all.

Thank you anyway.