Redhat Linux xinetd error

Operating Systems Linux Red Hat Redhat Linux xinetd error

Prev Next

07-18-2013

Registered User

28, 0

Join Date: Sep 2008

Last Activity: 15 September 2018, 11:07 AM EDT

Posts: 28

Thanks Given: 2

Thanked 0 Times in 0 Posts

Redhat Linux xinetd error

Dear all,

I am reciving the following error in the /var/log/messages of my system

Code:

Jul 18 11:14:27 airtest xinetd[12969]: START: echo-dgram pid=0 from=::ffff:XX.XX.XX.X
Jul 18 11:14:27 airtest xinetd[12969]: START: echo-dgram pid=0 from=::ffff:XX.XX.XX.X
Jul 18 11:19:17 airtest xinetd[12969]: START: echo-dgram pid=0 from=::ffff:XX.XX.XX.X
Jul 18 11:19:17 airtest xinetd[12969]: START: echo-dgram pid=0 from=::ffff:XX.XX.XX.X

Can somebody help me understand and resolve the above error?

Regards
Pistachio

Last edited by Scott; 07-18-2013 at 09:00 AM.. Reason: Code tags

pistachio

View Public Profile for pistachio

Find all posts by pistachio

Previous Thread | Next Thread

10 More Discussions You Might Find Interesting

1. Solaris

Looking for Xinetd for Solaris

I got the xinetd src from synack archive but when I try to compile I get errors all over the place, so am just wondering if anyone has a pre patched working version of xinetd for solaris 7 or higher there can share ??? thanks

2. Red Hat

Difference Redhat Linux/RH Enterprise Linux

what is the difference between Redhat Linux and Redhat Enterprise Linux. whereas Redhat linux have Server installation options too.

3. Emergency UNIX and Linux Support

take ssh out of xinetd

i solved myself. thx!

4. Red Hat

DELL M910 with RedHat Linux 5.5 getting "Buffer I/O error on device sdd"

Dear Guru, IHAC who is using Redhat Linux 5 on DELL M910. When system bootup, it show "Buffer I/O error on device sdd" error message. Below is the "dmesg" output. The scenario is: If more external FC SAN disk LUN add, the device would change other name. So it will impact the raw device...

5. Red Hat

"No Drives Found" error during Redhat Linux AS 4 installation

I'm trying to install Redhat LInux AS 4 update 4 on an IBM x306 series server. I keep getting following error: "No Drives Found. An error has occurred - no valid devices were found on which to create new file systems. Please check your hardware for the cause of this problem." I called IBM and...

6. Linux

uninstall xinetd

hey, haha it's me agian, i think that my xinetd is messed up, i am unable to stop it. I can start it though...lol. I just wonderd how can i uninstall it so i can reinstall it...maybe this time it'll work. I'm running RH 7.1 i think. thanks:)

7. UNIX for Dummies Questions & Answers

Linux RedHat. Help please.

I from russia. install rus Linux RedHat. When i load linux it ask me for user name and pass... and up of ask form label: Welcome to localhost... dont remember... what i want write in it? (sorry, bad english..:( )..

8. UNIX Desktop Questions & Answers

RedHat Linux Cd

I am wondering if anyone has copies (or can burn me a copy) of RedHat Linux. I will pay shipping charges... I don't have a CD burner and i dont want to run it off of my hard drive... please email me at: empireinfo623@yahoo.com or baldwitm@muc.edu

9. UNIX for Dummies Questions & Answers

redhat linux 7.3

hi, just installed redhat linux 7.3 on my server, and put it in gnome gui. Does anyone know what software i need to run a web server??? and what software i need to set up a proxy to secure it? also, if these are free to download, can you give me the links. Thanx

10. Cybersecurity

xinetd.conf

i want to edit inetd.conf for security on my redhat 7.1 box, but i dont have it in my /etc directory, rather, i have xinetd.conf. Can i use xinetd.conf for the same purpose, is it as useful as inetd.conf?

LEARN ABOUT DEBIAN

xinetd

XINETD(8)						      System Manager's Manual							 XINETD(8)

NAME

       xinetd - the extended Internet services daemon

SYNOPSIS

       xinetd [options]

DESCRIPTION

       xinetd  performs  the same function as inetd: it starts programs that provide Internet services.  Instead of having such servers started at
       system initialization time, and be dormant until a connection request arrives, xinetd is the only daemon process started and it listens	on
       all  service  ports  for  the  services	listed	in  its configuration file. When a request comes in, xinetd starts the appropriate server.
       Because of the way it operates, xinetd (as well as inetd) is also referred to as a super-server.

       The services listed in xinetd's configuration file can be separated into two groups.  Services in the first group are called multi-threaded
       and  they  require  the forking of a new server process for each new connection request.  The new server then handles that connection.  For
       such services, xinetd keeps listening for new requests so that it can spawn new servers.  On the other hand, the second group includes ser-
       vices  for  which the service daemon is responsible for handling all new connection requests.  Such services are called single-threaded and
       xinetd will stop handling new requests for them until the server dies.  Services in this group are usually datagram-based.

       So far, the only reason for the existence of a super-server was to conserve system resources by avoiding to fork a lot of  processes  which
       might  be dormant for most of their lifetime.  While fulfilling this function, xinetd takes advantage of the idea of a super-server to pro-
       vide features such as access control and logging.  Furthermore, xinetd is not limited to services listed in /etc/services.  Therefore, any-
       body can use xinetd to start special-purpose servers.

OPTIONS

       -d     Enables debug mode. This produces a lot of debugging output, and it makes it possible to use a debugger on xinetd.

       -syslog syslog_facility
	      This  option  enables  syslog logging of xinetd-produced messages using the specified syslog facility.  The following facility names
	      are supported: daemon, auth, user, local[0-7] (check syslog.conf(5) for their meanings).	This option is ineffective in  debug  mode
	      since all relevant messages are sent to the terminal.

       -filelog logfile
	      xinetd-produced  messages  will  be  placed  in the specified file.  Messages are always appended to the file.  If the file does not
	      exist, it will be created.  This option is ineffective in debug mode since all relevant messages are sent to the terminal.

       -f config_file
	      Determines the file that xinetd uses for configuration. The default is /etc/xinetd.conf.

       -pidfile pid_file
	      The process ID is written to the file. This option is ineffective in debug mode.

       -dontfork
	      Tells xinetd to stay in the foreground rather than detaching itself, to support being run from  init  or	daemontools.  This  option
	      automatically sets -stayalive (see below).

       -stayalive
	      Tells xinetd to stay running even if no services are specified.

       -limit proc_limit
	      This option places a limit on the number of concurrently running processes that can be started by xinetd.  Its purpose is to prevent
	      process table overflows.

       -logprocs limit
	      This option places a limit on the number of concurrently running servers for remote userid acquisition.

       -version
	      This option causes xinetd to print out its version information.

       -inetd_compat
	      This option causes xinetd to read /etc/inetd.conf in addition to the standard xinetd config files.  /etc/inetd.conf  is  read  after
	      the standard xinetd config files.

       -inetd_ipv6
	      This  option  causes  xinetd  to	bind  to IPv6 (AF_INET6) addresses for inetd compatibility lines (see previous option).  This only
	      affects how /etc/inetd.conf is interpreted and thus only has any effect if the -inetd_compat option is also used.

       -cc interval
	      This option instructs xinetd to perform periodic consistency checks on its internal state every interval seconds.

       The syslog and filelog options are mutually exclusive.  If none is specified, the default is syslog using the daemon facility.  You  should
       not confuse xinetd messages with messages related to service logging. The latter are logged only if this is specified via the configuration
       file.

CONTROLLING XINETD

       xinetd performs certain actions when it receives certain signals.  The actions associated with the specific signals  can  be  redefined	by
       editing config.h and recompiling.

       SIGHUP	      causes  a  hard reconfiguration, which means that xinetd re-reads the configuration file and terminates the servers for ser-
		      vices that are no longer available. Access control is performed again on running servers by checking  the  remote  location,
		      access  times  and  server  instances. If the number of server instances is lowered, some arbitrarily picked servers will be
		      killed to satisfy the limit; this will happen after any servers are terminated because of failing  the  remote  location	or
		      access  time  checks.  Also, if the INTERCEPT flag was clear and is set, any running servers for that service will be termi-
		      nated; the purpose of this is to ensure that after a hard reconfiguration there will be no running servers that  can  accept
		      packets from addresses that do not meet the access control criteria.

       SIGQUIT	      causes program termination.

       SIGTERM	      terminates all running servers before terminating xinetd.

       SIGUSR1	      causes  an  internal  state  dump  (the default dump file is /var/run/xinetd.dump; to change the filename, edit config.h and
		      recompile).

       SIGABRT	      causes an internal consistency check to verify that the data structures used by the program have not been  corrupted.   When
		      the check is completed xinetd will generate a message that says if the check was successful or not.

       On reconfiguration the log files are closed and reopened. This allows removal of old log files.

FILES

       /etc/xinetd.conf    default configuration file
       /var/run/xinetd.dump
			   default dump file

SEE ALSO

       inetd(8),

       xinetd.conf(5),

       xinetd.log(5)

       http://cr.yp.to/daemontools.html

AUTHOR

       Panos Tsirigotis, CS Dept, University of Colorado, Boulder Rob Braun

PRONUNCIATION

       zy-net-d

								   14 June 2001 							 XINETD(8)

Red Hat