Hi All, I was using samba client 3.0.0-15 on fedora core 1, accesing a samba server 3.0.4 with an exported folder wich had a linked directory named "web" within the same server to "/usr/local/apache/htdocs". when I accessed that directory I could saw the contents of the destination directory . (fine) After upgrading to fedora core 3 and therefore to samba 3.0.10 I found that the link in the samba folder is broken because it's pointing to a non existen directory in my machine instead of pointing to the directory located in the server. Anyone has any idea of why is this ? and how can i go back to my usual behavior ? Regards, Pablo
>After upgrading to fedora core 3 and therefore to samba 3.0.10 I found > >Who did you upgrade? client or server?>that the link in the samba folder is broken because it's pointing to a >non existen directory in my machine instead of pointing to the >directory located in the server. > >Try looking for the follow symlinks options, they may be your key. -- Paul Gienger Office: 701-281-1884 Applied Engineering Inc. Systems Architect Fax: 701-281-1322 URL: www.ae-solutions.com mailto: pgienger@ae-solutions.com
in reply to this message : http://www.mail-archive.com/samba@lists.samba.org/msg54046.html I have the same problem. I have an old Redhat 7.3 box that I am trying to replace with a FC3 box.. when the FC3 box mounts samba directories the symlinks show up as symlinks ( and are invalid as they point to non-local paths) When the RedHat 7.3 box mounts the same directories, it is unaware that the symlinks are not directories. For years I have accumulated symlinks that files between different projects. So, it's not an easy option to "stop using symlinks" I tried installing the old version of samba on the new machine, ( rpm -U samba-client-2.2.7-3.7.3.i386.rpm samba-common-2.2.7-3.7.3.i386.rpm --force --nodeps ) it complained but seemed to work. But even with the OLD rpms the symlinks still show up as symlinks. I am at wits end. My friend found related link in bugzilla . https://bugzilla.samba.org/show_bug.cgi?id=2008 If that is the problem, is there a quick and dirty trick to make the server think all clients are windows clients? ( clearly not an elegant solution but would solve the current crisis ) -- Russell Polo