Requiste for starting service xinetd

10 More Discussions You Might Find Interesting

1. Solaris

Error when running starting server service

Hi I have installed using tar a program called rabbitmq, and when I try to start it according to documentation, I get the following error: /usr/local/sbin/rabbitmq_server-3.6.14/sbin# ./rabbitmq-server ./rabbitmq-server: .: local: not found ...

2. Red Hat

A service is not starting after booting up.

I require a service named "X" to be started automatically every time we restart the Linux 6.2 machine.But it is not starting. I have included the service in Init.d folder by $chkconfig --add X.But the application is not starting automatically after every reboot.I need to invoke $service X start...

3. Red Hat

Httpd service not starting... Error "Documentroot must be a directory"

I am working with CentOS 6.5. Indeed the document root /var/www/html is a directory and it is a mount point of one file system (not NFS) I observed, if I unmount that file system, I could able to start httpd. Is it restricted in CentOS 6.X that the Documentroot can not be a mount point? ...

4. Solaris

Rpcbind service not starting

Hello all, I have read just about every rpcbind not starting thread and article on the internet it seems, but I have not found a solution to my problem as of yet. I have a solaris 10 server that has been running with no problems for a while. The other day it crashed and would not boot to the gui...

5. UNIX for Advanced & Expert Users

error starting named service in CentOS

Hi Guys, I am configuring DNS BIND server I am getting following error, can someone please help ...below is my complete /etc/named.caching-nameserver.conf file :- # service named restart Stopping named: Starting named: Error in named...

6. Emergency UNIX and Linux Support

take ssh out of xinetd

i solved myself. thx!

7. Solaris

Service not starting Solaris10

On one of our server inetd service has stuck in transition state , tried restarting it but it does not do any thing and there is no associated inetd process for the same , how can i start it .. w/o rebooting it svcs inetd STATE STIME FMRI online* 16:44:55...

8. UNIX for Dummies Questions & Answers

Starting a service at startup.

Hi guys I want to start a service and a script SiteMonitor.sh at startup. To start with i have modified /etc/rc.local file. Here is the content of my /etc/rc.local file. #!/bin/sh # # This script will be executed *after* all the other init scripts. # You can put your own...

9. Solaris

Smf managed service not starting

Hi Experts, While playing with smf in my local system ( which is not in production ) i am unable to restart the service svc:/network/nfs/server:default . I tried starting it in different way, however unable to restart the same. I was checking the dependency for that I disabled the...

10. AIX

Service starting Problem

Dear All, When i am start the service netd i am facing the problem 0513-015 The inetd Subsystem could not be started Please check subsystem resources and try again later. please suggest me. It is urgent

LEARN ABOUT SUSE

xinetd.log

XINETD.LOG(5)							File Formats Manual						     XINETD.LOG(5)

NAME

       xinetd.log - xinetd service log format

DESCRIPTION

       A  service configuration may specify various degrees of logging when attempts are made to access the service. When logging for a service is
       enabled, xinetd will generate one-line log entries which have the following format (all entries have a timestamp as a prefix):

	      entry: service-id data

       The data depends on the entry.  Possible entry types include:

	      START	  generated when a server is started

	      EXIT	  generated when a server exits

	      FAIL	  generated when it is not possible to start a server

	      USERID	  generated if the USERID log option is used.

	      NOID	  generated if the USERID log option is used, and the IDONLY service flag is used, and the remote end  does  not  identify
			  who is trying to access the service.

       In the following, the information enclosed in brackets appears if the appropriate log option is used.

       A START entry has the format:

	      START: service-id [pid=%d] [from=%d.%d.%d.%d]

       An EXIT entry has the format:

	      EXIT: service-id [type=%d] [pid=%d] [duration=%d(sec)]

       type can be either status or signal.  The number is either the exit status or the signal that caused process termination.

       A FAIL entry has the format:

	      FAIL: service-id reason [from=%d.%d.%d.%d]

       Possible reasons are:

	      fork	     a certain number of consecutive fork attempts failed (this number is a configurable parameter)

	      time	     the time check failed

	      address	     the address check failed

	      service_limit  the allowed number of server instances for this service would be exceeded

	      process_limit  a limit on the number of forked processes was specified and it would be exceeded

       A DATA entry has the format:

	      DATA: service-id data

       The data logged depends on the service.

	      login	  remote_user=%s local_user=%s tty=%s

	      exec	  remote_user=%s verify=status command=%s
			  Possible status values:

			  ok	    the password was correct

			  failed    the password was incorrect

			  baduser   no such user

	      shell	  remote_user=%s local_user=%s command=%s

	      finger	  received string or EMPTY-LINE

       A USERID entry has the format:

	      USERID: service-id text

       The text is the response of the identification daemon at the remote end excluding the port numbers (which are included in the response).

       A NOID entry has the format:

	      NOID: service-id IP-address reason

SEE ALSO

       xinetd(1L), xinetd.conf(5)

								   28 April 1993						     XINETD.LOG(5)

Linux