similar to: How do you exclude a directory that is a symlink?

The directory I'm trying to copy from is: /home/blah/dir The symlink is /home/blah/dir/unwanted_symlinked_dir On Fri, Mar 3, 2017 at 8:10 AM, Paul Slootman <paul+rsync at wurtel.net> wrote: > On Fri 03 Mar 2017, Steve Dondley wrote: > > > I'm trying to rsync a directory from a server to my local machine that > has > > a symbolic link to a directory I don't

Considering you cant INCLUDE a directory that is a symlink... which would be really handy right now for me to resolve a mapping of 103 -> meaningful_name for backups, instead im resorting to temporary bind mounts of 103 onto meaningful_name, and when the bind mount isnt there, the --del is emptying meaningful_name accidentally at times. I think both situations could benefit from a

Hi, I wanted to use a symlink in a share, but it didn't work. I tried it on Samba 4.10. I thought that follow symlinks = yes is enough (and it is default). I googled about it, and found a solution: unix extensions = no in the global section, and wide links = Yes follow symlinks = yes in the shares' section. According to the man, unix extensions = yes is the default, but the samba-tool

I have a share with a couple of symlinked files in it. On a Samba server, it looks like this for "addon" directory: # ls -l (...) acrobatreader7 (...) addon -> /home/samba/unattended-write/packages Now, if I mount it on a Linux client using smbmount, symlinks point to non existing directories locally (/home/samba/unattended-write/packages exist only on a Samba server): #

>>>>> 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.

https://bugs.freedesktop.org/show_bug.cgi?id=99913 Bug ID: 99913 Summary: [G96] Reclocking fails on voltage Product: xorg Version: unspecified Hardware: Other OS: All Status: NEW Severity: normal Priority: medium Component: Driver/nouveau Assignee: nouveau at

Hello! I just joined the list and will be happy to help where I can in my limited experience, but also come to the table with a question. I think there's something I'm missing regarding shared mailboxes and ACLs, so I will describe my situation and see if I am understanding correctly (running Dovecot 1.1.10). I have read over the Dovecot Wiki many times and have scoured many forums but

Hi to all, i have dovecot 2.2.5 when i digit doveadm who i see a lot of connections IMAP for single user liker the example below xxxxx.yyyyyy at mail.cgilfe.it 9 imap (20572 20614 19120 20653 19136 20655 19138 20661 20471) (192.168.x.xxx) Why so many IMAP? -- *Davide Marchi* *T*eorema *F*errara *Srl* Via Spronello, 7 - Ferrara - 44121 Tel. *0532783161* Fax. *0532783368* E-m at il:

Hello, I think this should be reported on bugzilla. Can someone do that for me? I read these error messages: "cannot delete non-empty directory: path/to/dir could not make way for new symlink: path/to/dir" (on last , dir is a symlink) upon rsync -a --backup --backup-dir=../part.inc/06 --links --partial-dir=.rsync.part --partial --progress --log-file=/mnt/x/Documents/rsync.a.log

Hello to all !!! I have some issues with some users that login to the same account through imap from many devices like: mobile,desktop/tablet !!! Issues like: 1. When a new email is arrived is not appearing to all devices... 2. New email is arriving to some other devices after a long period of time ... Generally issues like that .... Does anyone have an idea of how to solve this ..?

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

https://bugzilla.mindrot.org/show_bug.cgi?id=3600 Bug ID: 3600 Summary: please make ssh-keygen symlink aware for proper handling of hosts removal in symlinked known_hosts Product: Portable OpenSSH Version: 9.3p2 Hardware: amd64 OS: Linux Status: NEW Severity: enhancement

Hi everyone, I have deployed a rails tumblelog site via capistrano, but have run into a problem. What I am wanting to do is this: In my deployment script create symlinks from the public directory so that the images directory points to a shared images directory. Reason being is I am adding an image upload to the site (not file_column) and need to easily add the uploaded images and thumbs into

When CONFIG_EXT3_FS_POSIX_ACL is not defined, ext3_init_acl() is an inline function in fs/ext3/acl.h which doesn't check if a file is a symlink before applying umask. I've always liked my acls to be available (so never noticed), but came across this recently when trying to explain why RedHat Enterprise 3's BOOT kernel creates symlinks 755 during kickstart. I'm *assuming* this is

Hi, in my backup script I'm using the "-L" option to transform symlinks into referent files/dirs. Now I'm also using the "--delete" option. Unfortunately "--delete" doesnt work if an error like "Symlink has no referent" occurs. So far the only solution for that seems to not use the "-L" option or to add "--ignore-errors". It

We need to check for "$diver-$suite" not just "$diver" now Also when creating the current symlink only do so if mg-debian-installer-update did something, since it will now silently ignore unavailable combinations (e.g. armhf on Squeeze) Signed-off-by: Ian Campbell <ian.campbell@citrix.com> --- standalone-reset | 8 +++++--- 1 file changed, 5 insertions(+), 3

Dear Lustre Administrators, Starting with the next minor release of Lustre, version 1.4.9, we are removing the backwards-compatible /proc/sys/portals symlink due to a conflict with Cray portals /proc debug on XT3. Before upgrading to 1.4.9, please ensure that you change any configuration scripts or /etc/sysctl.conf files that access /proc/sys/portals/* or sysctl portals.* to use the

Dear Lustre Administrators, Starting with the next minor release of Lustre, version 1.4.9, we are removing the backwards-compatible /proc/sys/portals symlink due to a conflict with Cray portals /proc debug on XT3. Before upgrading to 1.4.9, please ensure that you change any configuration scripts or /etc/sysctl.conf files that access /proc/sys/portals/* or sysctl portals.* to use the

Dear Lustre Administrators, Starting with the next minor release of Lustre, version 1.4.9, we are removing the backwards-compatible /proc/sys/portals symlink due to a conflict with Cray portals /proc debug on XT3. Before upgrading to 1.4.9, please ensure that you change any configuration scripts or /etc/sysctl.conf files that access /proc/sys/portals/* or sysctl portals.* to use the

With R 2.15.2 patched (2012-10-29 r61044) and R devel (2012-10-29r61044) on **Windows 7 w/ NTFS ** running in admin mode, I get: EXAMPLE: > cat("Hello world", file="foo.txt") > file.exists("foo-lnk.txt") [1] FALSE > res <- file.symlink(from="foo.txt", to="foo-lnk.txt") > warnings() NULL > res [1] TRUE >