On Fri, 10 Feb 2006, Kevin W. Gagel wrote: > ----- Original Message ----- > >> I'm not sure it'll be a parameter as only about 7,000 > >> messages failed out of 90,000. Unless its some kind of > >> time out... But thats the thing, I don't know what the > >> error 70 means. > > > >look for a file called sysexits.h. there you can get the > >meaning of error codes. taken from a feroda sysexits.h: > >EX_IOERR -- An error occurred while doing I/O on some file. > >define EX_IOERR 74 /* input/output error */ > > > >well, thats not much of information. but place a 'set -x' > >at the top of your bash script, this might help discovering > >the problem. > > > >regards, > > I allready know (realize) the EX_IOERR is an IO error. I'm > trying to figure out what is going on to cause it and what > exactly the system is trying to tell me that it failed on. > Could it not find the file? The directory? Read the file? As > you indicated the sysexits.h doesn't tell much. > What will the "set -x" do?
it makes the bash script verbose, its kind of debugging modus. just try, wont harm anything. regards, Matthias
