Skip site navigation (1)Skip section navigation (2)
Date:      Mon, 21 Jul 1997 12:35:58 -0400
From:      "Gary Palmer" <gpalmer@FreeBSD.ORG>
To:        "Jonathan A. Zdziarski" <jonz@netrail.net>
Cc:        freebsd-ports@FreeBSD.ORG
Subject:   Re: News Revisited 
Message-ID:  <22988.869502958@orion.webspan.net>
In-Reply-To: Your message of "Mon, 21 Jul 1997 10:58:12 -0000." <Pine.BSF.3.95q.970721105525.11649B-100000@netrail.net> 

next in thread | previous in thread | raw e-mail | index | archive | help
"Jonathan A. Zdziarski" wrote in message ID
<Pine.BSF.3.95q.970721105525.11649B-100000@netrail.net>:
> OK.  Running inn.  Set up fine, works fine, only our links with other
> people aren't working - we're getting no news coming in from uunet or
> anywhere else.  nntplink is set up and working (you can see the proc's
> running), and its saving to in.coming, but the messages are not saving to
> our disk.  I've so far had to learn inn in a total of about 10 hours of
> work, so I'm not familiar with how this process works.  Anybody have any
> bright ideas on how to get this going/check to see if its configured
> properly?

So you have inn running properly, and stuff is being saved in
in.coming? From readers (i.e. postings from customers) or your feeds?

>From memory nntplink is only for the outbound news link, and has
nothing to do with inbound articles.

I have abslutely no idea why you are getting rnews batches in your
in.coming directory if you are running innd and it is accepting the
connections on port 119, but you can run 'rnews -U' to `unbatch' the
stuff in in.coming.

What would be helpful is setting syslogd up to log the news facility
and looking in there for error messages. 

Gary
--
Gary Palmer                                          FreeBSD Core Team Member
FreeBSD: Turning PC's into workstations. See http://www.FreeBSD.ORG/ for info



Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?22988.869502958>