Path: utzoo!censor!geac!torsqnt!news-server.csri.toronto.edu!cs.utexas.edu!wuarchive!zaphod.mps.ohio-state.edu!caen!ox.com!emv
From: chris@wugate.wustl.edu (Chris Myers)
Newsgroups: comp.archives
Subject: [list.nntp-managers] Re:  NNTP and CNEWS
Message-ID: <1991Feb2.180040.4456@ox.com>
Date: 2 Feb 91 18:00:40 GMT
References: <9102011749.AA26635@wugate.wustl.edu>
Sender: emv@ox.com (Edward Vielmetti)
Reply-To: chris@wugate.wustl.edu (Chris Myers)
Followup-To: list.nntp-managers
Organization: OTA Limited Partnership
Lines: 24
Approved: emv@ox.com (Edward Vielmetti)
X-Original-Newsgroups: list.nntp-managers

Archive-name: news/nntp/newsxd/1991-02-01
Archive: wuarchive.wustl.edu:/packages/newsxd-2.5.1-shar [128.252.135.4]
Original-posting-by: chris@wugate.wustl.edu (Chris Myers)
Original-subject: Re:  NNTP and CNEWS
Reposted-by: emv@ox.com (Edward Vielmetti)

> Then, every five minutes, cron kicks off a job that eventually runs a
> program called nntpsend, which deals with locking and renaming and runs
> nntpxmit.  (I can provide nntpsend.c to anyone who wants.)
> 
> There are doubtless race conditions, but I haven't noticed them yet.
> If anyone wants to scrutinize nntpsend, I'd be delighted....

Have you taken a look at newsxd?  It handles all of the locking,
reduces the load on your system and gives you a CONSIDERABLE amount of
control over when nntpxmit is run.  The latest version of newsxd
(2.5.1) was posted to comp.sources.unix some time ago and may be
retrieved from wuarchive.wustl.edu [128.252.135.4] via anonymous FTP.
The filename is /packages/newsxd-2.5.1-shar.

Chris Myers                                Internet: chris@wugate.wustl.edu
Software Engineer                           UUCP: ...!uunet!wuarchive!chris
Office of the Network Coordinator                BITNET: chris@wunet.bitnet
Washington University in Saint Louis                 Phone: +1 314 726 7390