I've looking for a solution for this and no amount of googling has
come up with anything.
Is it possible to provide a static listing on a server, say every
24 hours, that a standard end-user rsync can pull and use?
I have a lot of files to provide and the idea of every request
dynamically
On 22/12/11 14:44, Kevin Korb wrote:
Is it possible to provide a static listing on a server, say every
24 hours, that a standard end-user rsync can pull and use?
Sounds like a job for a snapshot. If you are on Linux that would
be an lvm2 snapshot. Other operating systems with basic volume
On 22/12/11 14:59, Kevin Korb wrote:
Is it possible to provide a static listing on a server, say
every 24 hours, that a standard end-user rsync can pull and
use?
Sounds like a job for a snapshot. If you are on Linux that
would be an lvm2 snapshot. Other operating systems with basic
volume
On 2011-07-01 09:40 PM, Chris Dennis wrote:
I have two hosts (my portable and my desktop). I work on both
hosts at different times and so I keep a few dirs sync'd
between the two. I have a docs dir where I may be modifying
files, adding files, renaming files and deleting files on
On Mon, 7 Jun 2010 4:07:22 am Mag Gam wrote:
Is it possible to sleep 1 second after each file
is rsynced?
Interesting idea but not that I know of.
Ofcourse, I can put this in a for loop and do a
sleep after each file is done, I was wondering if
there was anything native in rsync for this
On 2010-06-07, Eberhard Moenkeberg wrote:
Is it possible to sleep 1 second after each file
is rsynced?
If you are concerned about giving the rest of the system
some time to breathe then just nice the rsync process.
nice -n 19 rsync ... etc
This would not help, regarding i/o.
Care
On 2010-06-07, Mag Gam wrote:
I am more concerned with write penalty. We use netApps, and
if there is a huge write (10gb file) i would like to give the
filer to recover before I can start syncing more data.
Perhaps as Eberhard suggested, ionice might be useful and is
part of the util-linux-ng
I've read a few tutorials about how to use rsync via ssh using the
command= functionality to restrict where the user can sync to. I've
got this on the on the destination side in it's ~/.ssh/authorized_keys...
command=rsync --server -vvnlogDtpre.iLsf --timeout=999 .
On 2010-06-04, Matt McCutchen wrote:
I've read a few tutorials about how to use rsync via ssh
using the command= functionality to restrict where the
user can sync to.
...
or (my preference) use a single-use rsync daemon. See:
https://bugzilla.samba.org/show_bug.cgi?id=4163
I didn't know
