Summary: Looking for a smooth way to allow rsyncing of mail and news
to generate cumulative archives, but cut off a specified
date, and begin a new archive that contains nothing of the
previouis one.
That might have sounded kind of confusing, but here's my setup: I
rout
FYI, I decided to release a new version of my next-generation protocol
test app because I created an optimized transfer mode when files are
being sent whole (it bypasses all calls to librsync). This makes my
"rZync" test app faster than rsync for sending whole files (rather than
4x slower, like i
Included below is a shar archive containing two patches that together:
1) make backup files get their setuid and setgid bits stripped by
default
2) add a "-s" option that allows backup files to continue to have
these privileges
This means that if you update a collection of binaries with rsync,
A l'attention du Responsable du Bureau d'études automatismes - Merci de bien vouloir
apporter votre
attention à ce message.
Bonjour,
Nous avons le plaisir de vous proposer de vous envoyer gratuitement notre nouveau
catalogue de 330
pages.
Pour l'obtenir, retournez-nous cet email avec votre nom
On Fri, Jun 21, 2002 at 03:46:39AM -0700, Wayne Davison wrote:
> The count of transferred bytes in the latest protocol is now below what
> rsync sends for many commands -- both a start-from-scratch update or a
> fully-up-to-date update are usually smaller, for instance. This is
> mainly because m
On Thu, Jun 20, 2002 at 03:47:14PM -0600, [EMAIL PROTECTED] wrote:
> I don't know if the setlock thing is completely immune to racing.
setlock (and possibly other utilities like it) basically obtains an
exclusive lock on a user-specified file before running the indicated
program. If flock()/lock
For anyone who'd like to check out the latest release of my "rzync" [sic]
test release, I've just released a new version. For those that might
not have time to look at the code but could provide some feedback based
on a rough description, I've created the following simple web page:
http://ww
I was wondering if it would be possible to keep a user/uid <-> file map so
that root access wouldn't be necessary to store the files and retrieve them
with the correct original usernames (or uids), specifying a filename on the
command line as something like .rsyncuidmap.
Or even a file system s
