I'm using SAMBA for many years, in my SOHO - I'm quite satisfied. One small question is up every time when I'm creating a symlink on the SAMBA server box from a share to point to a moint point for example /mnt/some_block_device (of course read/writable for particular user), windows cleanly "see" it, as a directory entry - I c?an copy/remove do everything what could be done on the share. When I'm using the same share on a Linux box (I'm a Debian lover) it's seen as a broken symlink! This is the normal behavior? Can I change it some way? tovis
do you have follow sym links = yes in smb.conf? tovis wrote:> I'm using SAMBA for many years, in my SOHO - I'm quite satisfied. > One small question is up every time when I'm creating a symlink on the > SAMBA server box from a share to point to a moint point for example > /mnt/some_block_device (of course read/writable for particular user), > windows cleanly "see" it, as a directory entry - I c?an copy/remove do > everything what could be done on the share. When I'm using the same share > on a Linux box (I'm a Debian lover) it's seen as a broken symlink! > This is the normal behavior? Can I change it some way? > > tovis > > >
tovis wrote:> I'm using SAMBA for many years, in my SOHO - I'm quite satisfied. > One small question is up every time when I'm creating a symlink on the > SAMBA server box from a share to point to a moint point for example > /mnt/some_block_device (of course read/writable for particular user), > windows cleanly "see" it, as a directory entry - I c?an copy/remove do > everything what could be done on the share. When I'm using the same share > on a Linux box (I'm a Debian lover) it's seen as a broken symlink! > This is the normal behavior? Can I change it some way? > > tovis > >If you are mounting using CIFS, then unix extensions are probably being enabled. As a result, things that samba would normally hide (such as symlinks) are being sent for the client to sort out. If the symlink points to somewhere else inside the share, you could look at using relative instead of absolute links, or you could disable unix extensions. *Michael Heydon - IT Administrator * michaelh@jaswin.com.au <mailto:michaelh@jaswin.com.au>
First suggestion - hardlink - I do not know how to do it on Debian system (Sarge - oldstable). The system doesn't allow this :( "follow symlinks" option is enabled by default - I do not disble it. By the way I'm tried to put it in my smb.conf - in share [homes] and in [global] - also change this in smb.conf of clients - but nothing was change :( windows/DOS clients are follows symlinks but Linux clients not. Linux clients shows that the symlinks points to nowhere - the points are doen't exists on client box(es) - obviously.