Sponsored Content
Full Discussion: reload vsftp service
Operating Systems Linux Red Hat reload vsftp service Post 302572558 by fpmurphy on Thursday 10th of November 2011 09:55:05 AM
Old 11-10-2011
How are you running vsftpd? As a daemon or under xinetd?
 

10 More Discussions You Might Find Interesting

1. UNIX for Dummies Questions & Answers

VSFTP oddity

I am using smartFTP client on my windows machine to connect to a linux box of mine (different location) to download some large files 100+meg. The linux box is running vsftp. After several minutes of downloading, the connection suddenly dies, and I cannot reconnect to the box via FTP using ANY... (7 Replies)
Discussion started by: Spetnik
7 Replies

2. Linux

reload kernal without reboot

Hello! Does anyone know howto reload your kernal without rebooting the machine? I´ve updated the "/etc/security/limits.conf " file and need to make this active without rebooting the machine. this is Red Hat Advanced Server 2.1AS Regards... dOzY (3 Replies)
Discussion started by: dozy
3 Replies

3. UNIX for Dummies Questions & Answers

Reload Servlet in Tomcat

does anyone know how to reload servlet in tomcat? when do I actually reload it? when I modify any file in this server? (1 Reply)
Discussion started by: hamboy
1 Replies

4. UNIX for Dummies Questions & Answers

vsftp problems

Hi! I came across this site and was hoping someone could help me. I currently have a site that is hosted on a Virtual Dedicated Server running Fedora Core 4. This morning, while loading up files via Dreamweaver ftp I lost my connection. I contacted my hosting company and they said that I should... (7 Replies)
Discussion started by: skipdawg95
7 Replies

5. UNIX for Dummies Questions & Answers

how to reload the shell session

Hi there, I got to find out that if I make changes in the prompt or command aliases from .bashrc, I could apply those changes immediately with the command: source ~/.bashrc There's another situation when I'd like to apply changes without loging out and in again: If I add someone to a group of... (2 Replies)
Discussion started by: chebarbudo
2 Replies

6. UNIX Desktop Questions & Answers

Automatic reload of Thunar

I am using Thunar on FreeBSD 7.1 and XFCE. I would like the thunar window to reload automatically when a file has been added or deleted. Currently I press Ctrl-R, but perhaps a setting that I dont know of will do this automatically? (0 Replies)
Discussion started by: figaro
0 Replies

7. UNIX and Linux Applications

Vsftp

How do I assign an ftp user a default home directory such as /data/share upon login so they may not be able to traverse the filesystem (ie /) in vsftp? TIA (1 Reply)
Discussion started by: aikora92
1 Replies

8. UNIX for Dummies Questions & Answers

Command to reload a zone

I just created a CNAME and i was told a zone needs to be reloaded after creating a CNAME. What is the command to reload a zone after the CNAME has been created? Thanks in advance (1 Reply)
Discussion started by: German Shepherd
1 Replies

9. UNIX for Dummies Questions & Answers

Vsftp upload error

# Example config file /etc/vsftpd/vsftpd.conf # # The default compiled in settings are fairly paranoid. This sample file # loosens things up a bit, to make the ftp daemon more usable. # Please see vsftpd.conf.5 for all compiled in defaults. # # READ THIS: This example file is NOT an... (1 Reply)
Discussion started by: ment0smintz
1 Replies

10. Linux

VSFTP Anonymous users

Hi all, Im trying to enable anonymous users to upload files, e.g. i like my cisco router to upload config files ... for now iv i have file in /pub/upload/test.txt i can download the file from windows pc but if i like to to upload iv got this error im testing with windows pc but the same iv... (2 Replies)
Discussion started by: IvanMP
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. -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 02:12 AM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy