Note: This is a beta release of Red Hat Bugzilla 5.0. The data contained within is a snapshot of the live data so any changes you make will not be reflected in the production Bugzilla. Also email is disabled so feel free to test any aspect of the site that you want. File any problems you find or give feedback here.
Bug 163203 - /etc/init.d/dhcpd script has typo
Summary: /etc/init.d/dhcpd script has typo
Keywords:
Status: CLOSED RAWHIDE
Alias: None
Product: Fedora
Classification: Fedora
Component: dhcp
Version: 4
Hardware: i686
OS: Linux
medium
medium
Target Milestone: ---
Assignee: Jason Vas Dias
QA Contact:
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2005-07-14 00:40 UTC by jtidman
Modified: 2007-11-30 22:11 UTC (History)
0 users

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2005-07-14 20:33:34 UTC


Attachments (Terms of Use)

Description jtidman 2005-07-14 00:40:50 UTC
From Bugzilla Helper:
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.7.8) Gecko/20050511 Firefox/1.0.4

Description of problem:

The call to dhcpd in configtest() needs method of quieting STDERR output.

configtest()
{
        CFA=''
        if [[ "$DHCPDARGS" = *-cf* ]]; then
	    CFA=`echo $DHCPDARGS | sed 's/^.*-cf[\ \	]*/-cf/;s/[\ \	].*$//;s/-cf/-cf /'`;
        fi;
	/usr/sbin/dhcpd -t $CFA	2>/dev/null
# or	/usr/sbin/dhcpd -t $CFA	-q
	return $?
}



Version-Release number of selected component (if applicable):
dhcp-3.0.2-14.FC4

How reproducible:
Always

Steps to Reproduce:
1. yum update dhcp
2. service dhcpd restart
3.
  

Actual Results:  
only seen when "service dhcp restart" command is used "stop" and "start" do not show program copyright.

restart command shows program copyright:
Internet Systems Consortium DHCP Server V3.0.2
Copyright 2004 Internet Systems Consortium.
All rights reserved.


Expected Results:  Copyright should have been hidden.

Additional info:

Comment 1 Jason Vas Dias 2005-07-14 20:33:34 UTC
This is now fixed in Rawhide (dhcp-3.0.3rc1) and will be fixed in the next
FC-4 and FC-3 releases.


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