*** This bug is a duplicate of bug 268663 ***
https://bugs.launchpad.net/bugs/268663
Beware that the workaround in comment #6 will apply these 777
permissions to ALL shares defined in Samba. So this doesn't really work
if you also use Samba for other non-Public shares.
--
You received this
*** This bug is a duplicate of bug 268663 ***
https://bugs.launchpad.net/bugs/268663
I know it was a very long time ago. But I still have the same problem.
Is there any news or even solution? Thanks
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is
*** This bug is a duplicate of bug 268663 ***
https://bugs.launchpad.net/bugs/268663
** This bug has been marked a duplicate of bug 268663
files incoming through nautilus-share should be created with user ownership,
instead of nobody
--
owner of shared public folder is nobody
This is still an issue in Karmic.
The only fix I have found is to set 'create mask = 0777' and 'directory
mask = 0777' in the [global] section of /etc/samba/smb.conf
I had originally tried to set these parameters in
/var/lib/samba/usershares/sharename but they do not seem to work in
there.
I
This is most certainly still a problem.
1) Create a shared folder with guest and write permissions
2) access shared folder from windows XP and crate some files/folder
3) in ubuntu when accessing the shared folder, the files created in step 2 are
locked because they are owned by user nobody
Thank you for taking the time to report this issue and helping to make
Ubuntu better. You reported this issue a while ago and there hasn't been
any activity in it recently. We were wondering if this is still a
problem for you.
** Changed in: ubuntu
Status: New = Incomplete
--
owner of
I have run into this problem too. Correct me if im wrong but your
suggestion would make files owned by multiple people (depending on the
person accessing them)? Im not sure this is possible. Either way this is
a problem I have had trouble with in the past as well.
--
owner of shared public
Sorry if I'm missleading, no, currently files are owned by the user
nobody and the primary group of the user taht created the directory -
probably because the directory that is shared is user and group owned by
the user. What I want is, that new files are owned by the user you have
to see:
I
Yes ok that makes it all clear to me i think. Its an odd problem because
the person who put them there is using samba and can then delete them if
you gave the read/write access but you cannot because normally you would
not access the folder with samba or as root. I have a share folder much
similar
