Aharpo.367 net.general utzoo!decvax!duke!chico!harpo!ber Mon Jul 27 18:33:23 1981 uux junk mail I have found a copy of uux.c and uuxqt.c on mhtsa which attempted to provide an option to uux which caused uuxqt not to send exit status to the remote command originator. I fixed this code and added another option which says "only send exit status if it is non zero". I think these methods are more reasonable then the current technique of adding each command you don't want to know about to an if-then-else in uuxqt.c. The changes are trivial, and non-btl'ers can figure it out. Just have uux check for these options and define a new remote command constant (X_blah) to be sent to uuxqt on the remote system. Uuxqt sees the option when it runs, sets a flag and behaves appropriately when it thinks about mailing back status. Btl'ers are welcome to get the three modules from me (uux.c, uuxqt.c, uucp.h). If you've been complaining about getting extraneous mailings from harpo or chico about return codes and such, then diddle netnews. The options are: uux -n ... don't mail back return status uux -z ... don't mail back return status unless it's non-zero ----------------------------------------------------------------- gopher://quux.org/ conversion by John Goerzen of http://communication.ucsd.edu/A-News/ This Usenet Oldnews Archive article may be copied and distributed freely, provided: 1. There is no money collected for the text(s) of the articles. 2. The following notice remains appended to each copy: The Usenet Oldnews Archive: Compilation Copyright (C) 1981, 1996 Bruce Jones, Henry Spencer, David Wiseman.