RE: OpenBSD Secure Shell
On Fri, 21 Apr 2000, Christian Pernegger wrote:
> It's already filed as a bug.
>
> [CTRL]-[C]
>
> ...# dpkg --pending --configure
>
> or something similar will fix everything (I think.)
I saw this on i386 today when doing an update (reason why they say don't
run frozen on critical systems. -- Hrmmph, the hardware is less stable)
I was doing the update through 'apt-get' over SSH when the daemon wouldn't
restart. Did the update again at the console and it was fine.
--
Beiad
> Christian
>
> > -----Original Message-----
> > From: Jim McCloskey [mailto:mcclosk@ling.ucsc.edu]
> > Sent: Friday, April 21, 2000 12:57 AM
> > To: debian-user@lists.debian.org
> > Cc: phil@hands.com
> > Subject: OpenBSD Secure Shell
> >
> >
> >
> > When I did an upgrade against `froozen' today, the post-install script
> > for OpenBSD Secure Shell hung. PS reports it as a zombie process. The
> > last message to the console was:
> >
> > Unpacking replacement ssh ...
> > Setting up ssh (1.2.3-2) ...
> > Starting OpenBSD Secure Shell server: sshd.
> >
> > The server was not started. (I had answered NO when asked if I wanted the
> > server configured with the SUID bit set.)
> >
> > I was able to fix things (I think---haven't tried it much yet)
> > by running dpkg --configure ssh ,
> >
> > Jim McCloskey
> >
> >
> > --
> > Unsubscribe? mail -s unsubscribe
> > debian-user-request@lists.debian.org < /dev/null
> >
>
>
> --
> Unsubscribe? mail -s unsubscribe debian-user-request@lists.debian.org < /dev/null
>
Reply to: