argusarchive segmentation faults

[Peter Van Epp]

	Replaceing #!/bin/sh with #!/bin/sh -x -v as the first line will 
turn on debugging and tell you where the seg fault occurs (likely one of the
programs being called running out of memory). If it is generating core files
the core should tell you which program is getting the seg fault. rasort is
always a good bet, you may wish to comment out the RASORT line below if your
files are large (and/or feed one of the files that segfaults in to rasort and
see if it seg faults on the command line). 

if [ -f $ARCHIVE.tmp ]; then
#  $RAGATOR -VRr $ARCHIVE.tmp -w - | $RASORT -w $ARCHIVE
   $RASORT -r $ARCHIVE.tmp -w $ARCHIVE

Peter Van Epp / Operations and Technical Support 
Simon Fraser University, Burnaby, B.C. Canada

On Tue, Feb 01, 2005 at 12:12:31PM -0500, John Nagro wrote:
> I have been getting seg faults when using the argusarchive script
> recently. Any ideas?
> 
> -- 
> John Nagro
> john.nagro at gmail.com