Bug 52225 - ifup-ippp doenst check return code of isdnctrl
ifup-ippp doenst check return code of isdnctrl
Product: Red Hat Raw Hide
Classification: Retired
Component: initscripts (Show other bugs)
i386 Linux
medium Severity medium
: ---
: ---
Assigned To: Bill Nottingham
Brock Organ
Depends On:
  Show dependency treegraph
Reported: 2001-08-21 15:51 EDT by Ronny Buchmann
Modified: 2014-03-16 22:22 EDT (History)
2 users (show)

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Last Closed: 2001-08-22 01:55:57 EDT
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 Ronny Buchmann 2001-08-21 15:51:36 EDT
Description of Problem:
shows succesfull started ippp device, but it isnt started at all

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

How Reproducible:

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 16:51:26 EDT
Than, is this fixed in 6.24-1?
Comment 2 Ronny Buchmann 2001-08-22 01:55:02 EDT
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 08:40:25 EDT
It's fixed in 6.25-1. You will find it in next rawhide release.

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