Hi Chuck,
How do I set the debug log level to 9? I thought the request for a log was
directed to Killing Vector. But, I'll try to create the log if you can point me
to documentation on how to do that.
Thanks,
-- Scott
--
samba shares of symlinks are always read-only
https://bugs.launchpad.net/b
No response from user, closing.
Regards
chuck
** Changed in: samba (Ubuntu)
Status: Confirmed => Won't Fix
--
samba shares of symlinks are always read-only
https://bugs.launchpad.net/bugs/380715
You received this bug notification because you are a member of Ubuntu
Server Team, which is s
Can you include the log file when the debug level is set to 9 please?
Thanks
chuck
** Changed in: samba (Ubuntu)
Status: Incomplete => Confirmed
--
samba shares of symlinks are always read-only
https://bugs.launchpad.net/bugs/380715
You received this bug notification because you are a me
I can confirm this problem. On my Kubuntu Jaunty box:
/data/multimedia
/data/multimedia/mp3
/data/mp3 < symlink to /data/multimedia/mp3
On Windows, when I access the files under /data/mp3, they are all read-only. No
write permissions at all.
But when I access those same files using /d
I still can't reproduce it. I use your smb.conf and I can put files to
the "shared" share correctly using smbclient. To rule out the client
issue, could you try writing to the shared/shared2 shares locally using
smbclient ?
--
samba shares of symlinks are always read-only
https://bugs.launchpad.n
I've attached my smb.conf file, if it helps. -- Scott
** Attachment added: "smb.conf"
http://launchpadlibrarian.net/28840002/smb.conf
--
samba shares of symlinks are always read-only
https://bugs.launchpad.net/bugs/380715
You received this bug notification because you are a member of Ubuntu
S
Hi Thierry,
I tried what you suggested and had the same problem. However, I did
discovered something. It seems that it is the *name* of the share that
is causing the problem rather than what it is pointing to. On my system,
anything shared using the name "shared" is read-only, whether it points
to
I can't reproduce the problem on Jaunty. I created a symlink and shared
it using your parameters, I could successfully write to the resulting
share. So maybe the issue comes from somewhere else ?
Please try a simple local link/share like this and let me know if it works for
you:
$ mkdir real
$ ln
Thanks for the suggestion, chuck.
It seems that the parameter you suggested does not change anything. The
problem still exists.
N.B. this same share configuration worked before with the Ubuntu 8.10
release, but stopped working when I upgraded to Ubuntu 9.04. So, I think
it's a problem with the im
What happens when you put unix extenstions = no?
Regards
chuck
** Changed in: samba (Ubuntu)
Status: New => Incomplete
--
samba shares of symlinks are always read-only
https://bugs.launchpad.net/bugs/380715
You received this bug notification because you are a member of Ubuntu
Server Team
** Attachment added: "Dependencies.txt"
http://launchpadlibrarian.net/27180014/Dependencies.txt
--
samba shares of symlinks are always read-only
https://bugs.launchpad.net/bugs/380715
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to sam
11 matches
Mail list logo
