thad@btr.btr.com (03/07/91)
I posted an "en passant" remark about a bunch of my postings to comp.sys.3b1
never making it out to the world. Last night, at dinner after a computer
meeting, Dave Herron (dherron@twg.com) commented in response to my question
the files could be found in /usr/spool/news/.rnews and that they were placed
there while expire is running (causing the "Your post is spooled for later
processing" messages when originally posted).
I checked, and, by golly, they ARE there!
Question: HOW to fire these up so they make it out to the world?
There are two types of files:
executable cunbatch scripts, and
executable inews scripts
If you have some clues or know how to do this, please send email ASAP either
to me or to cs@btr.com (I'm just a customer/user here at BTR and would relay
the info to ``cs'' anyway). BTR is running bnews on SunOS 4.0.* if that
makes any difference.
Many thanks!
Thad
P.S. For reference, here's a partial listing of the type of files about which
I'm talking about (my posts are the "small" files):
[...]
-rw-r--r-- 1 news 295965 Feb 25 06:26 910225142660e3
-rw-r--r-- 1 news 1389 Mar 1 02:04 91030110052553
-rw-r--r-- 1 news 1403 Mar 1 02:19 91030110202583
-rw-r--r-- 1 news 1741 Mar 1 02:29 910301103025a3
-rw-r--r-- 1 news 2395 Mar 1 02:42 910301104325c0
-rw-r--r-- 1 news 1470 Mar 1 02:51 9103011052266a
-rw-r--r-- 1 news 255640 Mar 1 03:05 910301110531e3
-rw-r--r-- 1 news 2311 Mar 1 03:05 91030111062719
-rw-r--r-- 1 news 1443 Mar 1 03:11 91030111122743
-rw-r--r-- 1 news 242874 Mar 1 03:16 910301111631eb
-rw-r--r-- 1 news 888 Mar 1 04:12 910301121327d3
[...]
and here's a "file *" of the same range of files:
[...]
/usr/spool/news/.rnews/910225142660e3: executable cunbatch script
/usr/spool/news/.rnews/91030110052553: executable inews script
/usr/spool/news/.rnews/91030110202583: executable inews script
/usr/spool/news/.rnews/910301103025a3: executable inews script
/usr/spool/news/.rnews/910301104325c0: executable inews script
/usr/spool/news/.rnews/9103011052266a: executable inews script
/usr/spool/news/.rnews/910301110531e3: executable cunbatch script
/usr/spool/news/.rnews/91030111062719: executable inews script
/usr/spool/news/.rnews/91030111122743: executable inews script
/usr/spool/news/.rnews/910301111631eb: executable cunbatch script
/usr/spool/news/.rnews/910301121327d3: executable inews script
[...]
Thad Floryan [ thad@btr.com (OR) {decwrl, mips, fernwood}!btr!thad ]clewis@ferret.ocunix.on.ca (Chris Lewis) (03/09/91)
In article <2026@public.BTR.COM> thad@btr.btr.com writes: >I posted an "en passant" remark about a bunch of my postings to comp.sys.3b1 >never making it out to the world. Last night, at dinner after a computer >meeting, Dave Herron (dherron@twg.com) commented in response to my question >the files could be found in /usr/spool/news/.rnews and that they were placed >there while expire is running (causing the "Your post is spooled for later >processing" messages when originally posted). >I checked, and, by golly, they ARE there! >Question: HOW to fire these up so they make it out to the world? I sent mail, but my mail system is a bit flakey at the moment, so I'm posting too: In bnews, to unstick news, run "rnews -U". It's a good idea to place an "rnews -U" into your crontab to be run a couple of times per day. Especially an hour or so after your cron fires up expire. You can configure bnews to not unbatch stuff, just placing incoming stuff into .rnews, for later processing by an "rnews -U" at a better time (handy for deferring the unbatching until a less loaded time). This usually only happens with incoming feeds, not locally generated articles, but you can deferr locally generated articles too. B-news is SUPPOSED to run an "rnews -U" at the end of an expire run, but I've seen *that* not work on some systems. -- Chris Lewis, clewis@ferret.ocunix.on.ca or ...uunet!mitel!cunews!latour!ecicrl!clewis Psroff support: psroff-request@eci386.uucp, or call 613-832-0541 (Canada)
thad@public.BTR.COM (Thaddeus P. Floryan) (03/11/91)
In article <1991Mar08.200236.10786@ferret.ocunix.on.ca> clewis@ferret.ocunix.on.ca.UUCP (Chris Lewis) writes: >[...] >In bnews, to unstick news, run "rnews -U". It's a good idea to place >an "rnews -U" into your crontab to be run a couple of times per day. >Especially an hour or so after your cron fires up expire. >[...] Many, MANY thanks to Chris and to everyone else who responded with solutions for the "stuck" bnews spooled files. The management at BTR has implemented your solutions and everything is working fine here presently. I am personally thanking everyone who sent email help. Thad Floryan [ thad@btr.com (OR) {decwrl, mips, fernwood}!btr!thad ]
mikebe@i88.isc.com (Michael G. Beirne) (03/12/91)
In article <1991Mar08.200236.10786@ferret.ocunix.on.ca> clewis@ferret.ocunix.on.ca.UUCP (Chris Lewis) writes: >In article <2026@public.BTR.COM> thad@btr.btr.com writes: >>I posted an "en passant" remark about a bunch of my postings to comp.sys.3b1 >>never making it out to the world. Last night, at dinner after a computer >>meeting, Dave Herron (dherron@twg.com) commented in response to my question >>the files could be found in /usr/spool/news/.rnews and that they were placed >>there while expire is running (causing the "Your post is spooled for later >>processing" messages when originally posted). > >>I checked, and, by golly, they ARE there! > >>Question: HOW to fire these up so they make it out to the world? > >I sent mail, but my mail system is a bit flakey at the moment, so I'm >posting too: > >In bnews, to unstick news, run "rnews -U". It's a good idea to place This should be run as user news. One place I worked limited the size of a file a user could create to 2 meg. The history file for news is usually larger than 2 meg. Child processes inherit the limits of their parents. Therefore if you run "rnews -U" on a system that has such a limit you will corrupt the history file and cause even more grief for yourself as old articles will not get expired because they are not in the history file. To check the size of files you are allowed to create type "ulimit". This works in both csh and ksh but not in sh. >an "rnews -U" into your crontab to be run a couple of times per day. >Especially an hour or so after your cron fires up expire. >B-news is SUPPOSED to run an "rnews -U" at the end of an expire run, >but I've seen *that* not work on some systems. >-- >Chris Lewis, >clewis@ferret.ocunix.on.ca or ...uunet!mitel!cunews!latour!ecicrl!clewis >Psroff support: psroff-request@eci386.uucp, or call 613-832-0541 (Canada) -- mikebe@i88.isc.com or beirne@chinet.chi.il.us