Stephen wrote, in response to jfoley:
> Yeah I got to do the same for my program as well. Wouldn't a line
> with a ctrl-z in it most likely end up being corrupted in other ways
> as well?
Well, of course, but it least it won't stop the rest of the lines being
read.
Hmmm, I've just thought. What happens if CTRL-Z gets into the HTML page?
Will the rest of the page still appear? Could someone kindly test this
for me?
On the topic of end-of-something markers in the log files, I would like to
see an addition to analog from a debugging perspective. I've had my fair
share of "corrupted" log files, and finding the offending line in the file
is so difficult, I've basically punted on fixing them.
I was wondering if Analog could output the "trouble" lines as it reads a
file? That is, it would output the log file name it is working on, and the
line it barfed on. I know it outputs "corrupted" line entries, but the
ability to "know" which lines these are would also be helpful.
I'm working through a situation now where JWS is imbedding nulls (of all
things) into the log files :( Sure, I can "vi" them to get rid of them once
a week, but it would be useful to work around such an issue. vi detects the
"real" EOF mark (so the system is doing the right thing from a file read
perspective), and simply strips the nulls out. But, the nulls are causing
analog to barf when it reads the log files.
Yeah, I know. JWS is broke (in more than this way, but I don't have a
choice). Is there an "analog" way to get around this?
The good news is that I have good friends on the dev. team at Sun working
on JWS, but fixes are taking a long while to develop :)
--------------------------------------------------------------------
This is the analog-help mailing list. To unsubscribe from this
mailing list, send mail to [EMAIL PROTECTED]
with "unsubscribe analog-help" in the main BODY OF THE MESSAGE.
--------------------------------------------------------------------
