search for: sysmlink

With much hope I upgraded to rsync version 2.5.6 in hopes that it would correct the symbolic link bug I have been wrestling with... No dice. It still insists on dropping the leading slash from a symbolic link outside the source tree. Interactively it still works fine, but as a daemon it's busted. See previous posting 'rsyncd treats symlinks differently' for details. Can someone

On 31/12/15 14:55, Reindl Harald wrote: > > > Am 31.12.2015 um 15:43 schrieb James: >> On 12/30/2015 4:14 PM, Rowland penny wrote: >>> ./configure --prefix=/usr --mandir=/usr/share/man >>> --infodir=/usr/share/info --sysconfdir=/etc/bind --localstatedir=/var >>> --enable-threads --enable-largefile --with-libtool --enable-shared >>> --enable-static

...er structure folder/ folder/existent_file folder/symlink_existent --> existent_file # shows on the osx client folder/symlink_nonexistent --> nonexistent_file # hidden in osx client When I try to remove the folder with `rm -rf` in the osx client it fails, because it removes all files but the sysmlink on the nonexistent file (`rm: cannot remove ?folder/?: Directory not empty`). The folder shows up empty in the osx client, but on the server the symlink is still there. When I switch back to the smb1 protocol by connecting with `cifs://` in the osx client (`smbstatus` shows version `NT1`), the sym...

...der/existent_file > folder/symlink_existent --> existent_file # shows on the osx client > folder/symlink_nonexistent --> nonexistent_file # hidden in osx client > > When I try to remove the folder with `rm -rf` in the osx client it > fails, because it removes all files but the sysmlink on the nonexistent > file (`rm: cannot remove ?folder/?: Directory not empty`). The folder > shows up empty in the osx client, but on the server the symlink is still > there. > > When I switch back to the smb1 protocol by connecting with `cifs://` in > the osx client (`smbstatus`...

...der/existent_file > folder/symlink_existent --> existent_file # shows on the osx client > folder/symlink_nonexistent --> nonexistent_file # hidden in osx client > > When I try to remove the folder with `rm -rf` in the osx client it > fails, because it removes all files but the sysmlink on the nonexistent > file (`rm: cannot remove ?folder/?: Directory not empty`). The folder > shows up empty in the osx client, but on the server the symlink is still > there. > > When I switch back to the smb1 protocol by connecting with `cifs://` in > the osx client (`smbstatus`...

...named - >> > > I have checked and all I did after compiling bind9 was to provision > samba4, setup bind with samba and then started bind and samba. > > Rowland > > I'm going to update my distro and see what happens. As a FYI Ubuntu 12.04 seems to treat /var/run as a sysmlink. lrwxrwxrwx 1 root root 4 Dec 31 10:06 /var/run -> /run -- -James

Hello, I want the C drive to be pointing to /usr/share/wine-c instead of ./drive_c by default, without modifying in the config file. That is on typing the command "wine" itself , "dosdrives" in .wine directory should contain the symlink to /usr/share/wine-c for "C" drive. Where should I edit for that, so that i get the C drive pointing to /usr/share/wine-c by

Hi, After I have updated my SAMBA AD environment from version 4.9.18 to version 4.10.12 on my secondary server the program is unable to start and displays the following error message:"ERROR:failed to setup profiling". The testparm result didn't print any warning or error. System details: CentOS Linux release 7.7.1908 (Core) with kernel 3.10.0-1062.9.1.el7.x86_64 smb.conf