You ([EMAIL PROTECTED]) write:
>AFS commands (hope this isn't a trade secret :) do this:
> code = cmd_Dispatch(argc,argv);
> exit (code != 0);
>We would surely appreciate:
> exit (cmd_Dispatch(argc,argv));
>then our automated process could tell whether or not to retry
>). For example, this:
>Jul 24 13:34:09 <12223> afs.incr: Doing (try 1): /usr/afs/bin/pts removeuser -user
>root -group system:hascall
>Jul 24 13:34:10 <12223> /usr/afs/bin/pts: User or group doesn't exist so failed to
>remove user root from group system:hascall
>is not going to succeed, no matter how many times it gets tried.
If I understand your question correctly, I don't think that
will help. But it is also not a problem.
The AFS error codes are longs, whereas exit codes are a byte.
You'll just get the last byte, which probably won't help.
If you are just running programs, then using expect or perl
and examining the error messages seems to be a simple approach.
Yours,
Larry Schwimmer
[EMAIL PROTECTED]
