Subject: Hanging MOO server and o_n_c()

From: Mike Prudence <[email-masked]>
Date: Wed, 21 Apr 1993 06:44:36 -0700

Hi all,

We've got a bit of a problem with the MOO running here at HP.  We're
on 1.7.0, with a database gotten from an ancient LambdaCore.  Our
symptom is a server lockup caused suspiciously around the time that a
database dump is performed.  It's now happened twice, and we've
previously been running trouble free for months at a time.

I've noticed a defunct child process hanging around when the MOO
hangs, and the server itself just sits there - accepting no
connections, consuming no CPU time.

So - has anyone seen anything similar ?  Our machine is a HP9000/835,
running HP-UX 8.0.

On a possibly related note, I've just started playing around with
using outboard number crunchers for MOO tasks, and this means we have
a lot of open_network_connections() going on.  Is there any chance
that using this server feature could cause some sort of lockup ?  Just
wondering - you never know.

Cheers,

Mike/blip

[email-masked]                   "Only those who attempt the absurd will 
                                                     achieve the impossible."

---

From: Andrew Wilson <[email-masked]>
Date: Wed, 21 Apr 1993 10:14:57 -0700

>wondering - you never know.

You're not the only person harbouring the suspicion that there IS something
nasty happening when the server tries to dump AND there's onc()s hanging
around.  Wasn't there a server mod announced a while back, or some reference
made to a change to the onc() part of the server source. I'm too lazy to
scan back-issues of moo-cows myself.  Anyone feel like saying more on the
subject.

Andy (Networker)