On Tue, Nov 14, 2006 at 05:03:15PM -0600, William McInnis wrote:
> rsync error: timeout in data send/receive (code 30) at io.c(153)
If you're getting a timeout either, 1) your timeout is too short, 2)
your rsync isn't very recent, or 3) the client side doesn't know about
the timeout when talking t
hey my rsyncd will work well for a while then i will start to get this error
rsync error: timeout in data send/receive (code 30) at io.c(153)
check the error logs and just have this in there
it is on a local box so i know its not a network problem
--
This message has been scanned for viruses a
Title: Get your Website seen locally and globally
Graeme G Van Leer
Logistics Support Analyst
IMP Group Ltd,
Aerospace Division, Hangar #1
579 Barnes Road, Halifax International Airport,
Halifax, NS, B2T 1K3
(902) 873-2250 ext. 1141
[EMAIL PROTECTED]
--
To unsubscribe or chang
I had this problem here on some of our
servers after an o/s upgrade, and found that the /dev/urandom file had
changed permissions from 644 to 600.
ls -l /dev/urandom
crw--- 1 root
system 33, 1 Jul 21 10:49 /dev/urandom
I simply changed the permissions
chmod go+r /dev/urandom
On Sat, 04 Nov 2006 19:48:22 -0300, Manuel Kissoyan wrote:
> im trying to work out my backup with a monthly retention, wondering how i
> could keep a backup that is 30 days old all the time
You'll keep yourself confused as long as you word the problem that way.
You [probably!] don't always want
I'll be honest, I was about to send a long mail on how it still doesn't
work... when it suddenly did! :)
So I thought some poor soul might like a step by step so here it is
192.168.1.1 is the source with the data you want
192.168.1.2 is the destination where you want the data to go
with that in
