Bugzilla will be upgraded to version 5.0 on a still to be determined date in the near future. The original upgrade date has been delayed.
Bug 185781 - ifup clashes with $WINDOW environment variable
ifup clashes with $WINDOW environment variable
Status: CLOSED DUPLICATE of bug 174336
Product: Fedora
Classification: Fedora
Component: initscripts (Show other bugs)
All Linux
medium Severity medium
: ---
: ---
Assigned To: Bill Nottingham
Brock Organ
Depends On:
  Show dependency treegraph
Reported: 2006-03-17 17:47 EST by cody koeninger
Modified: 2014-03-16 22:58 EDT (History)
2 users (show)

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Last Closed: 2006-03-18 09:54:37 EST
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 cody koeninger 2006-03-17 17:47:50 EST
Description of problem:

This one's hilarious . . . the ifup scripts (eg.
/etc/sysconfig/network-scripts/ifup-eth ) contain lines like:

ip route replace default ${SRC} ${WINDOW:+window $WINDOW} dev ${REALDEVICE}

And guess what?  GNU screen sets the environment variable $WINDOW to
the number of the current window you're in, so if you're in a non-zero
screen window, the tcp window gets set to a small value, killing network

Version-Release number of selected component (if applicable):
at least fc 2 and 4

How reproducible:
run screen, add a window (^t c), switch to that window (^t 1).

# netstat -rn

Kernel IP routing table
Destination     Gateway         Genmask         Flags   MSS Window  irtt
Iface         UG        0 0          0

# ifup bond0:9

# netstat -rn
Kernel IP routing table
Destination     Gateway         Genmask         Flags   MSS Window  irtt
Iface         UG        0 1          0

lo and behold, the tcp window is jacked.  Here's why:
# echo $WINDOW
1  (or whatever the number of your GNU screen window is)

Expected results:

the network scripts should rely on something as likely to cause name clashes as

Additional info:
Comment 1 Miloslav Trmač 2006-03-18 09:54:37 EST
Thank you for the bug report. This particular bug has already been reported
into our bug tracking system, but please feel free to report any further
bugs you find.

*** This bug has been marked as a duplicate of 174336 ***

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