Red Hat Bugzilla – Bug 123222
xinetd can't start user defined rpc service
Last modified: 2014-08-31 19:26:09 EDT
Description of problem:
RHAS 3 FCS is installed on intel platform.
Linux test1 2.4.21-4.ELsmp #1 SMP Fri Oct 3 17:52:56 EDT 2003 i686
i686 i386 GNU/Linux
Configured a rpc service in /etc/xinetd.d and don't see this rpc
service is started by xinetd. But, when "rpcinfo -p", this rpc program
# default: on
disable = no
type = RPC
socket_type = dgram
wait = yes
protocol = udp
rpc_version = 1
rpc_number = 100145
user = root
server = /etc/init.d/in.toto_server
# rpcinfo -p
100145 1 udp 32777 toto_server
However, the rpc service can be started manually.
Version-Release number of selected component (if applicable):
Steps to Reproduce:
1. add toto_server config file in /etc/xinetd.d
2. cp in.toto_server to /etc/init.d/
3. add a line "toto_server 100145" to /etc/rpc.
4. service xinetd restart
May 13 15:25:28 test1 xinetd: xinetd shutdown succeeded
May 13 15:25:28 test1 xinetd: xinetd startup succeeded
May 13 15:25:30 test1 xinetd: xinetd Version 2.3.12 started with
libwrap loadavg options compiled in.
May 13 15:25:30 test1 xinetd: Started working: 5 available services
ps -ef | grep toto
root 3961 3075 0 15:28 ttyS1 00:00:00 grep toto
I don't see toto_server is running.
toto_server should be running as it is started manually.
Created attachment 100224 [details]
Xinetd never starts any servers until a client request for that
service is received, so no toto_server process will exist until a
client attempts to access it.
OK. Now I can see toto_server is started up by xinetd when a client
(toto_client) requests it. But, the first run always get rpc timed
out as the toto_server is just started up and miss this request.
However the subsequent runs are fine. How do I handle this situation?