11050 – /etc/init.d/xinetd check starts wrong command

Bug 11050 - /etc/init.d/xinetd check starts wrong command

Summary: /etc/init.d/xinetd check starts wrong command

Status:	RESOLVED FIXED

Alias:	None

Product:	Gentoo Linux
Classification:	Unclassified
Component:	[OLD] Server (show other bugs)
Hardware:	x86 Linux

Importance:	Highest normal (vote)
Assignee:	Gentoo Linux bug wranglers

URL:
Whiteboard:
Keywords:

Depends on:
Blocks:

Reported:	2002-11-21 05:23 UTC by Mark
Modified:	2003-02-04 19:42 UTC (History)
CC List:	1 user (show)

See Also:
Package list:
Runtime testing required:	---

Attachments
Add an attachment (proposed patch, testcase, etc.)

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

Description Mark 2002-11-21 05:23:19 UTC

in /etc/init.d/xinetd is the following code:

check(){
        ebegin "Performing Consistency Check"
        /bin/kill -s IOT xinetd &>/dev/null
        eend $?
}

However, "kill" should be replaced by "killall".

Comment 1 Maurizio Disimino 2002-11-22 02:41:38 UTC

why? doesn't /etc/init.d/xinetd check work for you?

-- Maurizio

Comment 2 SpanKY gentoo-dev

2002-11-23 15:29:53 UTC

it needs to be `killall` because `kill` does not take in names of processes as input ... 
 
also, kill does not recognize the signal 'IOT' while `killall` does ... 
and last, all the other functions use `killall` ... 
 
fixed in cvs ... 
http://cvs.gentoo.org/cgi-bin/viewcvs.cgi/gentoo-x86/sys-apps/xinetd/files/2.3.9/xinetd.rc6.diff?r1=1.1&r2=1.2