Bug 645977 - DEMAND=yes means different things to different tools.
Summary: DEMAND=yes means different things to different tools.
Keywords:
Status: CLOSED WONTFIX
Alias: None
Product: Fedora
Classification: Fedora
Component: rp-pppoe
Version: 15
Hardware: Unspecified
OS: Unspecified
low
medium
Target Milestone: ---
Assignee: Than Ngo
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2010-10-23 12:03 UTC by David Woodhouse
Modified: 2012-08-07 19:43 UTC (History)
2 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2012-08-07 19:43:27 UTC
Type: ---
Embargoed:


Attachments (Terms of Use)

Description David Woodhouse 2010-10-23 12:03:08 UTC
I have this in /etc/sysconfig/network-scripts/ifcfg-ppp0

# Ick. Trick adsl-start into thinking we're in demand mode. But not pppoe-connect
if [ "$0" = "/usr/sbin/adsl-start" ]; then
	DEMAND=yes
else
	DEMAND=no
fi

I don't want demand mode -- I don't want pppd to wait until there's outbound traffic; I need it to connect *immediately* and remain connected whenever it can. 
This is especially relevant because most of the outbound traffic on this interface is IPv6 -- and that doesn't even cause a demand-dial, because the default IPv6 route is only set from ip-up when the connection is actually made. I can't just rely on the occasional outbound ntp packet to keep the connection up, which is why a lot of people don't notice this bug and just use 'DEMAND=yes' mode.

But I *do* need 'DEMAND=yes' in /usr/sbin/adsl-start, because there it does something completely different -- it means that the script doesn't wait, and delay my boot, until the ADSL line is synced and the connection is actually made... and it means that the script doesn't *kill* the running pppoe-connect dæmon script when it fails to connect quickly enough.

How can we fix this so that I don't have to evil things in my ifcfg-ppp0 script?

Comment 1 Bug Zapper 2011-05-31 10:46:09 UTC
This message is a reminder that Fedora 13 is nearing its end of life.
Approximately 30 (thirty) days from now Fedora will stop maintaining
and issuing updates for Fedora 13.  It is Fedora's policy to close all
bug reports from releases that are no longer maintained.  At that time
this bug will be closed as WONTFIX if it remains open with a Fedora 
'version' of '13'.

Package Maintainer: If you wish for this bug to remain open because you
plan to fix it in a currently maintained version, simply change the 'version' 
to a later Fedora version prior to Fedora 13's end of life.

Bug Reporter: Thank you for reporting this issue and we are sorry that 
we may not be able to fix it before Fedora 13 is end of life.  If you 
would still like to see this bug fixed and are able to reproduce it 
against a later version of Fedora please change the 'version' of this 
bug to the applicable version.  If you are unable to change the version, 
please add a comment here and someone will do it for you.

Although we aim to fix as many bugs as possible during every release's 
lifetime, sometimes those efforts are overtaken by events.  Often a 
more recent Fedora release includes newer upstream software that fixes 
bugs or makes them obsolete.

The process we are following is described here: 
http://fedoraproject.org/wiki/BugZappers/HouseKeeping

Comment 2 Fedora End Of Life 2012-08-07 19:43:29 UTC
This message is a notice that Fedora 15 is now at end of life. Fedora
has stopped maintaining and issuing updates for Fedora 15. It is
Fedora's policy to close all bug reports from releases that are no
longer maintained. At this time, all open bugs with a Fedora 'version'
of '15' have been closed as WONTFIX.

(Please note: Our normal process is to give advanced warning of this
occurring, but we forgot to do that. A thousand apologies.)

Package Maintainer: If you wish for this bug to remain open because you
plan to fix it in a currently maintained version, feel free to reopen
this bug and simply change the 'version' to a later Fedora version.

Bug Reporter: Thank you for reporting this issue and we are sorry that
we were unable to fix it before Fedora 15 reached end of life. If you
would still like to see this bug fixed and are able to reproduce it
against a later version of Fedora, you are encouraged to click on
"Clone This Bug" (top right of this page) and open it against that
version of Fedora.

Although we aim to fix as many bugs as possible during every release's
lifetime, sometimes those efforts are overtaken by events. Often a
more recent Fedora release includes newer upstream software that fixes
bugs or makes them obsolete.

The process we are following is described here:
http://fedoraproject.org/wiki/BugZappers/HouseKeeping


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