Path: utzoo!utstat!news-server.csri.toronto.edu!cs.utexas.edu!samsung!zaphod.mps.ohio-state.edu!ncar!mephisto!bbn.com!mips2!mwarren From: mwarren@mips2.cr.bull.com (Mark Warren) Newsgroups: news.software.b Subject: Re: What happens with the nntp.a$$ files? Message-ID: <1990Jul20.182135.22896@mips2.cr.bull.com> Date: 20 Jul 90 18:21:35 GMT References: <1990Jul19.215007.27992@caen.engin.umich.edu> Organization: Bull HN Information Systems Inc. Lines: 24 In article <1990Jul19.215007.27992@caen.engin.umich.edu> stealth@caen.engin.umich.edu (Mike Pelletier) writes: >Occasionally I get "nntp.a" files hanging around in my >/usr/spool/news/in.coming directory. What entity in the C-news >entourage is responsable for processing these files, or is it NNTPs >responsability? Is there a simpler way to deal with them than >using "cat nntp.a* | rnews"? Thanks for the information... > Those are partial NNTP in coming spool files. They are built as nntp is receiving, and when they reach some size limit (defined in the nntp common.h file) they are renamed to some name that Cnews' newsrun program finds and unspools. The nntp.a* file is left around if your nntpd or your system crashes while nntp is receiving. Cnews has a script called "newsboot" or "bootnews" or something similar that is supposed to be run by /etc/rc that looks for these leftover turds and renames them so that newsrun will find them the next time it runs. -- == Mark Warren Bull HN Information Systems Inc. == == (508) 294-3171 (FAX 671-3020) 300 Concord Road MS820A == == mwarren@granite.cr.bull.com Billerica, MA 01821 ==