search for: bescoto

Hi, I am thinking about a non-standard usage of rsync (at least not mentioned in the man file) I want to synchronized my collegues home directories(trees) each night AND store rsync's internal updating commands (reversed) to be able to restore the state of a directory the day before. This would require - saving the internal updating commands in a separate directory - reversing these commands

Can someone explain to me what is happening here: ~ $ touch foo ~ $ ln foo bar ~ $ ls foo bar bar foo ~ $ mv foo bar ~ $ ls foo bar bar foo I try to move a file over a hard linked copy of itself and the move fails, but there is no error. Is this the intended behavior? -- Ben Escoto

A while back, I asked if there had been any consideration in making rsync support direct ssl (as opposed to just ssh). I've been looking around for a secure way (e.g. encrypted, so passwords are never in the clear, and even content is obscured from sniffers) to allow a set of limited-trust users (limited-trust being defined as mostly customers, whom you trust with their own data, but not with

Im brand new to rsync and i been doing alot of reading about it and it looks like the tool I have long been wanting. Bascially i got 1 server, 2 hard drives. partions are / /boot /home /usr /var /backup (2nd drive) Bascially what i am looking at doing is mirroring the first drive to the 2nd drive, and once that intial one is moved over, have a cron run nightly (or when specified) that will

If I want to make sure a file has really been deleted do I have to: 1. fsync the file 2. fsync the directory the file is in 3. both? Much thanks. -- Ben Escoto

Hi, I vaguely remember some talk on this list of a virtual file system of some sort for rsync. The goal was to handle cases where the file system on the original side carried information (permissions, ownership, special file types?) which couldn't be recorded directly on the receiving side. I think the proposal was to record as much of this information as possible in the receiving

Hi, can someone tell me whether applications can expect the write requests they make to be executed in order? For instance, suppose an application requests that a file be deleted, and then that another file be moved to an unrelated place. Will these events always happen in that order? Or to put it another way, if something unexpected happens in the meantime (say the computer crashes), is it