On Sat, 1 Feb 2003, Jorg B. wrote:
>
> This problem is occurring on two different servers, with completely different
> hardware, different version of slackware and different version of kernel
> (tried on 2.4.18, 2.4.19 and 2.4.20).
>
> There is nothing major in common between the 2 servers except
What kind of crash? Was it a panic, a hang or a reboot for no obvious
reason? Was it a clean shutdown or did the disks need fsck (assuming
an ext2 filesystem)?
Was rsync running as root or another user?
Did rsync use up some scarce resource, such as memory or processes?
What was rsync doing at
On Sat, Feb 01, 2003 at 02:17:53PM -0800, Jorg B. wrote:
> This problem is occurring on two different servers, with completely different
> hardware, different version of slackware and different version of kernel
> (tried on 2.4.18, 2.4.19 and 2.4.20).
>
> There is nothing major in common between
This problem is occurring on two different servers, with completely different
hardware, different version of slackware and different version of kernel
(tried on 2.4.18, 2.4.19 and 2.4.20).
There is nothing major in common between the 2 servers except proftpd and
rsync.
We have done some extens
On Sat, Feb 01, 2003 at 01:47:39PM -0800, Jorg B. wrote:
> Hello,
>
> We are running rsync version 2.5.6 on a slackware (version 9.0-beta) linux
> server. This server is basicly a ftp server (96 sessions max) and a rsync
> (rsync --daemon) server (25 connections max).
>
> The server keeps on cr
Hello,
We are running rsync version 2.5.6 on a slackware (version 9.0-beta) linux
server. This server is basicly a ftp server (96 sessions max) and a rsync
(rsync --daemon) server (25 connections max).
The server keeps on crashing and after many ours of hardware/software trouble
shooting the c
