INN 1.2 newgroup control message problem

Thread View: news.software.b

3 messages

[T] Back to Threads [V] Tree View [G] Group Articles

3 total messages Started by J Greely Tue, 26 Jan 1993 03:33

#5040

Author: J Greely
Date: Tue, 26 Jan 1993 03:33

14 lines
1212 bytes

All newgroup messages land in my newgroup.log file as "Unparseable".
My control.ctl file is stock (irrelevant, I'd say, since it doesn't
seem to be getting that far).  I even used the supplied makegroup
script to generate a sample newgroup, and, sure enough, the log file
reports:
	Unparseable newgroup by news@cis.ohio-state.edu

  I'm running SunOS 4.1.1 (patched for the dbzsync problem), and have
INN configured to use GNU sed 1.12, GNU grep 1.6, and GNU gawk 2.13.
RTFM and RTFFAQ have offered no solutions (having the filesystem break
my news2mail gateways didn't help either, but that's another
story...).  Anyone?
-- 
J Greely (jgreely@cis.ohio-state.edu; osu-cis!jgreely)

Re: INN 1.2 newgroup control message problem

#5045

Author: Rich Salz
Date: Thu, 28 Jan 1993 15:53

15 lines
1164 bytes

In <JGREELY.93Jan25223322@morganucodon.cis.ohio-state.edu> jgreely@morganucodon.cis.ohio-state.edu (J Greely) writes:
>All newgroup messages land in my newgroup.log file as "Unparseable".
>	Unparseable newgroup by news@cis.ohio-state.edu
Looking at samples/newgroup, this message is generated when the command
line has more than two parameters.  Double-check the article and make
sure that it really looks like this:
	Control: newgroup osu.wombats moderated
or some such.

>My control.ctl file is stock (irrelevant, I'd say, since it doesn't
>seem to be getting that far).
Not irrelevent; control.ctl is read by parsecontrol, which is called
first thing by newgroup.  If the newgroup scripts gets called it is
because control.ctl said "doit".
	/r$

Re: INN 1.2 newgroup control message problem

#5048

Author: J Greely
Date: Thu, 28 Jan 1993 18:58

13 lines
1344 bytes

In article <JGREELY.93Jan28130257@morganucodon.cis.ohio-state.edu>
 jgreely@morganucodon.cis.ohio-state.edu (J Greely) writes:
>and I'll poke at the GNU version to see if there's
>something obviously wrong with the way it's compiled here.

It didn't take much poking.  It appears from the source that commands of
the form:
	sed -n -e "s/foo/bar/p"
will never print anything in this version of GNU sed.  you have to use
something like this:
	sed -n -e "/foo/ {s//bar/;p;}"
-- 
J Greely (jgreely@cis.ohio-state.edu; osu-cis!jgreely)

Thread Navigation

This is a paginated view of messages in the thread with full content displayed inline.

Messages are displayed in chronological order, with the original post highlighted in green.

Use pagination controls to navigate through all messages in large threads.

Back to All Threads