Bug 14859

Summary:	ppp0 manual redialing problems
Product:	[Retired] Red Hat Linux	Reporter:	Bryan Reece <reece-bugzilla>
Component:	initscripts	Assignee:	Bill Nottingham <notting>
Status:	CLOSED RAWHIDE	QA Contact:
Severity:	medium	Docs Contact:
Priority:	medium
Version:	6.2	CC:	rvokal
Target Milestone:	---
Target Release:	---
Hardware:	i386
OS:	Linux
Whiteboard:
Fixed In Version:		Doc Type:	Bug Fix
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2000-07-30 20:15:05 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:

Description Bryan Reece 2000-07-30 20:15:02 UTC

If a user issues `ifup ppp0' while the link is already up, the script saya
 ppp0 already up, initiating redial
and starts the advertised redial.  Subsequent `ifdown ppp0' commands fail
due to the absence of /var/run/pppwatch-ppp0.pid, and manual intervention
is required.

Redialing doesn't drop the line for long, so the first redial attempt gets
the `If you'd like to make a call, please hang up and try again' that the
local switch sends if you stay off-hook after the distant party hangs up.

Attempting to force a second redial manually (another `ifup ppp0' shortly
after the failed call attempt) seems to result in dueling chats: 
one chat sends a dial command, then the second sends a dial command that
aborts the first dial, causing someone to see `NO CARRIER' and retry ad
nauseam.

Comment 1 Bill Nottingham 2000-08-07 05:24:49 UTC

This has since been fixed; subsequent ppp-watch calls do
not kill the first ppp-watch's lock file.