search for: jrssystem

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

Hello all, I am having a problem with rsync. I want to backup data from one machine to another remote machine. I have Freebsd4.7 on source and FreeBSD4.9 on destination machines. rsync is installed on both the machines. I gave the following command at the source machine. rsync -avvznrbe rsh /sourcepath 66.123.34.123:/destinationpath (66.123.34.123 is the destination ip address) Below is the

I'm trying to use rsync under Cygwin on 2 machines running Windows 2000 Server There's a 2MB link between them and I'm using SSH setup for a passwordless connection rsync hangs part way through transfers and when run again hangs at the same place in the same files with no explanation no matter what verbosity level I set it to. Each time it hangs it leaves an rsync process running on

(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

Has anybody else noticed cygwin.com and sources.redhat.com being down? The machine that answers to those addresses (and sourceware.org) is refusing HTTP connections, and has been for at least 48 hours now. Anybody here know anything about it? I haven't been able to find out diddly-squat about it on the web... -J

Is it possible to use --backup-dir= with a daemon mode target? I have been attempting to use --backup and --backup-dir= with a daemon mode server I use as target for an rsync command that "pushes" from the server needing backing up, and have met with no luck - I keep getting broken pipe errors, and attempts to create directories like "user@192.168.0.1::backup/backup" on

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

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

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

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

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.

Has any progress ever been made towards fixing the problem causing rsync processes to hang in the cygwin environment? I've tried just using Unison in the windows environment, since it has a native port, but, um. Unison is probably great for what it IS intended for, but it absolutely sucks nuts as a backup solution (has a tendency to choke and cancel the ENTIRE PROCESS without synching

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: #####################################################