ber (05/09/82)
I have 174 LOG.<pid>.0 files in my uucp spool directory. All of them are --w--w--w- so uulog won't clean them up. Has anyone addressed the problem with uucp that leaves these things lying around? Or perhaps its a local problem? brian redman
shannon (05/10/82)
The reason you have so many LOG.<pid>.0 files laying around is that they are not being merged back into the main LOGFILE because they have mode 222, which indicates they are still in use. They are changed to mode 666 when the program logging to them terminates. Anyway, the fix to the problem is to add a call to logcls() at the beginning of cleanup() in uux.c. Otherwise any temporary log files used by uux would not be changed to mode 666 when uux terminated. You may also find a LOG.<pid>.0 file left after a program aborts, use uuclean to get rid of those. Bill Shannon decvax!shannon DEC UNIX Engineering Group
trb (05/10/82)
Shannon's logcls() fix (to uux) doesn't mention that you should diddle the Makefile to include logent.o in the uux compilation. (uux didn't before.) Since there are systems other than 4bsd running uucp, this fix doesn't really belong in net.bugs.4bsd. I usually don't spend my time sifting thru 2.8bsd fixes, because I doubt I'll ever use one. Do they submit reports for bugs on 4bsd systems? Universal unix fixes should go in net.bugs or net.unix-wizards. Andy Tannenbaum Bell Labs Whippany, NJ (201) 386-6491