Eric Mountain wrote:
BTW, if you do get a core, it would also be useful to know what exactly you're
running on the NSLU2: Unslung, OpenSlug, Debian-ARM,... perl/rsync version
(esp the version of the program that dumps), etc.
Hmmm,
well that didn't take too long. The automatic run around 01:00 this
morning barfed with RC=139.
Core was generated by `/opt/bin/perl /opt/sbin/dirvish --vault IBM-rexx'.
Program terminated with signal 11, Segmentation fault.
Cannot access memory at address 0x4015cef4
(gdb) bt
Error accessing memory address 0x4015cef4: No such file or directory.
I guess I now need to read up on using gdb. Was this Perl or dirvish
that actually got the segmentation fault?
I am running,
Firmware Version: V2.3R29-uNSLUng-5.5-beta
Kernel: 2.4.22-xfs
This is perl, v5.8.6 built for armv5b-linux
rsync - 2.6.9-2
<h1 align="center">DIRVISH RELEASE NOTES</h1>
<h2>Dirvish version 1.2.1 released 18 February 2005</h2>
The backups are run by a script called by cron that pings each of three
machines to see if they are on, and then does a total of 5 trees. All
trees died with RC=139, but I only have a single core.
In each log file there is just the rsync call and nothing else.
Cheers Brian
_______________________________________________
Dirvish mailing list
[email protected]
http://www.dirvish.org/mailman/listinfo/dirvish
