Path: utzoo!utgpu!news-server.csri.toronto.edu!cs.utexas.edu!samsung!uunet!europa.asd.contel.com!noc.sura.net!mars!orion!stodola
From: stodola@orion.fccc.edu (Robert K. Stodola)
Newsgroups: comp.unix.ultrix
Subject: Blank lines in config files (Was: Warning about /etc/inetd.conf)
Message-ID: <1991Jun20.194026.26908@fccc.edu>
Date: 20 Jun 91 19:40:26 GMT
References: <8736@jhunix.HCF.JHU.EDU>
Sender: news@fccc.edu (USENET News System)
Organization: Fox Chase Cancer Center, Philadelphia PA
Lines: 20
Nntp-Posting-Host: relay.fccc.edu

In article <8736@jhunix.HCF.JHU.EDU> barrett@jhunix.HCF.JHU.EDU (Dan Barrett)
writes:
>
>	Guess what I just found out the hard way?  If you have any blank
>lines in /etc/inetd.conf, then inetd silently refuses to start up.
>In fact, it returns a "success" exit code (0) and then dies.
>
>	I hope this information helps somebody.  I just pulled my hair out
>over it.
>

To save some more hair: when you are using a distributed password file using
the Hesiod name server and leave a blank line at the end of the src/passwd
file and then type 'make passwd', everything seems OK, but the name server
decides there is an error in the database and won't update secondary servers.

Didn't lose any hair, but did lose a largish number of hours on it.
-- 

stodola@fccc.edu -- Robert K. Stodola (occasionally) speaks for himself.