Tim, you have a whole load of things in the global section that I would
leave out (including the msdfs line).
Your original problem was "...when they save to the samba share the file
permissions comes up as nobody & nogroup". You do have "guest ok = yes"
and you also have "map to guest = Bad User", so I suspect that for some
reason your users' authentication is failing and thus files are being
created nobody:nogroup.
Were it me, I'd stop Samba, save your existing smb.conf and replace it
with this:
--------------------------------------------------------------------------------
[global]
workgroup = HOME
passdb backend = tdbsam
wins support = Yes
read only = no
guest ok = no
[Pictures]
path = /mnt/sda1/Pictures
--------------------------------------------------------------------------------
Start Samba, try that, make sure users are being authenticated correctly,
and see what ownership files have when created. If the authentication
fails, you need to fix that. If the files are created with the expected
owner and group, you can add parts of your original smb.conf back in and
test until you find the failing line; however, as I said above, I suspect
a user authentication problem.
For the record (and it may not be important in your environment), setting
a Samba share directory to 0777 isn't very secure, and your method of
sharing may cause a problem if userA wants to modify files created by
userB as they may find the permissions don't allow that - but this isn't a
problem you have right now, so let's fix your problem first.
hth,
Keith
--
Keith Edmunds
+-------------------------------------------------------------------------+
| Tiger Computing Ltd | Helping businesses make the most of Linux |
| "The Linux Specialists" | http://www.tiger-computing.co.uk |
+-------------------------------------------------------------------------+
