On Friday 28 April 2006 6:46 am, Neill Jones wrote: > Not a perl expert but does the print print out to stdout? If so, maybe > (just maybe) it doesn't like > that since cron doesn't have a tty attached (really just guessing). If > you want to get a feel of what > is causing the problem though, just comment out sections of code and run > it until you can isolate > what line is causing the server error - I'd start with the whole script > commented out. That way you > can eliminate permissions etc before delving into the perl itself. > > Maybe no-one else is using this as a cronjob which is why they are not > seeing problems. > > Regards > > Neill > Neil, you may be on to something there. I commented out the whole script then un-commented it a line at a time, when it got to this line:
#print "$file\t$result\n"; I got the '500' error output. Prior to that the script reported 'no output'. There were several scripts written to get this .ndb file, both perl and bash. Maybe I should just try another one. -- Chris Registered Linux User 283774 http://counter.li.org 17:05:43 up 7 days, 20:50, 1 user, load average: 0.34, 0.43, 0.30 Mandriva Linux 10.1 Official, kernel 2.6.8.1-12mdk ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ The software required Win95 or better, so I installed Linux. ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
pgp8qEccceI3C.pgp
Description: PGP signature
