search for: symlinked

Hi all. I long time discover strange to me behavior. If I add --fake-super option on both sides rsync start always set owner and group of symlink. What interesting there no error, but it done each time as it has been changed. Simple reproduce: $ mkdir rsync.symlinks $ echo 'file content' > rsync.symlinks/file.itself $ ln -s file.itself rsync.symlinks/file.symlink Then try to transfer

As mentioned in another thread, I notice that the params used to control symlinks feel a bit inefficient and inelegant, and quite limited. I think there might be a good opportunity to simplify and also make their management in Samba more powerful and adaptable to use-cases. I'm guessing this list is a good enough starting point to propose a smb.conf param change to this area and see what

Processing commands for control at bugs.debian.org: > tags 496359 security Bug#496359: The possibility of attack with the help of symlinks in some Debian packages There were no tags set. Tags added: security > tags 496360 security Bug#496360: The possibility of attack with the help of symlinks in some Debian packages Tags were: confirmed Tags added: security > tags 496362 security

https://bugzilla.samba.org/show_bug.cgi?id=12820 Bug ID: 12820 Summary: rsync always try change owner and group of symlink in --fake-super mode Product: rsync Version: 3.0.9 Hardware: All OS: All Status: NEW Severity: normal Priority: P5 Component: core

...to symlinks via 'setfattr -h -n security.NTACL -v ... [file]' and hoped it would be evaluated for the symlink by samba - that doesn't seem to be the case. As dfs-symlinks are resolved by the client, the linked share's rights could only be checked after resolving and accessing the symlinked share by the client. To hide the symlink from the client, the server would have to resolve the symlink or evaluate some ACL on the symlink before (as mentioned above). I'd be grateful for ideas thanks -- M. Sc. Konrad Jacobi Fraunhofer-Institut f?r Gro?strukturen in der Produktionstechn...

ln -s real-file symlink file.itself is ./rsync.symlinks/file.itself, but you are trying to link ./file.itself (which presumably doesn't exist) to the real file. Since a symlink is just a pointer, it gets created, but doesn't point to any real file. Try: ln -s rsync.symlinks/file.itself . Joe On 10/11/2015 06:17 AM, Pavel Alexeev wrote: > Hi all. > > I long time discover

Hi, I would appreciate someone testing if their system can recognize symlinks (as below) on their SMB share. My Mac and Windows machines can NOT recognize symlinks on my NAS's SMB share, they just identify symlinks as real files and folders. Why is this an issue? Because when I try to copy parts of these backups from the NAS it just loops back on itself forever. Eg: From NAS (QNAP TS-453A)

I have a couple of samba shares that point to symlinks. Basically these are last night's copy of a bunch of data. The path changes every night (YYMMDD is in the path name), so I've just got one symlink that gets updated to the path with the latest date every night. I was using an old Samba on OpenSolaris for a long time and this process was working. Using 3.6.23 on RHEL and although

Hi list, Is there a configuration for gluster to have symlinks working with gluster nfs exports? When I try to create a symlink on a glusterfs nfs mount I get: ln: creating symbolic link `test' to `httpdocs': Unknown error 526 From nfs.log: [2012-02-18 01:27:27.541155] E [client3_1-fops.c:173:client3_1_symlink_cbk] 0-dcm-gluster-backup1-client-0: remote operation failed: Operation not

https://bugzilla.samba.org/show_bug.cgi?id=11558 Bug ID: 11558 Summary: rsync always try change owner and group of symlink in --fake-super mode Product: rsync Version: 3.1.2 Hardware: x64 OS: Linux Status: NEW Severity: normal Priority: P5 Component: core

I have a laptop and desktop that have most of home directory data sync'd, but I am having trouble keeping symlinks straight. On the desktop, my data is separate from the $HOME folder... $HOME = /remote/home/desktop/ and the data is at /data/. Within /data/, I have several directories that are inter-related... eg, /data/pub1/figs is a link pointing to /data/imgs/pub1. It makes life easier

When you say “real symlinks on OSX” do you mean an “alias” that Finder would create? Or a Unix-type symlink using the “ ln -s file link” command in Terminal? A Finder alias is not the same as a Unix-type symlink. My NAS runs Debian Linux with version 4.3.11 of smbd; my clients are all OSX Mojave. If I create an alias using Finder on the NAS, it behaves like a normal alias in OSX UNLESS I move

Hi Team, Trying to upgrade samba 4.9.3 on debian wheezy. while building facing the following error. Build phase! ` Configuring Samba 4 - x86_64 Checking for program gcc or cc : /usr/bin/gcc Checking for program cpp : not found Checking for program ar : /usr/bin/ar Checking for program ranlib : /usr/bin/ranlib Checking for gcc

I''m running 2.6.6 on a red hat EL3 system. using the following command, rsync -rlptDvzL --stats --include=a/ --include=a/dir/ --include=a/dir/symlink/ --include=a/dir/symlink/dir2/ --include=a/dir/symlink/dir2/dir3/ --exclude=''**'' /export/stuff remote::stuff I expect the "symlink" (which is really a symbolic link to a directory) to be preserved on the

Hi e, I am normally use gnome and would do the following to make my CD / DVD mount with exec gnome-mount --write-settings --device /dev/sdc0 -o exec What is the equivalent in KDE ? My initial research suggests that I actually have to write a custom udev rule to achieve this. This has led me as far as running udevinfo -q path -n /dev/scd0 udevtest /block/sr0 (the output is below) My

Hi! I am using rsync succesfully to maintain my mirrors. I have one problem, tho. To improve speeds of my filesystems, I have created a raid 0 of 4 disks, and I place the most heavily copied disks there. The fs has subdirectories, one for each set of typically .iso files, such as Mandrakelinux or fedora. I would like to be able to just do a symlink from the original tree to the directory on the

>>>>> Jeroen Ooms <jeroenooms at gmail.com> >>>>> on Wed, 20 Jul 2016 10:26:19 +0200 writes: > On Tue, Jul 19, 2016 at 6:46 PM, Kevin Ushey <kevinushey at gmail.com> wrote: >> R fails to install a package from source over a pre-existing package >> when the path to that package is a symlink, rather than a directory.

Hello! I'm having problems with udev /dev/tape/by-id/ symlinks.. it seems symlinks to tape drives are sometimes (randomly) missing after reboot. Server in question has IBM TS3200 tape library connected with 2 drives in it.. so /proc/scsi/scsi shows 3 devices: 2 tape drives, and 1 medium changer (tape library). So I should have 3 symlinks in /dev/tape/by-id/ directory.. 2 symlinks to tape

After a manual fix I have that, too. Point is that for historic hosts this symlink doesn't exist. The upgrade fails due to dbus becoming unavailable. And the next reboot fails, too, because the symlink is not created automatically. Can you confirm this? Regards Harri

I mean a Unix-style symlink as if created by "ln -s file link". > If I create Unix symlink, Finder will open the file UNLESS I move the linked file - in this case Finder CANNOT find the original file - the symlink is broken . In my case the Finder is able to open symlinks, this is not the problem. The problem is that they are real normal files from the point of view of a client