File creation as part of Moneydances internal backup process: Ownership and permissions on the network.

Thomas Garson <tgarson-3Ml1UW5/cBpWk0Htik3J/[email protected]> Fri, 05 Aug 2011 10:04:15 -0700
Newsgroups gmane.comp.finance.moneydance.general
Message-ID <[email protected]>
Sean,

For context, I'm still running Moneydance 606 'cause so far it does what 
I need....

Now for my issue:
The MD data file lives in a Samba share on an OpenSuse 11.4 server.
I have MD installed on my home office PC (OpenSuse 11.3) and my wifes' 
laptop (Windows XP).
Only one of us runs MD at any time because we access the same data file.
The owner of the share, and all files in it including the MD data file, 
is "root", but Group ownership is "operator", a Group to which both my 
and my wifes User IDs belong.
We both have rw Group access to the share and the MD data file through 
both Linux and Samba permissions and can open, edit and save the data 
file file with MD.
However, the saved file will not have root ownership. Its owner will be 
either my ID or my wifes', depending on which of us saved it. It will 
also have altered permissions that only allow User (no Group) write access.
I've worked around the permissions issue by having new files created 
with 0770 permissions by using the Force File Mode feature of Samba. 
However, if the data file was merely being opened, edited and saved, 
this should not be necessary.
The way this is working seems to indicate that MD is renaming the old 
file to be the backup and creating a new current data file, which I find 
to be a counter-intuitive method, if used.
If MD copied the old file to the backup name prior to saving the newly 
edited version, the ownership of the MD data file, as well as Group and 
all permissions, should be preserved. This is how I would prefer it to 
work. If this is what MD already does, then I have more server sleuthing 
to do. If this has been implemented since 606 then I guess it would be 
time to upgrade.

Thanks,
Tom Garson
Aural Technology