Bug 23756 - portmap sysvinit script doesn't handle missing /etc/sysconfig/network
Summary: portmap sysvinit script doesn't handle missing /etc/sysconfig/network
Keywords:
Status: CLOSED RAWHIDE
Alias: None
Product: Red Hat Linux
Classification: Retired
Component: portmap
Version: 6.2
Hardware: All
OS: Linux
low
low
Target Milestone: ---
Assignee: Trond Eivind Glomsrxd
QA Contact: Aaron Brown
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2001-01-11 00:22 UTC by wstearns
Modified: 2005-10-31 22:00 UTC (History)
0 users

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2001-01-11 00:22:47 UTC
Embargoed:


Attachments (Terms of Use)

Description wstearns 2001-01-11 00:22:44 UTC
If /etc/sysconfig/network is missing, the sysvinit script whines about "no
such file or directory" when network is sourced.
	Also, the test for "if [ ${NETWORKING} = "no" ] fails out because
NETWORKING has no value; the error is: "/etc/rc.d/init.d/portmap: [: =:
unary operator expected.

	Possible solution: replace:

. /etc/sysconfig/network

	with

if [ -f /etc/sysconfig/network ]
then
	. /etc/sysconfig/network
else
	exit 1
fi

	Also, replace:

if [ ${NETWORKING} = "no" ]

	with

if [ "${NETWORKING}" = "no" ]

	Cheers.

Comment 1 Trond Eivind Glomsrxd 2001-01-20 22:45:49 UTC
Fixed in portmap-4.0-31



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