ble via SameTime Connect within Philips, caesupport2 on AIM
"There are some who call me Tim?"
Erik Enge <[EMAIL PROTECTED]>
Sent by: [EMAIL PROTECTED]
10/01/2002 02:10 PM
To: Tim Conway/LMT/SC/PHILIPS@AMEC
cc: [EMAIL PROTECTED]
Subject:
Did you have a look at the core file? Building unstripped rsycn and then
debug the core should give you some ideas. The large number you are
getting may be caused by memory corruption.
> Usually it's pretty obvious which environment variable is the problem.
I think that you really mean process
[EMAIL PROTECTED] writes:
> Erik: One more thing to try: redirect in /dev/null to the rsync
> command. At one time, at least, its behaviour was different based on
> the nature of its STDIN. Make sure STDERR and STDIN are redirected
> somewhere, too... either a file or null.
All our output are r
PROTECTED]>
Sent by: [EMAIL PROTECTED]
10/01/2002 12:49 PM
To: [EMAIL PROTECTED]
cc: (bcc: Tim Conway/LMT/SC/PHILIPS)
Subject: Re: rsync 2.5.5 segmentation fault on Linux x86.
Classification:
Paul Haas <[EMAIL PROTECTED]> writes:
> T
Paul Haas <[EMAIL PROTECTED]> writes:
> Then I run it once interactively and once through cron and compare stuff.
>
> Usually it's pretty obvious which environment variable is the problem.
I also noticed in the logs that rsync exists with "exit code 12":
Oct 1 01:31:59 backup-server inetd[1
Paul Haas <[EMAIL PROTECTED]> writes:
> This isn't specific to rsync.
I must be missing something. The fact that rsync segfaults isn't
specific to rsync?
We run tens of thousands of cronjobs a week and none of them have so far
segfaulted.
However, since I can't make it segfault on the comma
On 1 Oct 2002, Erik Enge wrote:
> Hi all.
>
> I have a script which I call from cron. It basically does some stopping
> of a few services, rsyncs all files to a remote server and then starts
> the services again. However, rsync segfaults:
>
> /share/bin/cron.root.backup.sh: line 28: 18453 Seg
Erik,
2.5.5 rsync crashes and burns my hard disk, you are indeed lucky to get a
segmentation fault.
When I reported flakiness I was told it was my hardware. I upgraded my
hardware - no difference.
Then I was told to change my 2.4.x kernel. Why? it runs everything else,
and has reliably for over
