From: Dominic R. <dl...@ed...> - 2011-01-23 09:40:34
|
On 22/01/11 20:20, Heiko Zuerker wrote: > Quoting Dominic Raferd<dl...@ed...>: >> On 22/01/11 12:06, Heiko Zuerker wrote: >>> Quoting Dominic Raferd<dl...@ed...>: >>> >>>> On 22/01/11 11:45, Heiko Zuerker wrote: >>>>> Quoting Dominic Raferd<dl...@ed...>: >>>>>> Thanks Heiko, but I do not have /var anywhere in my smb.conf file. I >>>>>> only have paths that are subdirectories of /home. >>>>> Okay. >>>>> >>>>> Do you have this line in the smb.conf? >>>>> >>>>> [IPC$] >>>>> wide links = Yes >>>>> >>>> No, I have no reference to IPC at all. I think IPC is some internal >>>> Samba thingy. I do have 'wide links = Yes' in all my shares (but IPC is >>>> not among them) - I want to have wide links = No (the default - safe - >>>> setting) but this prevents access. >>> Add the above 2 lines to your smb.conf and things should work better. >>> It's a hidden share which is being used for the communication. >>> (Not sure about the details on it). >> If I add lines: >> >> [IPC$] >> path = /shm/var/tmp >> wide links = Yes >> >> then the errors in log about IPC stop, which is good, thanks. Both of >> these lines are needed. But if I have a share with wide links = No and I >> try to connect to it I still see this in the log: >> >> [2011/01/22 14:27:18.361834, 0] smbd/service.c:988(make_connection_snum) >> canonicalize_connect_path failed for service exampleshare, path >> /home/z-shares/exampleshare > I don't understand why it fails on /home, the ones I used under /var > were explained by the symlink. > And it not only fails on /home, it also fails with shares on /var or /shm/var... The only way I can get it to work is with 'wide links = Yes' parameter. In fact I cannot find any location that works with 'wide links = no'. Do you have shares on /var working with 'wide links = No'? |