innd stops responding

[Alex Kiernan]

On Mon, 19 Jul 2004 09:39:59 -0500, Heath Kehoe <hakehoe at avalon.net> wrote:
> > Certainly the behaviour you're seeing is typical for ovdb on Solaris;
> > I'm not sure if anyone's addressed the way nnrpd does termination yet,
> > but last time I looked it seemed like if you took a signal at the
> > wrong moment, nnrpd would try and make calls into ovdb (and hence
> > BerkeleyDB) in a re-entrant fashion, which isn't supported (not
> > unreasonably) by BerkeleyDB.
> 
> Whoa!!!  I never knew about this.  OK, looks like the sigpipe handler
> calls ExitWithStats.  Yuck!!  But how often does nnrpd exit in this way?
> 

Any time the user abandons the connection (which I suspect with
something like OE is often).

> There's an easy workaround:  turn on readserver in ovdb.conf, and
> restart
> news.  With readserver on, the nnrpd doesn't access BerkeleyDB directly,
> thus avoiding the signal handler problem.
> 

Ah, I'd forgotten that one!

-- 
Alex Kiernan