Bug 14837 - PPP interface "failing" on boot (timeout?)
Summary: PPP interface "failing" on boot (timeout?)
Keywords:
Status: CLOSED RAWHIDE
Alias: None
Product: Red Hat Raw Hide
Classification: Retired
Component: initscripts
Version: 1.0
Hardware: i386
OS: Linux
medium
medium
Target Milestone: ---
Assignee: Bill Nottingham
QA Contact:
URL:
Whiteboard:
: 16920 (view as bug list)
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2000-07-29 09:03 UTC by Reuben Farrelly
Modified: 2014-03-17 02:15 UTC (History)
1 user (show)

Fixed In Version:
Clone Of:
Environment:
Last Closed: 2000-09-02 18:05:20 UTC
Embargoed:


Attachments (Terms of Use)

Description Reuben Farrelly 2000-07-29 09:03:10 UTC
I have a ppp interface set up to come up on boot, and this works pretty 
much as expected (the link does actually come up on boot).
Unfortunately the initscripts seem to have some sort of timeout somewhere 
which does not give my modem enough time to negotiate and establish a 
connection.  This means that the startup script will timeout and consider 
the interface to have failed, and it then skips on past starting up other 
services and tasks as listed.
The interface comes up and is fully ready about 5 seconds after the 
initscripts have decided that there was a problem, and all works fairly 
normally after that.

Could the timeout before the initscripts decide that an interface has 
failed to come up be either lengthened or user specified, perhaps in the 
ifcfg-* files?

Comment 1 Henri Schlereth 2000-08-02 04:36:03 UTC
Exists in RH6.2. Dials in background and connects.

Comment 2 Reuben Farrelly 2000-09-02 18:05:16 UTC
Yes you're correct, but this behaviour is not ideal when other daemons in the 
startup (for example ntpd) are started _before_ the PPP link is fully up and 
routing.   This is because any other service which relies on DNS resolution 
when it starts does not get a satisfactory resolve and thus sometimes fails 
(unless of course there is access to DNS via another link).

In this case pppd being backgrounded after 30s is of no use whatsoever.  The 
ability to control this behaviour would be nice.





Comment 3 Bill Nottingham 2001-01-30 00:43:15 UTC
This will be fixed as of initscripts-5.60-1; there
is a BOOTTIMEOUT option.

Comment 4 Bill Nottingham 2001-01-30 00:44:10 UTC
*** Bug 16920 has been marked as a duplicate of this bug. ***


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