Thanks to everyone that posted back so quick and esp. to David and Ben for
finding the solution. 'type = unlisted' fixed the issue!
Thanks,
Jim
---------------------------- Original Message ----------------------------
Subject: Re: XInetd & /etc/services Issue
From: "Matthew Howard" <mch@xxxxxxxxxxxxxx>
Date: Wed, October 20, 2004 2:21 am
To: "Discussion of the Fedora Legacy Project"
<fedora-legacy-list@xxxxxxxxxx> Cc: tux@xxxxxxxxxxxx
jim@xxxxxxxxxxxx
--------------------------------------------------------------------------
Ben Stringer wrote:
>On Wed, 2004-10-20 at 05:37, Jim Robinson wrote:
>
>
>
>>Now in /etc/services I create the port & protocol entries:-
>>platypusd 5124/tcp # Platypus user utility daemon
>>
>>When I restart xinetd however I get this error:
>>Oct 19 15:32:25 venus xinetd[7520]: Exiting...
>>Oct 19 15:32:25 venus xinetd: xinetd shutdown succeeded
>>Oct 19 15:32:25 venus xinetd: xinetd startup succeeded
>>Oct 19 15:32:25 venus xinetd[13568]: service/protocol combination not in
/etc/services: platypusd/tcp
>>Oct 19 15:32:26 venus xinetd[13568]: xinetd Version 2.3.12 started with
libwrap loadavg options compiled in.
>>Oct 19 15:32:26 venus xinetd[13568]: Started working: 4 available services
>>
>>I have tried every which way I can think of to try and get xinetd to
read the correct lines from /etc/services but it just does not want to
jive.
>>
>>
>
>Do you use NIS or other alternative name services?
>
>The /etc/nsswitch.conf be be used to specify an alternative lookup
service for the services mappings, however the default is to use
>/etc/services
>
>Otherwise, your configuration looks fine.
>
>
>
You could also add the following attribute to your platypusd service
config file:
type = UNLISTED
That will let xinetd know that it shouldn't try to lookup the service.
Regards,
Matthew
--
fedora-legacy-list mailing list
fedora-legacy-list@xxxxxxxxxx
http://www.redhat.com/mailman/listinfo/fedora-legacy-list
|
