Acbosgd.153 net.news utzoo!decvax!duke!chico!harpo!cbosg!cbosgd!mark Sun Nov 22 13:37:45 1981 Re: uuxqt status That message means that the rnews command on the remote system (in your case, sytek) exited with status 1 (see wait(2) for why this is 256). This probably in turn means that sytek decided it had already seen the article you transmitted to it and threw it away. This is symptomatic of two problems. First, these messages normally only are sent to the guy who originated the news, or else to a name like "uucp". If you aren't posting that many articles, it would appear that your news is sending articles it gets from sytek back to sytek, unless you get news through two different sources. This isn't supposed to happen - perhaps your sys file thinks it's sending to some system other than sytek. Second, it is generally recommended that sites fix their uucps not to send back these annoying messages. Certainly in the (common) case where an article is fine and the exit status is zero, there shouldn't be an ack of this form, but there will be unless your neighbors fix their uucps. It's about a 15 line change to uucp, and I'll post the fix on the next article. You should also fix your sys file and/or your broadcast routine in netnews to use the -z option to uux (search for uux to find this code). Mark Horton ----------------------------------------------------------------- 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.