Bug 113225

Summary: unable to stop xinetd
Product: [openSUSE] SUSE LINUX 10.0 Reporter: Martin Mrazik <mmrazik>
Component: BasesystemAssignee: Dr. Werner Fink <werner>
Status: RESOLVED DUPLICATE QA Contact: Klaus Kämpf <kkaempf>
Severity: Blocker    
Priority: P5 - None CC: kukuk
Version: Beta 3   
Target Milestone: ---   
Hardware: Other   
OS: All   
Whiteboard:
Found By: Other Services Priority:
Business Priority: Blocker: ---
Marketing QA Status: --- IT Deployment: ---
Bug Depends on:    
Bug Blocks: 97395    
Attachments: y2logs after trying to disable xinetd

Description Martin Mrazik 2005-08-26 07:53:26 UTC 
Using yast2 I configured the "finger" service and enabled xinetd (Command:
/sbin/yast2 inetd). Now I'm unable stop the service. "ps ax | grep xinetd" shows
that xinetd is still running and also the command "finger @myHost" still works.

y2logs attached in the next comment.

PS: I'm unable to stop xinetd also from commandline:

king:/ # /etc/init.d/xinetd stop
Shutting down xinetd:                                                 done
king:/ # finger @king
[king/10.20.1.103]

Welcome to Linux version 2.6.13-rc6-git13-4-default at king.suse.cz !

  9:53am  up   1:13,  9 users,  load average: 1.16, 1.08, 1.09

Login      Name                  Tty      Idle  Login Time   Where
mmrazik    Martin Mrazik        *:0          -     Fri 08:40 console
...
...
king:/ # ps ax | grep xinetd
10432 ?        Ss     0:00 /usr/sbin/xinetd
12743 pts/7    R+     0:00 grep xinetd
Comment 1 Martin Mrazik 2005-08-26 07:54:04 UTC 
Created attachment 47711 [details]
y2logs after trying to disable xinetd
Comment 2 Thorsten Kukuk 2005-08-26 09:07:22 UTC 
killproc seems to be broken, killproc does not work anymore if there
is no -p option with a valid pid file.
Comment 3 Michael Gross 2005-08-26 09:51:09 UTC 
That's a bit strange. I compiled the official b3 src-package (Version sysvinit
2.85-49) on b3 and the included killproc worked perfectly in that manner. So
this bug may either be fixed already or the problem occured at build-time.
Comment 4 Dr. Werner Fink 2005-08-26 09:58:46 UTC 
Known and fixed

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