Bugzilla will be upgraded to version 5.0. The upgrade date is tentatively scheduled for 2 December 2018, pending final testing and feedback.
Bug 7865 - ppp-watch too intrusive.
ppp-watch too intrusive.
Product: Red Hat Linux
Classification: Retired
Component: initscripts (Show other bugs)
All Linux
medium Severity medium
: ---
: ---
Assigned To: Nalin Dahyabhai
Depends On:
  Show dependency treegraph
Reported: 1999-12-17 05:02 EST by Neil Darlow
Modified: 2008-05-01 11:37 EDT (History)
0 users

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Last Closed: 2000-03-20 11:22:17 EST
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Attachments (Terms of Use)

  None (edit)
Description Neil Darlow 1999-12-17 05:02:10 EST
The use of ppp-watch in ifup-ppp overrides expected use of "ifup ppp?".

Most annoyingly, it results in a persistent connection which most casual
ppp users don't want. They either want manual control or on-demand.

Additionally, ppp-watch is exec'd which results in ifup not returning
and being listed as <defunct> in the process table until it is killed by
a subsequent "ifdown ppp?".

Would it not be better to only invoke ppp-watch if PERSIST=yes is present
in ifcfg-ppp? and likewise make the same check in ifdown-ppp before
killing ppp-watch?

I also believe that ppp-watch should be started normally and followed by
an exit to permit ifup to return as it does when used for other interfaces.
Comment 1 Bill Nottingham 2000-03-20 11:22:59 EST
ppp-watch is intended to support a non-persistent connection
that reconnects on errors; it isn't supposed to be regular
'persistent' connections. The version that shipped with 6.1
did have some bugs in it that could cause odd behavior; you
should probably upgrade to the errata.

Note You need to log in before you can comment on or make changes to this bug.