Red Hat Bugzilla – Bug 8153
pppd does not reap child process deaths correctly in demand dial mode
Last modified: 2008-05-01 11:37:53 EDT
I have ppp-2.3.10-3 installed under Redhat 6.1 and have
ppp configured to work in demand-dial mode. This is
working as advertised. Recently, I added some code to
/etc/ppp/ip-up.local, but pppd does not always execute
Here's what I've tracked down so far:
1) The very first time that pppd brings the link up,
it executes if-up (which in turn executed if-up.local).
It is able to successfully reap the death of this child
process. So far, so good.
2) When pppd drops the link due to inactivity, it runs
if-down. However, it does not properly reap the
death of this child process. As such, it does not
have a chance to call ipcp_script_done to reset some
variables it uses. In particular, ipcp_script_pid remains
set to the pid of the ip-down script.
3) The next time pppd brings the link up, it checks to see if it
should run the ip-up script. It does this by seeing if
the ipcp_script_pid variable is 0. If so, then it runs
the script. But since the variable was never reset
properly, pppd will never run the ip-up or ip-down scripts
after the very first time.
If you need additional information, please email me and I'll
I'm experiencing this exact same problem (RH 6.1 & ppp-2.3.10-1).
Is there a workaround or fix?
I've taken a stab at fixing this. Please try the test release of ppp from
http://people/nalin/ppp-2.3.11-3.i386.rpm and let me know if it has any effect.
Sorry, the full URL is "http://people.redhat.com/nalin/ppp-2.3.11-3.i386.rpm".
The new ppp-2.3.11-3 appears to work for me - Thanks!
Excellent. This version is now in our beta and slated to ship with 6.2.
Aargh. Can't close this until email@example.com verifies that the new
version fixes it for him as well....
Yes, I've been using ppp-2.3.11-3 since 2/7/00 and it
appears to fix the problem. Go ahead and close out this bug.