Bug 16157 - IPV4_DEFRAG message will not display
IPV4_DEFRAG message will not display
Status: CLOSED CURRENTRELEASE
Product: Red Hat Linux
Classification: Retired
Component: initscripts (Show other bugs)
6.1
i386 Linux
medium Severity medium
: ---
: ---
Assigned To: Bill Nottingham
:
Depends On:
Blocks:
  Show dependency treegraph
 
Reported: 2000-08-14 07:45 EDT by Mike Bakke
Modified: 2014-03-16 22:15 EDT (History)
1 user (show)

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Environment:
Last Closed: 2000-08-14 07:45:36 EDT
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---


Attachments (Terms of Use)

  None (edit)
Description Mike Bakke 2000-08-14 07:45:35 EDT
The code in /etc/rc.d/init.d/network which decides whether or not to set 
IPV4_DEFRAG on sets ** mesage="Enabling IPv4 automatic defragmentation" **
instead of ** message="Disabling IPv4 automatic defragmentation" **

ie the variable "mesage" is used instead of "message". Therefore when the 
script displays $message - the prior contents are displayed. Relevant code 
fragment included here :

ipv4_defrag_set ()
{
	# Sets whether or not to always defrag packets.
	# Good for masquerading. Not so good otherwise.
	if [ -d /proc/sys/net/ipv4 ]; then
	    if [ ! -f /proc/sys/net/ipv4/ip_always_defrag ]; then
	       echo "/proc/sys/net/ipv4/ip_always_defrag is missing --" \
	            "cannot control IP defragmentation" >&2
	    else
	       if [ "$DEFRAG_IPV4" = "yes" -o "$DEFRAG_IPV4" = "true" ]; 
then
	          value=1
		  mesage="Enabling IPv4 automatic defragmentation"
	       else
	          value=0
		  message="Disabling IPv4 automatic defragmentation"
	       fi
	       
	       if [ $value != `cat /proc/sys/net/ipv4/ip_always_defrag` ]; 
then
	          action "$message" /bin/true
		  echo "$value" > /proc/sys/net/ipv4/ip_always_defrag
	       fi
	    fi
	fi
}
Comment 1 Bill Nottingham 2000-08-14 10:52:02 EDT
This has been fixed, at least by 6.2, if not in the 6.1 initscripts errrata.

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