Bug 3361

Summary: dip does not behave as ifup-sl expects
Product: [Retired] Red Hat Linux Reporter: lars
Component: initscriptsAssignee: Bill Nottingham <notting>
Severity: medium Docs Contact:
Priority: medium    
Version: 6.0CC: rvokal
Target Milestone: ---   
Target Release: ---   
Hardware: i386   
OS: Linux   
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 1999-08-24 15:37:17 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:

Description lars 1999-06-09 14:54:24 UTC
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 14:46:59 UTC
This issue has been forwarded to a developer for further action.

Comment 2 Bill Nottingham 1999-08-24 15:37:59 UTC
should be fixed in initscripts-4.33, in next Raw Hide release.