Skip site navigation (1)Skip section navigation (2)
Date:      Fri, 19 Apr 2002 10:54:33 -0700
From:      "Bruce A. Mah" <bmah@FreeBSD.org>
To:        Mike Hoskins <mike@adept.org>
Cc:        freebsd-stable@FreeBSD.org
Subject:   Re: inetd_enable=? 
Message-ID:  <200204191754.g3JHsX55040957@intruder.bmah.org>
In-Reply-To: <20020419103335.G10179-100000@snafu.adept.org> 
References:  <20020419103335.G10179-100000@snafu.adept.org>

next in thread | previous in thread | raw e-mail | index | archive | help
If memory serves me right, Mike Hoskins wrote:

> Did inetd_enable in /etc/defaults/rc.conf begin defaulting to NO instead
> of YES?  After upgrading a box remotely, and rebooting...  I was stumped
> as to why I could ping it but not SSH to the box.  Checked UPDATING, and
> changed the ephemeral port range back thinking that may be the cause...
> Then I started using my head for more than a hat rack, and noted that ps
> didn't show inetd running. (Always check the simplest things last!)  I
> usually run sshd, but this box is rarely touched in person so I'd opted
> to call it from inetd.

Yes, it changed as part of a mega-MFC of files in /etc, though there's a
bit of debate as to whether or not it *should* have changed.  :-)

It should be mentioned in UPDATING and the release notes.  As custodian
of the latter, I was going to wait to see what the final resolution of
this issue is, before writing it up.

Bruce.



To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-stable" in the body of the message




Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?200204191754.g3JHsX55040957>