> > Fcc +mail_log: errored (0177400)
> I searched through the nmh source and there is no mention of "177400", so
> you should ask the exmh people about that cryptic error.
I'd bet that the "177400" isn't a literal string, but an integer
printed out with a "%d" printf format, so a string search for it might
not turn up anything. I just searched for "errored" and found a hit
in uip/spost.c:
fcc (char *file, char *folder)
{
pid_t child_id;
int i, status;
char fold[BUFSIZ];
if (verbose)
printf ("%sFcc: %s\n", msgstate == resent ? "Resent-" : "", folder);
fflush (stdout);
for (i = 0; (child_id = vfork()) == NOTOK && i < 5; i++)
sleep (5);
switch (child_id) {
case NOTOK:
if (!verbose)
fprintf (stderr, " %sFcc %s: ",
msgstate == resent ? "Resent-" : "", folder);
fprintf (verbose ? stdout : stderr, "no forks, so not ok\n");
break;
case OK:
snprintf (fold, sizeof(fold), "%s%s",
*folder == '+' || *folder == '@' ? "" : "+", folder);
execlp (fileproc, r1bindex (fileproc, '/'),
"-link", "-file", file, fold, NULL);
_exit (-1);
default:
if ((status = pidwait(child_id, OK))) {
if (!verbose)
fprintf (stderr, " %sFcc %s: ",
msgstate == resent ? "Resent-" : "", folder);
fprintf (verbose ? stdout : stderr,
" errored (0%o)\n", status);
}
}
fflush (stdout);
}
so I guess the trick is to figure out what an octal "177400" as a return
value for pidwait() would mean.
--
[EMAIL PROTECTED]