Very Computer

Anyone any idea how I can determine what these error codes are?
I can't fix it, 'cause I don't know what's broken.

Regards, Chris

Christopher Moore telecommunicated (on 23Jan):
| Anyone any idea how I can determine what these error codes are?
| I can't fix it, 'cause I don't know what's broken.

I meant to answer your posting of a few days ago, but got distracted.

99 is used by rmail for twenty differnt minor errors.
141 ( that's what you meant, I think ): does it seem to affect ONLY the
first message out of a bunch of email in the same uucp connection?

141 from rmail turns out to be coming from a wait() system call.

As I recall, this still an open problem back at SCO.

One band-aid is to mv uuxqt to uuxqt.orig, then create a shell script
called uuxqt that does
        exec uuxqt.orig -x3

--

Many thanks Jean-Pierre,

This has indeed solved the problem. However, uuxqt now has to be started
by hand. The script has exactly the same permissions & ownership as the
original but it will not run by itself, for example; uudemon.hour comes
up with /usr/lib/uucp/uuxqt: Can not open - although it does have
permission & I have a : at the start of the script file to show it is a
bourne script.
Anyway I'll play with it some more, thanks again.

Regards, Chris.

You need to put "#!/bin/sh" at the first line of the script.  This tells
the *kernel* that it's a Bourne shell script.

Quote:>Bela<