Path: utzoo!utgpu!news-server.csri.toronto.edu!rpi!zaphod.mps.ohio-state.edu!wuarchive!psuvax1!hsdndev!dartvax!news
From: kriso@lombard.dartmouth.edu (Kris Olander)
Newsgroups: comp.sys.hp
Subject: Inetd core dumping (fresh 7.0 install)
Message-ID: <1991Apr17.201807.5207@dartvax.dartmouth.edu>
Date: 17 Apr 91 20:18:07 GMT
Sender: news@dartvax.dartmouth.edu (The News Manager)
Distribution: usa
Organization: Dartmouth College, Hanover, NH
Lines: 38
Originator: kriso@lombard.dartmouth.edu

While I'm on a roll...

I just finished installing HP-UX 7.0 (third time :-< )

I've configured our lan card, and installed all the
ARPA products.

When netlinkrc tries to start inetd at boot time I
get:

netlinkrc 103 Bad System call - core dumped

at about the spot where inetd is supposed to start.
Further investigation shows that it is inetd which
is failing.  Starting inetd by hand, generating a log
file using the '-l' flag yields the following info:

"Caught signal 12
 KILLING INETD on (date/time)
 
 Unable to close semaphore: Invalid argument"

To successfully get inetd running, (the last time I
loaded HP-UX) it was necessary to rebuild a kernel
with System V semaphores.

Would some kind soul explain what's going on? 

Why didn't I see this when I 'upgraded' to HP-UX 7.0
from HP-UX 6.5?

(ps: /usr/lib/sendmail seems to be doing something
     similar.  Does this guess make sense?)


-- 
Kris Olander
--------------kris.olander@dartmouth.edu----------------