Erik writes: > I am not sure if this is intended behaviour, but it certainly is not > expected. If would expect those rules to accumulate, having rules with * > as a key to apply to all shares -- making it easy to always for instance > exclude temporary directories -- on top of rules specific for a share.
The rules don't accumulate. "*" means default, and is used only if the share isn't explicitly specified. You interpretation is probably more intuitive, but unfortunately that's the way it is. > By the way, I also think it would be nice if backuppc could apply some > magic to make definitions uniform. Right now, an rsync share must be > entered as /home, whereas the same share as an rsyncd module, would be > entered as home. As on Samba. Maybe backuppc could translate home to > /home for rsync. I've tried to make them consistent, but this is a general issue - for example, the specifics of excludes and includes are different for different XferMethods. For the case you mention, I believe it makes the most sense as it is. For rsync the share really is a directory path (eg: /home or /home/user). Specifying "home/user" isn't very intuitive. For rsyncd it is whatever you name the module in rsyncd.conf. I'm not sure if "/home" is allowed as a module name (it probably isn't), but if it is you could take that path to make them consistent. Craig ------------------------------------------------------------------------- This SF.net email is sponsored by: Splunk Inc. Still grepping through log files to find problems? Stop. Now Search log events and configuration files using AJAX and a browser. Download your FREE copy of Splunk now >> http://get.splunk.com/ _______________________________________________ BackupPC-users mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/backuppc-users http://backuppc.sourceforge.net/
