My suggestion is to grep for the error message in the source and then look
at the lines before it in the source. When I encounter strange or
undescriptive error messages in programs this method almost always solves
the problem for me quickly.
Bob Toxen
[EMAIL PROTECTED]
http://www.cavu.com
http://www.cavu.com/sunset.html [Sunset Computer]
ftp://ftp.mindspring.com/users/cavu/century.c [Y2K CMOS clock fix for Linux]
ftp://ftp.mindspring.com/users/cavu/hwclock.c [Y2K hwclock for broken CMOS]
Fly-By-Day Consulting, Inc. "Don't go with a fly-by-night outfit!"
Failure is not an option!
It comes bundled with all Microsoft products (in my opinion).
"Linux, a better way to go!"
