On Thursday 20 March 2008, Stuart Halliday wrote:
Is it just me or a lot of people on this mailing list got into a bad habit
of also carbon copying to the poster as well?
Just delete the duplicate. It's that simple.
Ironically, the Bad Habits subject made me pull the original message
Hello,
I have just put reviewed versions of the rsync cheatsheets which I
posted a couple of years ago
(if I correctly keep track of time), right here:
http://public.m-plify.net/rsync_cheatsheets/
- Sheet one lists the possible combinations of SOURCE and DEST arguments
that may be given to
Wayne Davison wrote:
On Fri, Jan 11, 2008 at 09:45:00PM +0100, David Tonhofer wrote:
I have just put reviewed versions of the rsync cheatsheets which I
posted a couple of years ago
Cool -- thanks for the updates! I see that they now cover the arg
improvments that are in rsync 3
[EMAIL PROTECTED] wrote:
rsync version 2.6.9cvs protocol version 29
Running rsync from an rsnapshot script I get the following error:
unknown message 4:1 [generator]
rsync error: error in rsync protocol data stream (code 12) at io.c(307)
[generator=2.6.9cvs]
rsync: connection
Ed wrote:
Hi all,
I'm stuck with a little dilemma and I thought someone could give me a little
advice.
Is there a way to use rsync with an ssh certificate?
There should be
what I have:
First of all I am forced to use the root account with ssh which I know is a
big no,
Nathan wrote:
I've got an issue where I'm trying to force ssh access to rsync, the only way I could
find somebody saying was by doing a hosts allow = 127.0.0.0/24 which I think
Wayne said on this list. The problem is when I do that, I get a wacky error message back
which is as follows:
Okay, so who tried to subscribe the rsync list to the french national railway
newsletter?
--On Thursday, May 11, 2006 9:52 AM + [EMAIL PROTECTED] wrote:
Madame, Monsieur,
Ceci est une réponse automatique. Merci de ne pas répondre à ce message.
[...]
--On Friday, May 05, 2006 12:49 PM +0200 [EMAIL PROTECTED] wrote:
Dear user of samba.org,
Your email account was used to send a huge amount of junk email messages during
the last week.
We suspect that your computer had been compromised and now runs a trojaned
proxy server.
Please follow
First of all, thanks for all the comments.
And sorry for taking so long to respond. I had to strategically forget
a short time about the illustration and in interim two months have passed.
My inner clock must be going wrong.
Anyway, here is a revised edition. I have decided to keep the original
Hello, I guess someone must know the answer to this conundrum.
Context:
The device file in question has been created by an rsync backup.
The original device file (e.g. /dev/agpgart) as seen through stat(1) shows:
Size: 0 Blocks: 0 character special file
The copy of the device file
Hello,
I was somewhat confused by the rsync options, so I have
decided to do a little illustration showing the possible
SRC and DEST args. Feel free to use the diagram as you like.
(This includes critizing):
http://rei1.m-plify.net/Rsync_Usage.png
The original is a MS Visio (closed format etc,
11 matches
Mail list logo
