This is a discussion on samba-problem within the Slackware Linux Support forums, part of the Unix Operating Systems category; --> I've got a problem running samba (3.0.2a) on slackware 9.1: Samba does not follow any symbolic links although I've ...
| |||||||
| FAQ | Members List | Calendar | Search | Today's Posts | Mark Forums Read |
| ||||
| I've got a problem running samba (3.0.2a) on slackware 9.1: Samba does not follow any symbolic links although I've added "follow symlinks = yes" to smb.conf and as of the documentation this setting is default anyway. smbd starts without any errors. Any suggestions? |
| |||
| On 2004-08-11, Torsten Stauder <audio07@t-online.de> wrote: > I've got a problem running samba (3.0.2a) on slackware 9.1: > Samba does not follow any symbolic links although I've added "follow symlinks = yes" to smb.conf and as of the documentation this setting is > default anyway. > smbd starts without any errors. > > Any suggestions? Check out the "wide links" parameter in smb.conf (man smb.conf). Use 'testparm -v' to see all your options laid out. Becareful about symlinks. The man page warns of reasonably possible symlink-attack scenerio. -- --- SIGSEGV (Segmentation fault) @ 0 (0) --- +++ killed by SIGSEGV +++ |
| ||||
| >>I've got a problem running samba (3.0.2a) on slackware 9.1: >>Samba does not follow any symbolic links although I've added "follow symlinks = yes" to smb.conf and as of the documentation this setting is >>default anyway. >>smbd starts without any errors. >> >>Any suggestions? > > > Check out the "wide links" parameter in smb.conf (man smb.conf). Use > 'testparm -v' to see all your options laid out. Becareful about > symlinks. The man page warns of reasonably possible symlink-attack > scenerio. > wide links = Yes follow symlinks = Yes I know it's (potentially) a security hole. But believe me - my mother won't attack my server and it's firewall-secured to outside. So any further suggestions? |