On 04/17/06 09:16:00, Jukka Salmi wrote:

> When using /bin/sh this problem doesn't exist. However, using an old
> (2004-01-01) ksh didn't fix the problem...
>=20
> Is anybody else seeing this?

Yes. I also think I know what changed that causes this. Since
http://cvsweb.be.netbsd.org/cgi-bin/cvsweb.cgi/src/usr.bin/login/login_pam.=
c.diff?r2=3D1.16&r1=3D1.15&f=3DH

pam_login restores SIGINT to its previous value. However, the previous =20
value as saved on line 534 is SIG_IGN, because it was set so already on =20
line 157. My guess is /bin/sh explicitly sets SIGINT to the default.

(As a workaround you can put 'trap - 2' in your .profile )

Kind regards
dieter

>=20
>=20
> Regards, Jukka
>=20
> --
> bashian roulette:
> $ ((RANDOM%6)) || rm -rf ~
>=20
>=20