From nobody  Wed May  6 06:10:02 1998
Received: (from nobody@localhost)
          by hub.freebsd.org (8.8.8/8.8.8) id GAA26134;
          Wed, 6 May 1998 06:10:02 -0700 (PDT)
          (envelope-from nobody)
Message-Id: <199805061310.GAA26134@hub.freebsd.org>
Date: Wed, 6 May 1998 06:10:02 -0700 (PDT)
From: archer@lucky.net
To: freebsd-gnats-submit@freebsd.org
Subject: pppd doesn't restore drainwait for tty
X-Send-Pr-Version: www-1.0

>Number:         6536
>Category:       bin
>Synopsis:       pppd(8) doesn't restore drainwait for tty
>Confidential:   no
>Severity:       serious
>Priority:       medium
>Responsible:    freebsd-bugs
>State:          closed
>Quarter:        
>Keywords:       
>Date-Required:  
>Class:          sw-bug
>Submitter-Id:   current-users
>Arrival-Date:   Wed May  6 06:10:01 PDT 1998
>Closed-Date:    Sat May 15 14:43:11 UTC 2010
>Last-Modified:  Sat May 15 14:43:11 UTC 2010
>Originator:     Alexander Litvin
>Release:        2.2.6-STABLE
>Organization:
Lucky Net Ltd
>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.
>Release-Note:
>Audit-Trail:
State-Changed-From-To: open->analyzed 
State-Changed-By: bde 
State-Changed-When: Wed May 6 08:48:24 PDT 1998 
State-Changed-Why:  
PPPIOCSASYNCMAP conflicts with TIOCSDRAINWAIT, and pppd apparently issues 
the former after closing the PPP line discipline.  This clobbers drainwait. 
Responsible-Changed-From-To: freebsd-bugs->peter 
Responsible-Changed-By: johan 
Responsible-Changed-When: Mon Jun 3 19:10:49 PDT 2002 
Responsible-Changed-Why:  
Over to pppd maintainer. 

http://www.freebsd.org/cgi/query-pr.cgi?pr=6536 

From: Eugene Grosbein <eugen@grosbein.pp.ru>
To: bug-followup@freebsd.org
Cc: peter@freebsd.org
Subject: Re: bin/6536: pppd doesn't restore drainwait for tty
Date: Sat, 5 Apr 2003 22:59:03 +0800

 Hi!
 
 This PR was analyzed for enough time, wasn't it?
 Just wondering how it applies to 4.8-RELEASE :-)
 
 Eugene Grosbein
Responsible-Changed-From-To: peter->freebsd-bugs 
Responsible-Changed-By: peter 
Responsible-Changed-When: Tue Dec 13 03:38:23 UTC 2005 
Responsible-Changed-Why:  
Sombody can renumber PPPIOCSASYNCMAP in our tree to a non-conflicting 
number and check it in after compile testing. 

http://www.freebsd.org/cgi/query-pr.cgi?pr=6536 

From: Alex Kozlov <spam@rm-rf.kiev.ua>
To: bug-followup@FreeBSD.org, spam@rm-rf.kiev.ua
Cc:  
Subject: Re: bin/6536: pppd(8) doesn't restore drainwait for tty
Date: Thu, 13 May 2010 14:54:57 +0300

 Hi
 
 PPPIOCSASYNCMAP and pppd does not exist in CURRENT and RELENG_8.
 Therefore state of this pr can be changed to patched.
 
 
 --
 Adios
State-Changed-From-To: analyzed->closed 
State-Changed-By: jilles 
State-Changed-When: Sat May 15 14:43:10 UTC 2010 
State-Changed-Why:  
It seems very unlikely that this will be fixed, given that pppd(8) was 
removed in 8.0. Please use the supported ppp(8) or mpd from ports. 

http://www.freebsd.org/cgi/query-pr.cgi?pr=6536 
>Unformatted:
