Google Groups no longer supports new Usenet posts or subscriptions. Historical content remains viewable.
Dismiss

pty problem

11 views
Skip to first unread message

Eugene Grosbein

unread,
May 23, 2003, 8:02:57 AM5/23/03
to
Привет!

Кто-нибудь знает, что за фигня иногда начинает творится на
FreeBSD 4.8-STABLE (замечалось и раньше немного) с pty:

1) screen вылетает сразу после старта, в зависимости от настроек
может успеть написать:

fgtty: Inappropriate ioctl for device

Hо быстро затирает это сообщение.

Вот конец ktrace:

37390 screen CALL lstat(0x8077f78,0xbfbff8b4)
37390 screen NAMI "/tmp/screens"
37390 screen RET lstat -1 errno 2 No such file or directory
37390 screen CALL mkdir(0x8077f78,0x1ed)
37390 screen NAMI "/tmp/screens"
37390 screen RET mkdir 0
37390 screen CALL access(0x8084920,0)
37390 screen NAMI "/tmp/screens/S-eu"
37390 screen RET access -1 errno 2 No such file or directory
37390 screen CALL mkdir(0x8084920,0x1c0)
37390 screen NAMI "/tmp/screens/S-eu"
37390 screen RET mkdir 0
37390 screen CALL chown(0x8084920,0,0)
37390 screen NAMI "/tmp/screens/S-eu"
37390 screen RET chown 0
37390 screen CALL stat(0x8084920,0xbfbff8b4)
37390 screen NAMI "/tmp/screens/S-eu"
37390 screen RET stat 0
37390 screen CALL umask(0x12)
37390 screen RET umask 0
37390 screen CALL __sysctl(0xbfbff40c,0x2,0x8084fe0,0xbfbff408,0,0)
37390 screen RET __sysctl 0
37390 screen CALL sigaction(0x1,0xbfbff3e4,0xbfbff3fc)
37390 screen RET sigaction 0
37390 screen CALL fork
37390 screen RET fork 37392/0x9210
37390 screen CALL setgid(0)
37390 screen RET setgid 0
37390 screen CALL setuid(0)
37390 screen RET setuid 0
37390 screen CALL sigaction(0x1,0xbfbff3c4,0xbfbff3dc)
37390 screen RET sigaction 0
37390 screen CALL sigaction(0x1,0xbfbff3b4,0xbfbff3cc)
37390 screen RET sigaction 0
37390 screen CALL sigaction(0x1e,0xbfbff3c4,0xbfbff3dc)
37390 screen RET sigaction 0
37390 screen CALL sigaction(0x1f,0xbfbff3b4,0xbfbff3cc)
37390 screen RET sigaction 0
37390 screen CALL sigaction(0x2,0xbfbff3c4,0xbfbff3dc)
37390 screen RET sigaction 0
37390 screen CALL sigaction(0x12,0xbfbff3b4,0xbfbff3cc)
37390 screen RET sigaction 0
37390 screen CALL sigaction(0x1c,0xbfbff3c4,0xbfbff3dc)
37390 screen RET sigaction 0
37390 screen CALL sigaction(0xe,0xbfbff3c4,0xbfbff3dc)
37390 screen RET sigaction 0
37390 screen CALL setitimer(0,0xbfbff3d4,0xbfbff3c4)
37390 screen RET setitimer 0
37390 screen CALL sigprocmask(0x1,0xbfbff3b8,0xbfbff3a8)
37390 screen RET sigprocmask 0
37390 screen CALL sigsuspend(0xbfbff3b4)
37390 screen PSIG SIGHUP caught handler=0x8064450 mask=0x0 code=0x0
37390 screen RET sigsuspend -1 errno 4 Interrupted system call
37390 screen CALL sigaction(0x1,0xbfbfe4e8,0xbfbfe500)
37390 screen RET sigaction 0
37390 screen CALL stat(0x8084920,0xbfbff178)
37390 screen NAMI "/tmp/screens/S-eu/37392.ttyv1.www"
37390 screen RET stat -1 errno 2 No such file or directory
37390 screen CALL exit(0)

2) mc с subshell тоже вылетат с диагностикой:

subshell.c: read (subshell_pty...): Unknown error: 0

mc -u запускается и работает.

Вот кусочек ktrace (конец):

36868 mc RET read 858/0x35a
36868 mc CALL close(0x5)
36868 mc RET close 0
36868 mc CALL open(0x80f2620,0x2,0x4)
36868 mc NAMI "/dev/ttyp0"
36868 mc RET open 5
36868 mc CALL pipe
36868 mc RET pipe 6
36868 mc CALL fork
36868 mc RET fork 36869/0x9005
36868 mc CALL close(0x5)
36868 mc RET close 0
36868 mc CALL write(0x4,0xbfbffa70,0x27)
36868 mc GIO fd 4 wrote 39 bytes
" PROMPT_COMMAND='pwd>&7;kill -STOP $$'
"
36868 mc RET write 39/0x27
36868 mc CALL sigaction(0x2,0xbfbffa38,0)
36868 mc RET sigaction 0
36868 mc CALL select(0x7,0xbfbff9c0,0,0,0xbfbff9b8)
36868 mc RET select 1
36868 mc CALL read(0x4,0x8110380,0x64)
36868 mc GIO fd 4 read 40 bytes
" PROMPT_COMMAND='pwd>&7;kill -STOP $$'\r
"
36868 mc RET read 40/0x28
36868 mc CALL select(0x7,0xbfbff9c0,0,0,0xbfbff9b8)
36868 mc RET select 1
36868 mc CALL read(0x4,0x8110380,0x64)
36868 mc GIO fd 4 read 0 bytes
""
36868 mc RET read 0
36868 mc CALL ioctl(0x1,TIOCSETA,0x80f2b60)
36868 mc RET ioctl 0
36868 mc CALL writev(0x2,0xbfbff950,0x4)
36868 mc GIO fd 2 wrote 54 bytes
"
subshell.c: read (subshell_pty...): Unknown error: 0
"
36868 mc RET writev 54/0x36
36868 mc CALL exit(0x1)

Eugene
--
"Люди забыли эту истину," - сказал Лис, - "но ты не забывай"

Vladimir Kurtukov

unread,
May 27, 2003, 10:52:01 AM5/27/03
to
Hello Eugene.

23 May 03 17:02, you wrote to all:

EG> 2) mc с subshell тоже вылетат с диагностикой:

EG> subshell.c: read (subshell_pty...): Unknown error: 0

вроде помогало killall -CONT <your shell>

Vladimir

0 new messages