From: Arkadiusz Miskiewicz <arekm@pld-linux.org>
To: linux-ppp@vger.kernel.org
Subject: Re: some change in ppp 2.4.3: tcflush failed: Bad file descriptor
Date: Thu, 25 Nov 2004 16:09:03 +0000 [thread overview]
Message-ID: <200411251709.03660.arekm@pld-linux.org> (raw)
In-Reply-To: <200411231157.43347.arekm@pld-linux.org>
On Thursday 25 of November 2004 16:44, Arkadiusz Miskiewicz wrote:
> Well, after such disconnect new pppd runs pppoa -I eth1 multiple times
> without killing old one and this causes huge load (it's hard to do anything
> on the system then). Old, not killed pppoa processes reports multiple
> Nov 25 16:18:15 arm pppoa[6387]: Packet not from driver (mac:
> 0:60:4c:41:53:74) Nov 25 16:18:15 arm pppoa[6387]: Packet not from driver
> (mac: 0:60:4c:41:53:74) Nov 25 16:18:15 arm pppoa[6328]: Packet not from
> driver (mac: 0:60:4c:41:53:74) Nov 25 16:18:15 arm pppoa[6328]: Packet not
> from driver (mac: 0:60:4c:41:53:74)
>
> Shouldn't pppd kill old pty "command" before running new one?
It looks like this:
[root@arm misiek]# pstree -lpu | grep ppp
|-pppd(17285)-+-sh(17286)---pppoa(17287)
| |-sh(17479)---pppoa(17484)
| `-sh(17539)---pppoa(17540)
|-sh(8386)---pppoa(8390)
new pppoa is created at each retry
--
Arkadiusz Mi¶kiewicz PLD/Linux Team
http://www.t17.ds.pwr.wroc.pl/~misiek/ http://ftp.pld-linux.org/
next prev parent reply other threads:[~2004-11-25 16:09 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-11-23 10:57 some change in ppp 2.4.3: tcflush failed: Bad file descriptor Arkadiusz Miskiewicz
2004-11-23 16:06 ` James Carlson
2004-11-25 15:44 ` Arkadiusz Miskiewicz
2004-11-25 16:09 ` Arkadiusz Miskiewicz [this message]
2004-11-25 21:27 ` Paul Mackerras
2004-11-25 22:55 ` Arkadiusz Miskiewicz
2004-11-26 0:51 ` Paul Mackerras
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=200411251709.03660.arekm@pld-linux.org \
--to=arekm@pld-linux.org \
--cc=linux-ppp@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox