The Linux Administration group is for the discussion of technical issues technical issues that arise during the administration of Linux systems, including maintaining the operating system and supporting end-user applications.

There should be absolutely no need to restart the entire computer to get
some services running. This is *nix not windows and I achieve up-times
in excess of 300 days keeping all other services up while restarting
only those that have been reconfigured or recently installed. Locate the
method of the control for the services in question and simply (re)start
them as necessary.

DO not add DNS as inet service , DNS (usually bind software) work very well
as standalone daemon and the load of entire system will be higher because of
load/unload operations on each DNS invocation
Do you have any special reason to put it under inet management?

Name the file SERVICE_NAME. Then restart? xinetd to read your new service file.

On starting again, xinetd reads all files in /etc/xinetd.d only if /etc/xinetd.conf tells it to, via this line:

includedir /etc/xinetd.d

Check your /etc/xinetd.conf to confirm the location of its includedir.

This e-mail and the information it contains are confidential and may be
privileged. If you have received this e-mail in error please notify us
immediately. You should not copy it for any purpose, or disclose its
contents to any other person.

Inet and xinet is for starting non-daemon services, DNS and other like
apache, work as daemons in the system, hence they dont need to be started by the inetd.
Please beware which services you want to add and read if they can be started from
the inet service.

tim.clarke via linuxadmin-l wrote:
>
>
> There should be absolutely no need to restart the entire computer to get
> some services running. This is *nix not windows and I achieve up-times
> in excess of 300 days keeping all other services up while restarting
> only those that have been reconfigured or recently installed. Locate the
> method of the control for the services in question and simply (re)start
> them as necessary.

Although I would tend to agree, I suspect that you are missing a number
of kernel bug/security fixes as a kernel update requires a reboot.

cd /etc/xinetd.d
cp telnet YOUR_SERVICE_NAME
edit YOUR_SERVICE_NAME and change server name and other parameters if
needed
edit /etc/service and add port number & service name
reload/restart xinetd service

Copyright 1998-2015 Ziff Davis, LLC (Toolbox.com). All rights reserved. All product names are trademarks of their respective companies. Toolbox.com is not
affiliated with or endorsed by any company listed at this site.