similar to: Following directory symlinks across partitions

Hi samba list, I am seeing a peculiar issue when sharing out a directory containing a soft symlink pointing to a directory outside of the share and a different filesystem/block device. i have 2 shares: [share1] read only = No follow symlinks = yes wide links = yes /media/stor0/user [share2] /media/stor1/user /media/stor0 is an xfs filesystem /media/stor1 is an xfs filesystem there is a folder

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 We had 3.0.2a which worked fine. If you tried to open a file that the ACLs wouldn't let you, you'd get access denied. We had follow symlinks=no in smb.conf Now with 3.0.8, and no other changes, we get a message about "The file has moved or otherwise gone away," instead of access denied. And we get this in the log file: [2004/11/16

I'm struggling with following symlinks with samba on the recent versions. I cannot use mount -bind as I've seen others suggest. This is for my mythtv backend, so I'm using the rename script to create nice names for the recordings. Anyway, I can map the drive from Windows XP and Windows 7, and see symlinked files, but I cannot open or copy them as I used to be able to do. My

Hi! I run Linux Gentoo 2.6.28 with Samba 3.0.28 installed. In one of the shares there is a number of symlinks pointing to the folders found on different logic partitions of the drive. When I move a large file (some gigabytes) with a Windows client from one folder to another (which are symlinks to different partitions), after some time the system offers to overwrite the file with the same name but

Dear all, I am trying to synchronize data from a remote machine (ssh) to my local one using rsync (pure scp would overwrite everything every time). The problem is, however, that due to the size of data and available storage, I have to distribute it over several hdd's. For that I have a script, which moves every single file (typical size ~ 4GB) to a different (randomly selected) hdd, leaving

This mail message follows from several discussions with Luke Leighton. It's mostly technical in nature but I'm submitting to all mailing lists anyway (Luke's suggestion). We have our Samba server running with the Berkeley AMD automounter (nothing peculiar here). In order for our Samba users to walk the automount tree, we created a program to create symbolic links from the local

Hello, I am using samba in a heterogeneous UNIX/NT environment. Samba exports file systems that contain many symlinks. My users want to access the symlinked files from windows explorer, i.e. the symlinks need to be followed by samba. For security reasons, symlinks pointing to locations outside the share must not be followed. According to the samba documentation I have to set these parameters in

After receiving requests to post answers to this query, I figured I'd resubscribe to let people know that there is, in fact, a way around this. When I upgraded johnboy to Linux kernel version 2.6.10, all the formerly problematic symlinks worked. Apparently, the 2.6.10 kernel fixed some issues in the smbfs code relating to symlinks (thanks to Ted McManus for pointing this out to me). So if

Hi all, I've encountered a problem in using Samba 3.0.4. I've got a Red Hat 7.3 box (johnboy) running as a domain controller, and we've got symlinks to a bunch of NFS mounts on a different machine (pawalton) to give people the necessary file access using only one SMB mount. For example, the SMB share is under /smbfiles in the root directory of the Samba server. Within /smbfiles,

Hello, Samba version: 3.5.6, OS CentOS 5.5 64-bit. The problem: I have a share with symlinks leading outside the share. After mounting the shared resource (cifs), I can't proceed through symlinks (permission denied). Setting options follow symlinks = yes wide links = yes for the share doesn't change Samba behaviour. Could someone enlighten me on how to handle this? Thanks.

https://bugzilla.samba.org/show_bug.cgi?id=13569 Bug ID: 13569 Summary: --link-dest may follow symlinks and failure to hard link a non-regular file is fatal Product: rsync Version: 3.1.3 Hardware: All OS: All Status: NEW Severity: normal Priority: P5 Component: core

Hi, I am quite new to R - but quite expierience in programming. Nonetheless I have some problemes in accessing information of the "summary" object. Here is what I do: model <- lm ( y ~ myVariable ) "summary(model)" gives me an object which has a lot of information about the regression. Now I'd like to access programmatically the level of significance which is

Brendan, Unless I am seriously mistaken, I believe that by adding this 'wide links = no' to each share section will end the ability to create and use symlinks on your shares. I am unsure why anyone would want to really include symlinks into a Samba share. Does anyone care to enlighten me? Regards, Robert Adkins II IT Manager/Buyer Impel Industries, Inc. Ph. 586-254-5800 Fx.

A while back I got some good advice about using bind-mount on my Linux server to include directories outside my Samba shares. It had been years since I set up a server and forgot about "follow symlinks" and stumbled on that yesterday. Is there a reason for using one of these over the other one? Hal

A minor issue, but I''m seeing that when we generate a application skeleton using the "rails" command, the generated script files follow the symlink of our ruby installation. On our machines, ruby is installed under /usr/pkg/ruby/ruby182/ with a symlink /usr/pkg/ruby/ruby -> /usr/pkg/ruby/ruby182/ Our sysadmins like using the symlinks as a way of managing the

Hi all, I have a samba 3 server, and I want my users from Linux to access shares on this server (like everybody:) ) . I have these directories : user1_dir for user1 user2_dir for user2 share for all On the server, I have this directory structure : /home/users/user1_dir /home/users/user2_dir /home/data/share I have a symbolic link in user1_dir and in user2_dir pointing to

Hi, I can't figure out how to backup a tree with symlinks. I either get errors like rsync: open(rc2.d/S20inetd) failed!!: No such file or directory (2) or (with --safe-link on the client and "munge symlinks = yes" on the server): ignoring unsafe symlink "/etc/rc2.d/S20inetd" (in backups) -> "/rsyncd-munged/../init.d/inetd" What I am trying to do is

Is there any way to specify in smb.conf that you don't want to follow symbolic links, or to somehow disable this in smbclient? I have an smb file indexer, and whenever it hits a linux box with a symlink pointing to the current directory, it creates thousands of extra entries. I'd like to be able to simply not follow symbolic links, as I have no way of disabling the "follow

Hi, following the instructions on https://bugzilla.samba.org/createaccount-save.html, I've applied for a bugzilla account at bugzilla-maintenance at samba.org but didn't receive a reply, so I report through this list. With --link-dest the search for a candidate to link from, follows symlinks in directory path components, when the path element is a directory in the source tree but a

hey all 'scp -r ' follows symlinks. IMO this is a bug and should be changed - it: a) hampers the use of scp. As it stands, I cannot use 'scp -r' because of this behavior. If someone links to '/', or if I hit a recursive symlink, I'm screwed. b) It is inconsistant with cp. When you 'cp -r' on a file, it does NOT follow the symlink. When you scp