Brian wrote:
Eric Mountain wrote:
On Friday 06 April 2007 12:47, Paul Slootman spake thus:
That means it's fairly out of the scope of dirvish; either the perl port
is buggy, or there are deeper problems with the system (shared libs,
kernel, memory...)
First thing I would go for is to upgrade perl: there is a 5.8.8-16
available it seems (if I'm looking in the right place - not familiar
with this stuff):
http://ipkgfind.nslu2-linux.org/details.php?package=perl&official=
Cheers,
Eric
Thanks Eric and Paul,
just upgraded Perl and the first test ran OK. Only time will tell.
Cheers Brian
_______________________________________________
Dirvish mailing list
[email protected]
http://www.dirvish.org/mailman/listinfo/dirvish
Oh well,
got an RC=139, with core, with 5.8.8-16 perl yesterday evening.
Just one thing bothers me, I started dirvish two times yesterday
evening, like this:
ping -c 1 192.168.123.180 > /dev/null
if [ $? -eq 0 ]
then
/bin/logger "Brian is active"
/opt/sbin/dirvish --vault brian
dirvret=$?
/bin/logger "dirvish RC = $dirvret"
.....
so for two different vaults, as the pc that has those two trees on to
backup was active at that time. So both times Perl died. I assume there
is nothing that I need to do inbetween those calls that could revive
Perl. I see that either all backups go through OK, or all die, its never
so that some are OK and some are not.
Anything I could check in Perl if I was to get the RC=139?
Cheers Brian
_______________________________________________
Dirvish mailing list
[email protected]
http://www.dirvish.org/mailman/listinfo/dirvish
