Blank lines in config files (Was: Warning about /etc/inetd.conf)

Robert K. Stodola stodola at orion.fccc.edu
Fri Jun 21 05:40:26 AEST 1991


In article <8736 at jhunix.HCF.JHU.EDU> barrett at 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 at fccc.edu -- Robert K. Stodola (occasionally) speaks for himself.



More information about the Comp.unix.ultrix mailing list