Welcome to Linux Knowledge Base and Tutorial
"The place where you learn linux"
Let The Music Play: Join EFF Today

 Create an AccountHome | Submit News | Your Account  

Tutorial Menu
Linux Tutorial Home
Table of Contents

· Introduction to Operating Systems
· Linux Basics
· Working with the System
· Shells and Utilities
· Editing Files
· Basic Administration
· The Operating System
· The X Windowing System
· The Computer Itself
· Networking
· System Monitoring
· Solving Problems
· Security
· Installing and Upgrading
· Linux and Windows

Glossary
MoreInfo
Man Pages
Linux Topics
Test Your Knowledge

Site Menu
Site Map
FAQ
Copyright Info
Terms of Use
Privacy Info
Disclaimer
WorkBoard
Thanks
Donations
Advertising
Masthead / Impressum
Your Account

Communication
Feedback
Forums
Private Messages
Surveys

Features
HOWTOs
News Archive
Submit News
Topics
User Articles
Web Links

Google
Google


The Web
linux-tutorial.info

Who's Online
There are currently, 78 guest(s) and 0 member(s) that are online.

You are an Anonymous user. You can register for free by clicking here

  

xinetd



SYNOPSIS

       xinetd [options]


DESCRIPTION

       xinetd performs the same function as inetd: it starts pro­
       grams 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 ser­
       vices, xinetd keeps listening for new requests so that  it
       can  spawn  new  servers.   On  the other hand, the second
       group includes services 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  provide
       features such as access control and logging.  Furthermore,
       xinetd is not limited to services listed in /etc/services.
       Therefore, anybody can use xinetd to start special-purpose
       servers.


OPTIONS

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

       -syslog syslog_facility
              This option enables syslog logging  of  xinetd-pro­
              duced 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

       -dontfork
              Tells  xinetd to stay in the foreground rather than
              detaching itself, to support being run from init or
              daemontools.  This option automatically sets -stay­
              alive (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 concur­
              rently 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 concur­
              rently  running  servers for remote userid acquisi­
              tion.

       -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.

       -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  services
                      that  are  no longer available. Access con­
                      addresses that do not meet the access  con­
                      trol criteria.

       SIGQUIT        causes program termination.

       SIGTERM        terminates  all running servers before ter­
                      minating 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).

       SIGIOT         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 success­
                      ful 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)
  
Show your Support for the Linux Tutorial

Purchase one of the products from our new online shop. For each product you purchase, the Linux Tutorial gets a portion of the proceeds to help keep us going.


Login
Nickname

Password

Security Code
Security Code
Type Security Code


Don't have an account yet? You can create one. As a registered user you have some advantages like theme manager, comments configuration and post comments with your name.

Help if you can!


Amazon Wish List

Did You Know?
You can choose larger fonts by selecting a different themes.


Friends



Tell a Friend About Us

Bookmark and Share



Web site powered by PHP-Nuke

Is this information useful? At the very least you can help by spreading the word to your favorite newsgroups, mailing lists and forums.
All logos and trademarks in this site are property of their respective owner. The comments are property of their posters. Articles are the property of their respective owners. Unless otherwise stated in the body of the article, article content (C) 1994-2013 by James Mohr. All rights reserved. The stylized page/paper, as well as the terms "The Linux Tutorial", "The Linux Server Tutorial", "The Linux Knowledge Base and Tutorial" and "The place where you learn Linux" are service marks of James Mohr. All rights reserved.
The Linux Knowledge Base and Tutorial may contain links to sites on the Internet, which are owned and operated by third parties. The Linux Tutorial is not responsible for the content of any such third-party site. By viewing/utilizing this web site, you have agreed to our disclaimer, terms of use and privacy policy. Use of automated download software ("harvesters") such as wget, httrack, etc. causes the site to quickly exceed its bandwidth limitation and are therefore expressly prohibited. For more details on this, take a look here

PHP-Nuke Copyright © 2004 by Francisco Burzi. This is free software, and you may redistribute it under the GPL. PHP-Nuke comes with absolutely no warranty, for details, see the license.
Page Generation: 0.09 Seconds