gz@spt.entity.com (Gail Zacharias) (12/22/87)
I've recently upgraded from a 286 to a 386 (SCO Xenix) and started
having problems receiving uucp mail. I get the mail normally, but it
also gets deposited in /usr/spool/uucp/.XFDDIR, where all the failed
uucp transactions go. I run smail.
After poking around a bit, it seems that running smail through the shell
(as uucp does) returns a non-zero status. That is, smail does exit(0)
but the shell claims a non-zero exit status! I can also get this to
happen by invoking smail by hand in the cshell if I specify a full path:
% /usr/bin/smail gz
testing
^D
% echo $status
2
If I just type % smail gz, this doesn't happen, i.e. echo $status shows 0
(no, I don't have a different smail elsewhere in the search path). I have
written little test programs that fork a smail, and some that fork a shell
to run smail. The former return 0, the latter return 0x0200. The non-zero
exit value is almost always 2 ('no such file'?) but I think I have also seen
3 ('no such process'?) although I can't duplicate that reliably.
Can anybody offer any guesses as to what's going on? Better yet, any
solutions? (I have sources to smail, but not to the shell or uucp). My
.XFDDIR is filling up and I'm afraid of missing some real lossage by
automatically cleaning it out...
Thanks in advance for any help.
=========
gz%entity.com@eddie.mit.edu gz@entity.com {backbone}!spt!gz