Date: Wed, 6 May 1998 06:10:02 -0700 (PDT) From: archer@lucky.net To: freebsd-gnats-submit@FreeBSD.ORG Subject: bin/6536: pppd doesn't restore drainwait for tty Message-ID: <199805061310.GAA26134@hub.freebsd.org>
next in thread | raw e-mail | index | archive | help
>Number: 6536 >Category: bin >Synopsis: pppd doesn't restore drainwait for tty >Confidential: no >Severity: serious >Priority: medium >Responsible: freebsd-bugs >State: open >Quarter: >Keywords: >Date-Required: >Class: sw-bug >Submitter-Id: current-users >Arrival-Date: Wed May 6 06:10:01 PDT 1998 >Last-Modified: >Originator: Alexander Litvin >Organization: Lucky Net Ltd >Release: 2.2.6-STABLE >Environment: FreeBSD sivka.carrier.kiev.ua 2.2.6-STABLE FreeBSD 2.2.6-STABLE #2: Wed May 6 1 1:31:57 EEST 1998 archer@sivka.carrier.kiev.ua:/usr/src/sys/compile/sivka i 386 >Description: I do not actually know at what exact conditions it happens, but sometimes when pppd receives SIGHUP, it fails somewhere with message "ioctl(PPPIOCSFLAGS): Inappropriate ioctl for device". When pppd exits after that, drainwait for that tty device is -1, and with such drainwait tty fails to accept large writes. For me it takes place with dgb0: PC/Xe 64K, I do not know if it is the case for other serial devices. >How-To-Repeat: Set up a dialup ppp server, using pppd and DIGI PX/Xe serial board. When pppd fails with "ioctl(PPPIOCSFLAGS): Inappropriate ioctl for device", check drainwait value for the tty (e.g. with comcontrol). >Fix: As a workaround I patched pppd to restore drainwait value. >Audit-Trail: >Unformatted: To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-bugs" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?199805061310.GAA26134>