'rm name.$TIMESTAMP'? I don't see why that's hard. and 'tail -50
error.log' (or however many lines are needed) should give you the name
of the broken file.
--
Jeremy Wadsack
Wadsack-Allen Digital Group
Pfender, Alexander ([EMAIL PROTECTED]):
> think i should do that, the problem is that all logs looks like
> 'name.$TIMESTAMP'. i think that's very difficult to exclude one ore two of
> possible corrupt log-files. many thanks jeremy...
> -----Urspr�ngliche Nachricht-----
> Von: Jeremy Wadsack [mailto:[EMAIL PROTECTED]]
> Gesendet: Mittwoch, 27. Juni 2001 16:00
> An: [EMAIL PROTECTED]
> Betreff: Re: [analog-help] Broken Pipe, please give me a hint
> Pfender, Alexander ([EMAIL PROTECTED]):
>> i use this great analog tool, but i must scan a very large amount of
>> log files (~ 4GB every day). analog terminate with an Broken Pipe at
>> 1/3 before it's done and produced a 40MB debug file. could anybody
>> give me a little help about this error? i have read some hints in
>> documentation, but there is written that this is not an analog error
>> and i can't locate the source of this error. is it an exception of
>> gzip -cd (gunzip)? don't know...
> It's most likely a problem with gzip (this is the only external
> process that Analog pipes to/from). You can tail your error log file
> to find out which file it's failing on and remove the offending file
> (it's likely a corrupt archive).
+------------------------------------------------------------------------
| This is the analog-help mailing list. To unsubscribe from this
| mailing list, go to
| http://lists.isite.net/listgate/analog-help/unsubscribe.html
|
| List archives are available at
| http://www.mail-archive.com/[email protected]/
| http://lists.isite.net/listgate/analog-help/archives/
| http://www.tallylist.com/archives/index.cfm/mlist.7
+------------------------------------------------------------------------
