*BSD News Article 77463


Return to BSD News archive

Path: euryale.cc.adfa.oz.au!newshost.carno.net.au!harbinger.cc.monash.edu.au!munnari.OZ.AU!news.mel.connect.com.au!news.mira.net.au!news.vbc.net!samba.rahul.net!rahul.net!a2i!news.PBI.net!news.mathworks.com!nntp.primenet.com!newspump.sol.net!news.mindspring.com!realtime.net!news
From: kevin@freeside.fc.net
Newsgroups: news.software.nntp,comp.unix.bsd.freebsd.misc,muc.lists.freebsd.hackers
Subject: nntplink problems with freebsd 2.1.0 / Please Help!
Date: 5 Sep 1996 03:46:39 GMT
Organization: Desperate and Frustrated, Inc.
Lines: 32
Distribution: inet
Message-ID: <841885628.7779@dejanews.com>
NNTP-Posting-Host: bastion.dejanews.com
X-RTcode: 2bed0d4a321f558ba62e4d55
X-Originating-IP-Addr: 204.145.225.22 (ministry.paranoia.com)
Xref: euryale.cc.adfa.oz.au news.software.nntp:25742 comp.unix.bsd.freebsd.misc:26560

I'm posting through DejaNews because this plea for help is too important to
leave up to my current FreeBSD 2.1.0-RELEASE, inn, and nntplink situation for
distribution.  Three people have spent many hours on this and I've finally
got to break down and ask "what the f&%@!" because I haven't been able to
locate anyone else's answer on the Net and there ought to be one. :)

We've tried five various versions of nntplink from 3.1.0 to 3.3beta4wdPL3
and a 3.3.1 that turned up from somewhere with the same basic result from
all of them.. a select(): Invalid argument error bombs things every time,
but only when nntplink is started from INN's newsfeeds.. it works just fine
when run from the command line (it's gone under gdb many times).  Studying
the kernel sources and cvsweb history, only two things should cause select()
to return EINVAL and I can't see that we're running into either of those.
Going with the 3.3pl2 (for example) configure script and defining HAVE_MMAP
and HAVE_WORKING_SELECT results in an instant crash (and respawning by innd)
of nntplink with a select():.*Invalid argument error every time.  Undefining
HAVE_MMAP doesn't have any effect.  Undefining HAVE_WORKING_SELECT bypasses
the code that causes it to abort immediately, but the select() calls still
fail and it never gets any news across.  It's got to be one simple thing,
but I need someone else's fresh insight on how to fix it.  I can't believe
that I haven't been able to locate a single reference on compiling nntplink
for FreeBSD (and it's not in the ports collection).. is nobody using it or
is my news server the only one having this problem?

Please copy any followups to me in email.  Patches and specifics especially
appreciated.  I'm dying to fix whatever it is.

thanks,
kevin
-----------------------------------------------------------------------
This article was posted to Usenet via the Posting Service at Deja News:
    http://www.dejanews.com/      [Search, Post, and Read Usenet News!]