search for: ilsf

I've read a few tutorials about how to use rsync via ssh using the command= functionality to restrict where the user can sync to. I've got this on the on the destination side in it's ~/.ssh/authorized_keys... command="rsync --server -vvnlogDtpre.iLsf --timeout=999 . bkp",no-port-forwarding,no-X11-forwarding,no-agent-forwarding ssh-rsa AAetc I've tried variations of the above but I basically get this error... % rsync -avv --delay-updates --delete-after /path/to/files/ remote:bkp opening connection using: ssh remote rsync --server -vvl...

...c should reuse the current copy and not trying to create a copy on the /tmp parition of the NAS. Any hints what might be the problem? Thanks - Ben myhost:~# rsync -avvv /srv/storage rsync at naspy::Backups -P opening tcp connection to naspy port 873 sending daemon args: --server -vvvlogDtpre.iLsf --partial . Backups/ sending incremental file list [sender] make_file(storage,*,0) send_file_list done [sender] make_file(storage/7N-ZDGtCZq01gFJQEd8eqPuiGbumCWtPoje-4KMVfzIFs1,*,2) [sender] make_file(storage/PmjyreYXD0Istwvp-8D6PWA5zeZP1DdbboxuS3xGZphQe1,*,2) [sender] make_file(storage/JKsb9I8-7...

...es confirmation, the is quite terse: "Allow use of key foobar? Key fingerprint abcdf." It would be desirable to have instead a text like: Confirmation is required before allowing usage of key foobar Key fingerprint abcdf. to process 1234 (ssh example.com rsync --server --sender -logDtpre.iLsf) allegedly for "connecting to example.com (1.2.3.4)" The rsync command line would be recovered by the agent itself, thus being quite trustworthy. In this case the example represented a local application. If it was a forwarded request it could be: Confirmation is required before allowin...

...though they are not set on the client side. The client is called like this: rsync -rlptgo -qz --del --timeout=180 user at server /local/path On the server, we have a wrapper script that parses all the options that the client sends, with: options=$(getopt -l server,sender,timeout: -o vnlogDtprzde.iLsf -- $SSH_ORIGINAL_COMMAND) Now getopt keeps emitting errors that the -C and -x options are unrecognised. Is this a recent change in rsync to set these options even if the user hasn't specified them? Regards, Anand

...-checksum is enabled, but isn't normally. Strangely the mtime of the file appears to be different. I don't know why rsync isn't copying it. I'm doing [root at localsys tmp]# rsync -ravv remote:/root/tmp/ ./ opening connection using: ssh remote rsync --server --sender - vvlogDtpre.iLsf . /root/tmp/ receiving incremental file list delta-transmission enabled coolingfit.pro~ is uptodate total: matches=0 hash_hits=0 false_alarms=0 data=0 sent 17 bytes received 141 bytes 105.33 bytes/sec total size is 2963 speedup is 18.75 Here is the file on localsys: [root at localsys tmp]#...

...nc.dirs) cmd=ssh -i /Users/pedrofortunyayuso/.ssh/backup_pfortuny_net machine=pfortuny.net user=pfortuny path=~/backup_mbpro/ cmd[0]=ssh cmd[1]=-i cmd[2]=/Users/pedrofortunyayuso/.ssh/backup_pfortuny_net cmd[3]=-l cmd[4]=pfortuny cmd[5]=pfortuny.net cmd[6]=rsync cmd[7]=--server cmd[8]=-vvvvlogDtpre.iLsf cmd[9]=. cmd[10]=~/backup_mbpro/ opening connection using: ssh -i /Users/pedrofortunyayuso/.ssh/backup_pfortuny_net -l pfortuny pfortuny.net rsync --server -vvvvlogDtpre.iLsf . "~/backup_mbpro/" note: iconv_open("UTF-8", "UTF-8") succeeded. (Client) Protocol versions...

...data/vm/green/data-ll.img root at st1:~# ls -al /data/vm/green/data.img -rw-r--r-- 1 libvirt-qemu libvirt-qemu 375809638400 Mar 26 21:01 /data/vm/green/data.img root at st1:~# ps auxw|grep rsync root 4942 97.3 0.5 120800 83448 ? Rs Mar25 1379:18 rsync --server --sender -vlHogDtpAXrze.iLsf --numeric-ids . / root 8755 0.0 0.0 7836 872 pts/1 S+ 21:02 0:00 grep rsync root at st1:~# strace -p 4942 Process 4942 attached - interrupt to quit ^CProcess 4942 detached root at st1:...