On 17 Dec 1998, Harry Zink writes:
> Here's what I'm getting in the log, when my system hangs up way
> earlier than the 10 minutes idle time I have it configured for:
> Dec 17 23:37:22 gate diald[404]: Closing down idle link.
> Dec 17 23:37:23 gate pppd[4984]: Terminating on signal 2.
> Dec 17 23:37:29 gate pppd[4984]: Connection terminated.
> Dec 17 23:37:30 gate pppd[4984]: Exit.
> Dec 17 23:37:31 gate diald[404]: Delaying 30 seconds before clear to dial.
>
> What the hell is signal 2?
Can we lose the profanity? Signal 2 is SIGINT (you can do a kill -l
to get a signal list showing their numbers and names).
However, I suspect the real clue is in the first line of this log
excerpt.
It is not the pppd idle timer that is expiring. It is diald deciding
to close down a link it believes to be idle. That's what the first
line says. That log entry came from diald. So, diald is sending a
SIGINT to pppd, trying to make pppd terminate the link gracefully,
which it dutifully does. That's what it is supposed to do, according
to the pppd man page, upon receipt of a SIGINT.
So the real culprit is diald, not pppd. It has its own timers, and
complex filtering rules. That diald idle timer is not set from the
idle parameter in Linuxconf's PPP setup menu.
Is diald a part of your standard Linux distribution? If you added it
yourself, how did you configure it? It might be nice to have a diald
module for Linuxconf, but I've not heard of one :-)
I suggest that you reread the diald documentation carefully, and check
your diald filtering rules. I'm fairly sure that will find the cause
of the unwanted link disconnect.
Jonathan
--
Jonathan Marsden | Internet: [EMAIL PROTECTED] | Making electronic
1849 N. Wabash Ave.| Phone: +1 (909) 794 1151 | communications work
Redlands, CA 92374 | FAX: +1 (909) 794 3016 | reliably for Christian
USA | http://www.xc.org/jonathan | missions worldwide
---
You are currently subscribed to linuxconf as: [[email protected]]
To unsubscribe, forward this message to [EMAIL PROTECTED]
