Bug 52225

Summary:	ifup-ippp doenst check return code of isdnctrl
Product:	[Retired] Red Hat Raw Hide	Reporter:	Ronny Buchmann <ronny-rhbugzilla>
Component:	initscripts	Assignee:	Bill Nottingham <notting>
Status:	CLOSED RAWHIDE	QA Contact:	Brock Organ <borgan>
Severity:	medium	Docs Contact:
Priority:	medium
Version:	1.0	CC:	rvokal, than
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:	2001-08-22 05:55:57 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 Ronny Buchmann 2001-08-21 19:51:36 UTC

Description of Problem:
/etc/init.d/network
shows succesfull started ippp device, but it isnt started at all

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

How Reproducible:
always

Steps to Reproduce:
i.e. use isdn4k-utils-3.1-44
or produce any other hardware problem so that isdnctrl doesnt work as expected


Expected Results:
/etc/init.d/network should show a failure not success

i think the problem is inside ifup-ippp (and ifup maybe)

possible solution:
do a final "isdnctrl list $DEVICE" to see if interface is up (maybe enough)
or do 

isdnctrl $* >/dev/null 2>&1 && exit 1

in log_isdnctrl()


btw, ibod should be started with daemon(), or not?

Comment 1 Bill Nottingham 2001-08-21 20:51:26 UTC

Than, is this fixed in 6.24-1?

Comment 2 Ronny Buchmann 2001-08-22 05:55:02 UTC

isdnctrl $* >/dev/null 2>&1 && exit 1

is wrong, right is of course:

isdnctrl $* >/dev/null 2>&1 || exit 1

Comment 3 Ngo Than 2001-08-22 12:40:25 UTC

It's fixed in 6.25-1. You will find it in next rawhide release.