Bug 3361 - dip does not behave as ifup-sl expects
dip does not behave as ifup-sl expects
Product: Red Hat Linux
Classification: Retired
Component: initscripts (Show other bugs)
i386 Linux
medium Severity medium
: ---
: ---
Assigned To: Bill Nottingham
Depends On:
  Show dependency treegraph
Reported: 1999-06-09 10:54 EDT by lars
Modified: 2014-03-16 22:09 EDT (History)
1 user (show)

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Last Closed: 1999-08-24 11:37:17 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 lars 1999-06-09 10:54:24 EDT
ifup-sl does not expect dip to exit unless the connection

  doexec /usr/bin/dip dip-$DEVICE $DIPSCRIPT
  if [ "$PERSIST" != "yes" -o ! -f /var/run/sl-$DEVICE.dev
]; then
    exit 0

Unfortunately, the version of dip distributed with RH6.0
(dip-3.3.7o-14) backgrounds immediately after establishing
a connection.

In the case of a successful connection, that means that dip
appears to exit, and ifup-sl assumes the connection has
closed.  If $PERSIST is "yes", ifup-sl will try to
reactivate the connection.  dip starts up, finds the serial
port in use, and exists, so ifup-sl tries to reactivate the

And so forth.

Workaround: turn off "PERSIST" and think of another way to
handle dropped connections.

Solution: fix dip, or fix ifup-sl.  Perhaps it could
check for the lock file dip puts in /var/lock, and use
this to check whether or not dip is still running.
Comment 1 Jay Turner 1999-06-29 10:46:59 EDT
This issue has been forwarded to a developer for further action.
Comment 2 Bill Nottingham 1999-08-24 11:37:59 EDT
should be fixed in initscripts-4.33, in next Raw Hide release.

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