signals not working in shells run under emacs on SUSE 6.3

[Robert L Krawitz]

   Date: Mon, 14 Feb 2000 20:40:41 -0500
   From: Jerry Callen <jcallen at narsil.com>

   Proc         Status   Buffer         Tty         Command
   ----         ------   ------         ---         -------
   shell	     run      *shell*	     (none)	 /bin/bash -i

   When I do it as root, I get this:

   Proc         Status   Buffer         Tty         Command
   ----         ------   ------         ---         -------
   shell	     run      *shell*	     /dev/ttyp0	 /bin/bash -i

   So the root process has a (presumably pseudo) tty. BTW, this
   is running emacs as an X client, not in a terminal emulator.

Well, that's certainly the problem, all right -- ^C, ^Z and friends
only mean anything to the tty driver as far as sending interrupts go.
Under SuSE 6.2, M-x list-processes gives me this:

Proc         Status   Buffer         Tty         Command
----         ------   ------         ---         -------
shell	     run      *shell*	     /dev/ttyp1	 /bin/bash -i

What are the protections on your tty's and pty's starting with
/dev/tty*?  Mine look like this:

$ ls -l /dev/ttyp*
crw-------   1 root     tty        3,   0 Jul 22  1999 /dev/ttyp0
crw-rw-rw-   1 root     tty        3,   1 Feb 14 20:47 /dev/ttyp1
crw-rw-rw-   1 root     tty        3,   2 Feb 14 11:21 /dev/ttyp2
crw-rw-rw-   1 root     tty        3,   3 Feb 11 18:48 /dev/ttyp3
crw-rw-rw-   1 root     tty        3,   4 Feb 14 20:49 /dev/ttyp4
crw-rw-rw-   1 root     tty        3,   5 Jul 22  1999 /dev/ttyp5
crw-rw-rw-   1 root     tty        3,   6 Jul 22  1999 /dev/ttyp6
crw-rw-rw-   1 root     tty        3,   7 Jul 22  1999 /dev/ttyp7
crw-rw-rw-   1 root     tty        3,   8 Jul 22  1999 /dev/ttyp8
crw-rw-rw-   1 root     tty        3,   9 Jul 22  1999 /dev/ttyp9
crw-rw-rw-   1 root     tty        3,  10 Jul 22  1999 /dev/ttypa
crw-rw-rw-   1 root     tty        3,  11 Jul 22  1999 /dev/ttypb
crw-rw-rw-   1 root     tty        3,  12 Jul 22  1999 /dev/ttypc
crw-rw-rw-   1 root     tty        3,  13 Jul 22  1999 /dev/ttypd
crw-rw-rw-   1 root     tty        3,  14 Jul 22  1999 /dev/ttype
crw-rw-rw-   1 root     tty        3,  15 Jul 22  1999 /dev/ttypf
$ ls -l /dev/ptyp*
crw-rw-rw-   1 root     tty        2,   0 Jul 22  1999 /dev/ptyp0
crw-rw-rw-   1 root     tty        2,   1 Feb 14 20:47 /dev/ptyp1
crw-rw-rw-   1 root     tty        2,   2 Feb 14 11:21 /dev/ptyp2
crw-rw-rw-   1 root     tty        2,   3 Feb 11 18:48 /dev/ptyp3
crw-rw-rw-   1 root     tty        2,   4 Jul 22  1999 /dev/ptyp4
crw-rw-rw-   1 root     tty        2,   5 Jul 22  1999 /dev/ptyp5
crw-rw-rw-   1 root     tty        2,   6 Jul 22  1999 /dev/ptyp6
crw-rw-rw-   1 root     tty        2,   7 Jul 22  1999 /dev/ptyp7
crw-rw-rw-   1 root     tty        2,   8 Jul 22  1999 /dev/ptyp8
crw-rw-rw-   1 root     tty        2,   9 Jul 22  1999 /dev/ptyp9
crw-rw-rw-   1 root     tty        2,  10 Jul 22  1999 /dev/ptypa
crw-rw-rw-   1 root     tty        2,  11 Jul 22  1999 /dev/ptypb
crw-rw-rw-   1 root     tty        2,  12 Jul 22  1999 /dev/ptypc
crw-rw-rw-   1 root     tty        2,  13 Jul 22  1999 /dev/ptypd
crw-rw-rw-   1 root     tty        2,  14 Jul 22  1999 /dev/ptype
crw-rw-rw-   1 root     tty        2,  15 Jul 22  1999 /dev/ptypf

There might be some kind of security setting in 6.3 about whether user
programs are allowed to allocate ptys.  I don't have anything like
that in 6.2, but it's a reasonable guess that something like that's
going on with you.

The other possibility I would check is that one of your pty's
(specifically, the first unused one) has accidentally been set to
something other than 666 and emacs gives up after that attempt fails.

-- 
Robert Krawitz <rlk at alum.mit.edu>      http://www.tiac.net/users/rlk/

Tall Clubs International  --  http://www.tall.org/ or 1-888-IM-TALL-2
Member of the League for Programming Freedom -- mail lpf at uunet.uu.net
Project lead for The Gimp Print --  http://gimp-print.sourceforge.net

"Linux doesn't dictate how I work, I dictate how Linux works."
--Eric Crampton
-
Subcription/unsubscription/info requests: send e-mail with
"subscribe", "unsubscribe", or "info" on the first line of the
message body to discuss-request at blu.org (Subject line is ignored).