Date: Mon, 22 Jul 2002 21:50:28 +0200 From: Gerhard Sittig <Gerhard.Sittig@gmx.net> To: freebsd-stable@freebsd.org Subject: Re: PAM... HELP!! Message-ID: <20020722215028.D1494@shell.gsinet.sittig.org> In-Reply-To: <89773.1027287205@verdi.nethelp.no>; from sthaug@nethelp.no on Sun, Jul 21, 2002 at 11:33:25PM %2B0200 References: <20020721223830.T24610-100000@phoenix.vh.laserfence.net> <89773.1027287205@verdi.nethelp.no>
next in thread | previous in thread | raw e-mail | index | archive | help
On Sun, Jul 21, 2002 at 23:33 +0200, sthaug@nethelp.no wrote:
>
> > Hi, I recently did a make world on a remote system, and now find myself
> > locked out, apart from one SSH connection I left running, however, dialups
> > don't last forever and I will have to close that connection soon. Is there
> > any way I can get SSH to work around PAM for the meantime, and is this
> > problem fixed yet (a desparate cvsup is now in progress)
>
> What worked for me:
>
> - install new /etc/pam.conf (from /usr/src/etc/pam.conf)
> - install new /etc/ssh/sshd_config (from /usr/src/crypto/openssh/sshd_config)
This is another way of saying "I ran mergemaster".
> - restart the running master sshd (/usr/sbin/sshd)
This is another way of saying "I started sshd after running
mergemaster in single user mode".
To sum it up: The sequence of steps from UPDATING is correct
and doesn't show the problem. Those who insist in doing things
in a different way should be prepared to meet failures and are
expected to (be able to) help themselves out. (yes, I can
certainly be considered a smartass:)
Even for remote upgrades there have been multiple hints in the
numerous threads in this list (this is the point where this post
is not just a simple "I told you ..."): serial consoles (with
concentrators or "cross over" connecting two remote machines),
installing systems on new disks and shipping / simply swapping
the disk, installing to a second disk remotely (think DESTDIR)
and rebooting into the first system should the updated one fail,
etc etc ...
One might get away often times without running single user mode.
But one should be prepared when it doesn't work. There is a
reason for the suggested procedure (often explained and easily
found in the archive, search for "updat" or "single user" and
"colo" or "remote").
virtually yours 82D1 9B9C 01DC 4FB4 D7B4 61BE 3F49 4F77 72DE DA76
Gerhard Sittig true | mail -s "get gpg key" Gerhard.Sittig@gmx.net
--
If you don't understand or are scared by any of the above
ask your parents or an adult to help you.
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?20020722215028.D1494>