similar to: --backup-dir and daemon mode

Hi, As far as I can tell, after version 2.6.4, the "--daemon" and "--temp-dir" options are not compatible anymore. Previous versions allow this. We use this heavily at my site. Is this an intentional change or bug? My command to start the daemon is this: /usr/local/bin/rsync --temp-dir=/.rsyncd-spool --daemon Thanks, -Eddie

I'm having an issue with the --suffix and -b flags - I've tried the following commands: rsync -avbr --backup-dir=/rsyncbackup rsynctest user@server.com::module rsync -avbr --backup-dir=/rsyncbackup --suffix="" rsynctest user@server.com::module and either way, I wind up with a tilde as a suffix on all the files moved into the backup directory at time of synchronization.

Rsync counts directories as files when it's creating the file list, but does not count them as files in the "files transferred" statistic. Example output from my backup logs, when initializing a new backup volume (rsyncing a set of data to a completely empty filesystem): [2004-07-09 03:03:37] - Number of files: 75007 [2004-07-09 03:03:37] - Number of files transferred:

It occurs to me that it would probably avoid a LOT of newbie confusion if instead of "bytes written" and "bytes read", the stats said "bytes sent" and "bytes received". Anybody who doesn't know better intutively tends to grasp "bytes written" as what got written *to the hard drive* rather than what got sent over the pipe. Jim Salter JRS

A couple of ideas about things that would be nice to see in rsync: 1. a "0.5v" option - something that would just show a progress either by file or by megabyte, ie "processing file 1,048 of 9,032" or "processing: 832 of 3,459 MB". The standard "verbose" is good for troubleshooting, but it's not very useful for gauging how much has been done and how

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Please cc in replies as I am not subscrubed to the list - However I have just searched backwards over the list archive looking for an answer and I can't find any posts relating to this. I am currently backing up my family's windows machine over the network to my linux box by mounting the windows disk as a file share an using cp to copy

Hello all - I am running rsync 2.5.6 on two FreeBSD 5.0 machines. I have experimented with running rsync using ssh, with command lines like the following: rsync -rv --progress jimbo@192.68.100.10:/usr/share/smbshare /usr/home/jimbo And also with running rsync as a daemon on the master server, and syncing to it from the other machine like so: rsync -rv --progress 192.168.100.10::test

Hi everybody - I'm trying to write a Perl wrapper for some rsync tasks that need doing. Problem is, there's some sort of odd interaction going on between Perl and the daemon mode communication for the rsync client, and I'm at my wit's end in trying to figure it out. Here's the Perl script: #####################################################

Hi All. Since it's a lengthy one to explain, I'll jump right into my issue: I run rsync on 3 debian systems for the purpose of backing up approximately 500GBs of various types of data. The general strategy is two systems hold full backups and the third holds incremental's using date-based --backup --backup-dir=. The directory in question is an NFS mount. Here's the problem:

Consider following directory structure: > mkdir -p src/empty tgt bkp when making an initial backup with > rsync -r src/ tgt then the empty directory in src will be copied to tgt. However, if the directory is removed from src > rmdir src/empty and rsync is run like > rsync -r --delete -b --backup-dir=../bkp src/ tgt/ then the empty directory does end up in bkp. I am using

Hello Samba list - I have been using Samba for about a year now, on FreeBSD 4.x and 5.x servers. It works flawlessly, except for one thing - the manipulation of directory permissions via the Win2K native interface. I can manipulate permissions on FILES just fine from the Win2K interface, and if I am using FreeBSD 5.x with ACL support, can even create and manipulate true ACLs using the Win2K

(accidentally sent directly to Larry the first time - cross-posted to list after-the-fact in case someone else finds it useful) > I hope to manage rsync access the same way. Clients would be > forced to come in via SSH (because no other ports are open), and > once in, the configuration of rsync will determine what they can > do, precisely. This is just a hope at the moment

For some reason when using -owner -group my files end up being nobody:nobody on the destination..? This is Solaris 9. Jeremy S. Loukinas

Dear List, Currently, I'm trying to implement a new feature to rsync. Delta back: Well, it simply just backups diff blocks, and the program is able to restore to any backup points. Current problem met for adding files! But I met a newbie problem here. I'm going to add six files, which are diff.h/diff.c del.h/del.c and merge.h/merge.c. I have modified Makefile.in. When I add an

https://bugzilla.samba.org/show_bug.cgi?id=2758 wayned@samba.org changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |ASSIGNED ------- Additional Comments From wayned@samba.org 2005-06-07 10:49 ------- Yes, this particular problem started in 2.6.4 because

I have tried to compile 2.0.4b and 2.0.5a on AIX3.2.5 and it gives a problem when I test it with "smbclient -L bigserver", that was discussed in the archives. I thought it was fixed. It gives:- [1999/07/22 20:57:05, 0] smbd/uid.c:(68) Couldn't set effective uid to 207. Currently set to (real=0,eff=0). Error was Not owner [1999/07/22 20:57:05, 0] smbd/service.c:(463) Can't

Maybe nice to share some details? -----Original Message----- To: Marc Roos; dovecot Subject: Re[4]: Lightweight LMTP daemon to avoid overkill MTA I ended up 'hacking' LMTP support into the external spam filter. Someone else already contributed 'real' patches to implement LMTP support, so once I go live with this mail platform it should be stable. Met vriendelijke groeten,

================================================= This is an automated summary of the status of the R-bugs repository. Note that this may be neither complete nor perfectly correct at any given instance: Not all bugs are reported, and some reported bugs may have been fixed, but the repository not yet updated. Some bug fixes are difficult to verify because they pertain to specific hardware or

================================================= This is an automated summary of the status of the R-bugs repository. Note that this may be neither complete nor perfectly correct at any given instance: Not all bugs are reported, and some reported bugs may have been fixed, but the repository not yet updated. Some bug fixes are difficult to verify because they pertain to specific hardware or

I ended up 'hacking' LMTP support into the external spam filter. Someone else already contributed 'real' patches to implement LMTP support, so once I go live with this mail platform it should be stable. Met vriendelijke groeten, William Edwards T. 040 - 711 44 96 E. wedwards at cyberfusion.nl ? ----- Original Message ----- From: Marc Roos (M.Roos at f1-outsourcing.eu) Date: