I've compiled 2.5.1p1 on
HP-UX mdv010 B.11.00 A 9000/887 457369232 two-user license
with --prefix=/usr --sysconfdir=/etc/ssh \
--with-ssl-dir=$MYPWD/openssl-0.9.6 \
--with-pid-dir=/etc/ssh \
--with-default-path=/bin:/usr/bin:/sbin:/usr/sbin:/usr/local/bin
--with-entropy-timeout=250
Nothin special I think, works fine with 2.3.0p1.
Well, when I try to stop a process using CTRL+C (CTRL+Z does not work
too) nothing happens.
Is it a known problem?
Randolf
--
+---------------------------------------------------------------------+
| Randolf Skerka http://www.randolf.org |
+---------------------------------------------------------------------+
On Wed, 21 Feb 2001, Randolf Skerka wrote: : I've compiled 2.5.1p1 on : : HP-UX mdv010 B.11.00 A 9000/887 457369232 two-user license : : with --prefix=/usr --sysconfdir=/etc/ssh \ : --with-ssl-dir=$MYPWD/openssl-0.9.6 \ : --with-pid-dir=/etc/ssh \ : --with-default-path=/bin:/usr/bin:/sbin:/usr/sbin:/usr/local/bin : --with-entropy-timeout=250 : : Nothin special I think, works fine with 2.3.0p1. : : Well, when I try to stop a process using CTRL+C (CTRL+Z does not work : too) nothing happens. i don't see this on hp-ux 11. what does stty -a show? does it work if you do stty intr ^c
I can't help but notice this sounds just like the problem I have on my Solaris 2.6 boxen. If you search the list archives from several months ago, you can find the work around I posted. Basicly it all boiled down to the state of CTRL-C at the time sshd was launched. Go to the console of the machine in question (if you can), stop sshd and start sshd _INTERACTIVELY_ (do not use a cron job, at job, or anything else that is not interactive). Then ssh into the box and see if the CTRL-C works. If it does, you have the same problem we have on Solaris 2.6. Sshd seems to remeber the state of CTRL-C funcitonality at the time of startup and propigates that to all ssh sessions (even though stty reports otherwise). Stopping sshd and starting it from an at job or cron job when upgrading will give you a daemon that has no CTRL-C functionality (interupt key does not exist in the non-interactive shells of at and cron). -Garrick On Wed, 21 Feb 2001, Randolf Skerka wrote:> > I've compiled 2.5.1p1 on > > HP-UX mdv010 B.11.00 A 9000/887 457369232 two-user license > > with --prefix=/usr --sysconfdir=/etc/ssh \ > --with-ssl-dir=$MYPWD/openssl-0.9.6 \ > --with-pid-dir=/etc/ssh \ > --with-default-path=/bin:/usr/bin:/sbin:/usr/sbin:/usr/local/bin > --with-entropy-timeout=250 > > Nothin special I think, works fine with 2.3.0p1. > > Well, when I try to stop a process using CTRL+C (CTRL+Z does not work > too) nothing happens. > > > Is it a known problem? > > > Randolf > -- > +---------------------------------------------------------------------+ > | Randolf Skerka http://www.randolf.org | > +---------------------------------------------------------------------+ > >
Hi, On Wed, Feb 21, 2001 at 10:05:41AM -0800, Garrick James wrote:> Basicly it all boiled down to the state of CTRL-C at the time sshd was > launched. Go to the console of the machine in question (if you can), stop[..] Exactly. I thought we got this fixed, resetting the signal handler for SIGINT? Ages ago? gert -- USENET is *not* the non-clickable part of WWW! //www.muc.de/~gert/ Gert Doering - Munich, Germany gert at greenie.muc.de fax: +49-89-35655025 gert.doering at physik.tu-muenchen.de