From: bfc <chappaquasuite@yahoo.com>
To: linux-ppp@vger.kernel.org
Subject: hanging tcsetattr call
Date: Wed, 05 Mar 2008 22:19:00 +0000 [thread overview]
Message-ID: <15861511.post@talk.nabble.com> (raw)
It seems when my chat script times out, i'll get an "alarm" notification from
chat, then chat exits, and
pppd hangs for a while on a tcsetattr() call -- it's trying to restore the
terminal characteristics of
our serial port.
Eventually it syslogs:
Mar 5 17:09:25 box pppd[21132]: tcsetattr: Interrupted system call (line
1001)
Evidentally the pppd can no longer use the device, perhaps it's been reset
from having an session attempted
but not succeeding? Anyone else ever see this problem?
Should there be any signal flow that causes this to go correctly, e.g. a
SIGCHLD going to the pppd?
Or does pppd just see a non-zero exit value from chat, and should gracefully
shut itself down?
Thanks!
--
View this message in context: http://www.nabble.com/hanging-tcsetattr-call-tp15861511p15861511.html
Sent from the linux-ppp mailing list archive at Nabble.com.
next reply other threads:[~2008-03-05 22:19 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-03-05 22:19 bfc [this message]
2008-03-05 22:31 ` hanging tcsetattr call Bill Unruh
2008-03-06 1:43 ` bfc
2008-03-06 1:58 ` Bill Unruh
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=15861511.post@talk.nabble.com \
--to=chappaquasuite@yahoo.com \
--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