Bug 84807 – adsl-start exits at line 218 when run by init script

Bug 84807 - adsl-start exits at line 218 when run by init script

Summary:	adsl-start exits at line 218 when run by init script

Status:	CLOSED CURRENTRELEASE

Aliases:	None

Product:	Red Hat Linux
Classification:	Retired
Component:	rp-pppoe (Show other bugs)
Sub Component:
Version:	8.0
Hardware:	i386 Linux

Priority	medium Severity medium
Target Milestone:	---
Target Release:	---
Assigned To:	Ngo Than
QA Contact:	Jay Turner
Docs Contact:

URL:
Whiteboard:
Keywords:

Depends On:
Blocks:
	Show dependency tree / graph

Reported:	2003-02-21 11:00 EST by Summer Maynard
Modified:	2015-01-07 19:03 EST (History)
CC List:	2 users (show)

See Also:
Fixed In Version:
Doc Type:	Bug Fix
Doc Text:
Story Points:	---
Clone Of:
Environment:
Last Closed:	2004-10-08 19:17:10 EDT
Type:	---
Regression:	---
Mount Type:	---
Documentation:	---
CRM:
Verified Versions:
Category:	---
oVirt Team:	---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---

Attachments	(Terms of Use)
Add an attachment (proposed patch, testcase, etc.)

Groups: None (edit)

Description Summer Maynard 2003-02-21 11:00:17 EST

From Bugzilla Helper:
User-Agent: Mozilla/5.0 Galeon/1.2.6 (X11; Linux i686; U;) Gecko/20020830

Description of problem:
When adsl-start is run manually, it starts up successfully.

When it is run by 'service network start' (manually or during boot), it returns
the following error and a status of 'Failed'

Bringing up interface ppp0:  /sbin/adsl-start: line 218:  4165 Terminated      
       $CONNECT "$@" >/dev/null 2>&1
 [60G[ [0;31mFAILED [0;39m]


Version-Release number of selected component (if applicable):


How reproducible:
Always

Steps to Reproduce:
1.boot the system or run 'service network start/restart'
2.
3.
    

Actual Results:  Error noted in description comes up and the startup of ppp0 fails.

Expected Results:  The interface should come up properly.

Additional info:

Comment 1 Ngo Than 2004-10-08 19:17:10 EDT

it's not reproduceable in FC2 und FC3test3. please reopen it again if 
it still appears. Thanks

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