shawn%mit-dspg@BRL.ARPA (11/18/83)
I have the following wishes for uucp: 1) to be able to print what's queued, in a reasonable way, and to be able to know what's going where, and how big it is. (without doing an ls /usr/spool/uucp). 2) to be able to cancel a request, without haveing to use grep, cat, and rm. 3) to be able to have something to run at night, as a batch daemon, (run by say, cron), and warn me of any errors uucp had during the day, and mail me the error string. If this has been done, or any of the above has been done, I would be VERY happy to be alerted to it. (and very thankful). Else, in a fiew weeks, I will set apon the tasks myself. Thanks In advance, -Shawn
BostonU SysMgr <root%bostonu.csnet@csnet-relay.arpa> (02/11/85)
We don't use UUCP much so I might be missing something here, apologies: We have a hard-wire between two machines and it seems like it would make sense if it just were always open rather than either having one side 'call' in or hack something to get alternate login shells on either side as desired etc. Perusing the code, it seems to me that uucp may not be robust enough to do this as written: 1) Something reasonable would have to happen when one side really went down 2) New work entering the queue would have to wake up uucico to start sending. Am I just missing something that's there? -Barry Shein, Boston University