Bug 50760
Summary: | ppp-watch is not necessary for demand-dial PPP links | ||||||
---|---|---|---|---|---|---|---|
Product: | [Retired] Red Hat Linux | Reporter: | Need Real Name <kevin> | ||||
Component: | initscripts | Assignee: | Bill Nottingham <notting> | ||||
Status: | CLOSED RAWHIDE | QA Contact: | Brock Organ <borgan> | ||||
Severity: | medium | Docs Contact: | |||||
Priority: | medium | ||||||
Version: | 7.1 | CC: | ccrayne, goeran, rvokal | ||||
Target Milestone: | --- | ||||||
Target Release: | --- | ||||||
Hardware: | All | ||||||
OS: | Linux | ||||||
Whiteboard: | |||||||
Fixed In Version: | 7.20-1 | Doc Type: | Bug Fix | ||||
Doc Text: | Story Points: | --- | |||||
Clone Of: | Environment: | ||||||
Last Closed: | 2003-05-19 21:32:23 UTC | Type: | --- | ||||
Regression: | --- | Mount Type: | --- | ||||
Documentation: | --- | CRM: | |||||
Verified Versions: | Category: | --- | |||||
oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |||||
Cloudforms Team: | --- | Target Upstream Version: | |||||
Embargoed: | |||||||
Attachments: |
|
Description
Need Real Name
2001-08-02 21:28:07 UTC
Created attachment 30394 [details]
ppp-watch Patch against ppp-watch.c of initscripts-5.83-1
I have a similar problem with my 56K modem. I think the problem happens with demand and non-on-demand links because ppp-watch fork's twice with de code of ppp-watch.c in initscripts-5.83-1. After I execute: $ date;ifup ppp0;date I check my logs and I see a new pppd process starts when ifup finish. So I wrote the previous patch. Running RedHat 7.2 with all the latest rpm's upto 07/12/2001. This is still a problem ... this also seems to be the same bug as 6291 and 51874. Have taken a look at rawhide rpms and see no change. Okay, tried the ifup-ppp patch and basic tests find it to work. ifup ppp0 and ifdown ppp0 seem to do what I think is correct. Don't know if ppp-watch patch would help, but I think the RedHat devs people will make a good choice. Hope to see this soon in an updated rpm. If I find any other problems I will update the bug. In 7.20-1 this seems to be fixed. So this report can be closed now, right? Sure. |