similar to: Feature request

While uploading a file via SFTP, the file which is being overwritten is done so in real-time rather than waiting until the transfer has finished. In other words, if it takes you 60 seconds to upload the new file, the old file is unusable for a period of 60 seconds. This is a major problem if the file you are overwriting, for example, is a server script which is accessed hundreds or thousands

I'm trying to rsync files to a set of symlinked directories on an XServe running OS X. The directories look like this: tna@csx:~/2/2006$ l total 80 lrwxr-xr-x 1 tna tna 39 Feb 24 13:18 2006-01 -> /Volumes/CSArchiveArray001/2006/2006-01 lrwxr-xr-x 1 tna tna 39 Feb 24 13:18 2006-02 -> /Volumes/CSArchiveArray001/2006/2006-02 When I run rsync from Linux in --dry-run mode,

I'm trying to understand how to properly setup the /etc/rsyncd.conf file to run an rsync daemon with a secrets file specified in a module - the rsync.conf manpage does not spell it out clearly enough. Rsync server is rsync-2.5.6. If this is my /etc/rsyncd.conf file: ------------------------------------ log file = /var/log/rsync uid = root gid = root [test] uid = rsync1 gid =

Greetings. Currently, the --one-file-system applies to both the source and destination and this is a problem. In my source, I have a symlink pointing to a directory on another device which I would like to have copied. I thus use --copy-unsafe-links. I also use --delete. This is dangerous because if there is a bug in my script, I would not like the destination to become suddenly

I put them on the wiki page, but I'm not sure if they're read often or whatever. a - Sqlite support I know its been talked about, but it wasn't on the request/todo page until i threw it on there, so i wanted chime in for it as well b - User configurable ports ports are hardcoded in the c source file. it would be nice if these were the defaults, and could be

Unlink files, symlinks, FIFOs, devices etc. (except directories) before writing them when extracting CPIOs. This stops weird behaviour like: 1) writing through symlinks created in earlier CPIOs. eg foo->bar in the first CPIO. Having foo as a non-link in a subsequent CPIO, results in bar being written and foo remaining as a symlink. 2) if the first version of file foo is larger

Hello! I need a suggestion. How to copy broken symlink as symlink with rsync? Example: # mkdir src # ln -s file-that-doesnt-exist src/broken-link # rsync -a src/ dst/ # ls -l src/ total 0 lrwxrwxrwx 1 root root 22 Dec 16 10:31 broken-link -> file-that-doesnt-exist # ls -l dst total 0 I want src/ and dst/ to be identical after sync. -- WBR, Yakov Hrebtov

Hi, We use rsync to share data between two remote sites. We are using rsync after configuration of the rsync.conf file. I created a module in the file with the relevant entries and permissions. The problem is that I get "connection refused ", when I try to run rsync in the following way: root@rsync1-mpg:/root# rsync ptsinf01.pt.intel.com:: rsync: failed to connect to

Rsync maintainers please review rsync bug https://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=98740 The code in question is in socket.c in start_accept_loop. The user is getting these warning messages:

I have a simple script that sends one file to two locations on the same destination server. Here's the code: DEST="remotehost" SRC="/home/boss/application.conf" DST1="/home/user1/application.conf" DST2="/home/user2/application.conf" RSYNC1=`rsync -caW -e ssh $SRC $DEST:$DST1` RSYNC2=`rsync -caW -e ssh $SRC $DEST:$DST2` This runs every 5 minutes. What

Dear all, I have enhanced scp to do the following. 1) Check the SHA1 checksums of the file fragments at the source and destination and resume file transfer from where it left off last time 2) If the file checksums match and size also matches, then the file is assumed to be identical and skipped, the user is also informed of the same 3) If the destination file size is larger than the source,

Hi all, I want to run 2 rsync daemons on my system. Each has its own configuration file, and they are listening on a specific port. These 2 daemons are running perfectly but getting them started by 2 init scripts is a bit more difficult. The problem is that when stopping rsync you check the pid of rsync, which results in both pids of the daemons. Off course i want the script to be very

Hi. I found and reported a bug about a year ago regarding symbolic links but haven't seen any mention of it since and it is still present in 2.6.1-pre2. Just want to make sure it isn't forgotten. It can be reproduced by synchronizing two directories, one of which contains a normal file and the other has a symlink of the same name. With the archive, update and backup options set, rsync

I've noticed the following behavior on files that are overwritten with an scp command and I can't decide if this is intended behavior or a bug? Can someone with a little more insight please share the reasoning for this (if any)? I've tested this with a mix of 3.4p1 and 3.5p1 hosts. Suppose we have 2 files on different hosts, with different group ownership and permissions. user1 is not

For the last few system builds, I've noticed that the variable in /etc/make.conf NO_MAILWRAPPER=true is being ignored, resulting in my sendmail (different than stock version) being overwritten. This applies to 4.8-STABLE; is this a known issue.

I'm new the the PAM world and have CentOS 5 64-bit installed on a system. I want to tweak some of the system-auth module settings, but the top of the file says anything configured in that file will get overwritten, as it is autogenerated by authconfig. I checked out authconfig, and it doesn't seem clear to me how to make the changes I need via authconfig. So, where do I need to look?

The following patch unlinks (deletes) files, symlinks, FIFOs, devices etc before writing them when extracting CPIOs. It doesn't delete directories. This stops weird behaviour like: 1) writing through symlinks created in earlier CPIOs. eg foo->bar in the first CPIO. Having foo as a non link in a subsequent CPIO, results in bar being written and foo remaining as a symlink. 2)

Systemd service files are generally coming with packages. This means these files can be overwritten by some system update if this updates also your Samba packages (note: I never had nor tested that behaviour with Samba packages, but it happens for other packages). 2016-02-23 8:39 GMT+01:00 L.P.H. van Belle <belle at bazuin.nl>: > Uh... just add : > > netbios name = PC_NAME >

OpenSSH still has this feature, SSH-1.2.27 no longer has it. Admittedly it can be useful sometimes, even though I'd prefer this to be done using a trivial shell wrapper, which would be the UNIX way of doing things. Not being able to call OpenSSH's ssh by another name (say ``ssh1'') can get in the way when having to maintain two versions of ssh in parallel because the ``ssh ->

I'm copying a partition that has a bunch of hardlink based snapshots (-aPH). I think there's about 250,000 files in each backup and between 100 and 200 snapshots. Earlier today, I saw the files had completed and it was making all the hardlinks. I thought it would be "not long" but it's been making hardlinks for 12 hours (at least). There's only 36Gb in snapshot, the