Sponsored Content
Top Forums UNIX for Dummies Questions & Answers Strange email problem, red hat/qmail Post 35067 by LivinFree on Thursday 27th of March 2003 12:21:36 AM
Old 03-27-2003
I'm not quite sure if Redhat 5.1 had the ability yet (yeesh... that's the oldest production Redhat box I've ever heard of - I hope it being patched), but xinetd can bind to an interface, as opposed to listening on all at once. Are you using inted or xinetd? Or either, for that matter? Was anything changed, upgraded, edited, or added in the past few days?
 

10 More Discussions You Might Find Interesting

1. UNIX for Dummies Questions & Answers

Problem Downloading Red Hat

I've been having problems downloading Red Hat 7.2 from their FTP site. It downloads rather slowly(between 2-3k/sec, I'm on broadband) and after about 10 minutes stops downloading altogether. Am I doing something wrong? (2 Replies)
Discussion started by: Tradewynd
2 Replies

2. UNIX for Dummies Questions & Answers

Please Help Me With This Linux Red Hat 7.2 Modem Problem

I cant get my modem to work. Linux just isn't recognizing it. every time I typed wvdial, i get a message saying my modem is not responding I tried looking for drivers at the website Neo directed me to but I just couldn't find the right one from the information I was given about my modem... (2 Replies)
Discussion started by: TRUEST
2 Replies

3. UNIX for Dummies Questions & Answers

Linux Red Hat 7.2 Problem

how come red hat doesn't have this programs which was already supposed to be on it?? take for instance, I was reading this Linux book that says for me to do some work in glint X11 client for packagement. it says glint is accessible from the command line or control panel. the problem is, I... (4 Replies)
Discussion started by: TRUEST
4 Replies

4. UNIX Desktop Questions & Answers

Red Hat loading problem

when i try to load Redhat 7.2 the screen gets all mished together as if it were a meltdown the book says its a prob with X but it dosnt really say what to do WINMe works fine i have a radeon 64 MB card 1 gig processor and 2 HDs on a Dell 1 GHZ how do i fix this ? (1 Reply)
Discussion started by: ASpin
1 Replies

5. Linux

Red Hat RPM problem

I have my system setup different then the conventional setup: # df -h Filesystem Size Used Avail Use% Mounted on /dev/hdc2 2.0G 977M 936M 52% / /dev/hdc1 97M 9.0M 83M 10% /boot none 251M 0 251M 0% /dev/shm So when I try... (2 Replies)
Discussion started by: jasonr
2 Replies

6. Linux

Installation Problem on Red hat linux 9

Hi, I am trying to install our new acquired Red Hat linux 9 on Compaq Proliant ML370. However, l has already configured the raid 0+1. The linux installation starts from the CD, its allows for the selection of Language, keyboard but l am stocked at choosing the installation package media. I... (4 Replies)
Discussion started by: kayode
4 Replies

7. UNIX for Dummies Questions & Answers

Problem Red Hat 9 Installation

I have a problem with a red hat 9 install on a compaq laptop. I installed the OS and everything tests ok but It boots to a blank screen instead of the GUI login I wanted. What can I do to correct this instead of installing all over. I tried the rescue option several times and tried to run... (2 Replies)
Discussion started by: vedder191
2 Replies

8. Linux

Red Hat linux(Advance server) problem

we are receiving following error in our application server & server not booted:- "INIT IP ID x ,Respawning too fast; disable for 5 minutes." Please give me solution for above mention problem as early as possible . AKM (3 Replies)
Discussion started by: akm9999
3 Replies

9. Infrastructure Monitoring

Problem Installing Cacti on Red Hat

Can someone please point me in the direction of where I can find out how to install cacti? there doesn't seem to be straightforward steps for it. after downloading the tar.gz file from cacti.net, there's basically no instructions of what to do from that point on. any help will be appreciated. ... (1 Reply)
Discussion started by: SkySmart
1 Replies

10. Red Hat

Red Hat application server ssl keystore problem

A client is accessing our JBoss server. In the past, we set up a keystore and everything worked fine. That certificat expired and we've installed the new one. Now the client is getting the following error - HTTP/1.1 500 Internal Server Error Date: Mon, 14 Apr 2014 13:25:44 GMT Server:... (1 Reply)
Discussion started by: kkinney
1 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. -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)
All times are GMT -4. The time now is 11:48 AM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy