The original post:
>Frequently when we reboot our Sun servers and workstations, some
>services from inetd.conf do not get started. Instead, error messages
>such as "in.rlogind: service not available" are displayed. However, if
>I kill -HUP inetd after rebooting (thereby forcing it to rescan
>inetd.conf) the services that fell through the cracks when booting will
>start (sometimes I have to kill -HUP a number of times to get a "clean"
>rescan without error messages).
>Unforunately, the services that don't start are not consistently
>reproducible. The problem occurs with different services seemingly at
>random and sometimes the problem doesn't occur at all.
>Is there some sort of limit on the size of inetd.conf? The problem
>seems to get better (but not disappear) when some unused services are
>removed from inetd.conf.
>Any suggestions, common experiences, etc. would be greatly
>Oh yeah. SPARC 10/51 SunOS 4.1.3 plenty of RAM etc.
>- jeff -
>Jeff Gordon email@example.com
The overwhelming response was to check for and remove any blank lines that
might be in inetd.conf and services (/etc and NIS) - sure enough we had
a blank line in services.
Thanks to all who responded:
Barry Margolin <barmar@Think.COM>
Brett M Hogden <firstname.lastname@example.org>
Dave Mitchell <D.Mitchell@dcs.shef.ac.uk>
Mike Raffety <email@example.com>
Scott McWilliams <firstname.lastname@example.org>
Tim.Griffin@fw.gs.com (Tim Griffin - Systems Consultant)
Tim.Tokarsky@dssserv.fw.gs.com (Timothy Tokarsky)
brett@bsysparc.Bentley.COM (Brett S. Yeagley)
email@example.com (Linda Cygan)
firstname.lastname@example.org (Danny Johnson)
email@example.com (David H. Brierley)
firstname.lastname@example.org (Donald McLachlan)
email@example.com (Fredrik Nyman)
firstname.lastname@example.orgPont.com (Tim Evans)
- jeff -
This archive was generated by hypermail 2.1.2 : Fri Sep 28 2001 - 23:09:06 CDT