Date: Fri, 19 Apr 2002 13:04:24 -0500 From: Christopher Schulte <schulte+freebsd@nospam.schulte.org> To: Mike Hoskins <mike@adept.org>, <freebsd-stable@freebsd.org> Subject: Re: inetd_enable=? Message-ID: <5.1.0.14.0.20020419125245.050f25e0@pop3s.schulte.org> In-Reply-To: <20020419103335.G10179-100000@snafu.adept.org>
next in thread | previous in thread | raw e-mail | index | archive | help
At 10:43 AM 4/19/2002 -0700, 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. Looks like this commit made inetd default to off in /etc/defaults/rc.conf. Was there a good reason to run sshd from inetd versus having it start as a daemon? If so, you should have explicitly told /etc/rc.conf you wanted inetd on, versus relying on it being a default. Revision 1.53.2.53 / (download) - annotate - [select for diffs] , Mon Apr 15 00:44:14 2002 UTC (4 days, 17 hours ago) by dougb Branch: RELENG_4 To make sure sshd stays alive after upgrading (assuming daemon invocation) 1) define sshd_enable="YES" in /etc/rc.conf - now changes in /etc/defaults/* won't impact you. 2) make sure you use mergemaster as part of your update routine, in case certain subsystem changes (PAM) require configuration tweaking to maintain workable service >Later, >-Mike > >-- >"They that can give up essential liberty to obtain a little temporary > safety deserve neither liberty nor safety." --Benjamin Franklin -- Christopher Schulte http://www.schulte.org/ Do not un-munge my @nospam.schulte.org email address. This address is valid. 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?5.1.0.14.0.20020419125245.050f25e0>