10 More Discussions You Might Find Interesting
1. 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 (4 Replies)
Discussion started by: Wpgn
4 Replies
2. Red Hat
Dear all,
I am reciving the following error in the /var/log/messages of my system
Jul 18 11:14:27 airtest xinetd: START: echo-dgram pid=0 from=::ffff:XX.XX.XX.X
Jul 18 11:14:27 airtest xinetd: START: echo-dgram pid=0 from=::ffff:XX.XX.XX.X
Jul 18 11:19:17 airtest xinetd: START: echo-dgram... (1 Reply)
Discussion started by: pistachio
1 Replies
3. Emergency UNIX and Linux Support
i solved myself.
thx! (2 Replies)
Discussion started by: pabloli150
2 Replies
4. Red Hat
Hello all,
I´m trying to configure the ftp service (port 21) in a Red Hat Enterprise 4 from xinetd.
Anybody have done this?
Thank you in advance. (3 Replies)
Discussion started by: mig28mx
3 Replies
5. Linux
Hi,
Once again I came to get rescued in a situation where one of my workstations has this ierd thing that "xinetd" won't start at reboot or shutdown. I have done the follwoing but no change in results.
chkconfig --list xinetd
xinetd 0:off 1:off 2:on 3:on 4:on 5:on ... (2 Replies)
Discussion started by: harjitsingh
2 Replies
6. Shell Programming and Scripting
Hello there,
I hope I took the right forum...
I never worked with Perl, but now I have to get a simple fileserver running. The goal is to deliver an XML file (it's part of a new security model in the Flashplayer, see Adobe - Developer Center : Setting up a socket policy file server for more... (9 Replies)
Discussion started by: blemmo
9 Replies
7. Solaris
Hello,
I'm working on a Solaris 9/Sparc machine and it has the Solaris 10 version of Perl (5.8.8) installed on it, which always requires all kinds of library files that Solaris 9 doesn't come with. I think the best way to do is to uninstall this wrong version and install the correct Solaris 9... (1 Reply)
Discussion started by: alanlh
1 Replies
8. UNIX for Advanced & Expert Users
I do make sure that in my system (redhat 9.0 with eveything installed)
file cvspserver with correct content
in directory /etc/xinetd.d/
line
cvspserver 2401/tcp
cvspserver 2401/udp
in file /etc/service
I aslo restart service xinetd
but when I issue command ... (1 Reply)
Discussion started by: victorvvk
1 Replies
9. Linux
hi...
i am trying to find out the services which should be started before the service xinetd can be started.
I have read thru the /etc/rc.d/init.d script and i think xinetd depends on service network as it checks whether the variable NETWORKING is set or not
|| exit 0
Does it... (0 Replies)
Discussion started by: tuxfood
0 Replies
10. Cybersecurity
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? (2 Replies)
Discussion started by: lealyz
2 Replies
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.
-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).
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 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)