Date: Mon, 22 Jul 2002 22:37:19 +0200 From: sthaug@nethelp.no To: Gerhard.Sittig@gmx.net Cc: freebsd-stable@freebsd.org Subject: Re: PAM... HELP!! Message-ID: <4896.1027370239@verdi.nethelp.no> In-Reply-To: Your message of "Mon, 22 Jul 2002 21:50:28 %2B0200" References: <20020722215028.D1494@shell.gsinet.sittig.org>
next in thread | previous in thread | raw e-mail | index | archive | help
> > > 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". Except this is quite a bit quicker. > > - restart the running master sshd (/usr/sbin/sshd) > > This is another way of saying "I started sshd after running > mergemaster in single user mode". Please note what the original writer said - remote login, only one SSH connection left. In this case, mergemaster in single user mode is not an alternative. > 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:) I tried to answer based on having seen the same problem myself, and what I did to solve it. I can well believe that following the steps in UPDATING would have worked if used from the start - but it's not always an alternative when you are locked out. > 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"). Remote upgrade (without single user, only a network connection) has been a lifesaver for me many times, and I certainly plan to continue doing upgrades this way. Yes, I am indeed prepared for the occasional failure - but as long as it works for me in 95% or 99% of the cases, it saves me a lot of time and frustration. Steinar Haug, Nethelp consulting, sthaug@nethelp.no 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?4896.1027370239>