Sponsored Content
Full Discussion: ftp problem?
Operating Systems Linux Red Hat ftp problem? Post 302528323 by hadimotamedi on Tuesday 7th of June 2011 02:40:53 AM
Old 06-07-2011
ftp problem?

Dear All
I cannot ftp to my RedHat server from MS Windows machine ,but ping and telnet are ok. I checked as the following :
#chkconfig tftp on
#setup
After enabling tftp service, still the ftp is not ok but ping & telnet are ok. Can you please help me?
Thank you
 

10 More Discussions You Might Find Interesting

1. UNIX Desktop Questions & Answers

ftp problem

I use FTP in a shell script to transfer the files to a remote server. Sometimes the program hangs without returning any errors after the command ftp server_name How do you detect from within the shell that something is wrong? How do you trap the errors returned by ftp command? Any help... (3 Replies)
Discussion started by: marusia
3 Replies

2. UNIX for Dummies Questions & Answers

FTP problem. please help

can someone tell me how I can deal with a problem am having concerning users that are faliing to use one of the shells specified in the /etc/shells file. as a result, am told, these users are bound fail to connect via FTP. i know i goto check the /etc/shells file on the target host but what... (5 Replies)
Discussion started by: TRUEST
5 Replies

3. Shell Programming and Scripting

Ftp problem

hi i have written a shell to automate the ftp process for the particular file.iam getting errors when try to ftp it.And i am cant get why the lcd is not being taken properly as it is taking during runtime.can anyone give me a solution here its my code DATE=`date '+%d_%m_%Y'`... (1 Reply)
Discussion started by: cskumar
1 Replies

4. Solaris

FTP problem

Hi Guys, Got problem when I tried to get files from Solaris server to my PC. The connection transfer was using FTP and the connection was made from the solaris server to my PC. Here's what happened when the file transfer being made: # ftp 10.192.23.230 Connected to 10.192.23.230. 220... (9 Replies)
Discussion started by: raskita
9 Replies

5. HP-UX

FTP problem

We recently moved offices and checked our network ID. I have configured all the files that I am familiar with and am able to telnet and ping from my pc but I am unable to ftp. Any suggestions...Thanks (5 Replies)
Discussion started by: andrewd
5 Replies

6. Shell Programming and Scripting

problem with ftp:

i have got 2 servers in unix(IBM AIX 5.3) namely below. test1 production1 i m trying to do ftp from test1 to production1. ------------------------------------------------------------ below the script called naveed1.sh which lies in test1,also it have two files called ... (2 Replies)
Discussion started by: ali560045
2 Replies

7. Shell Programming and Scripting

problem in FTP

i m able to login to Unix box from window's cmd can anyone tell me how to run a script from window cmd using ftp ? the script is in unix box and i need to run from windows CMD using ftp (2 Replies)
Discussion started by: ali560045
2 Replies

8. Shell Programming and Scripting

FTP Problem

Hello experts, I've got the following script that is supposed to FTP a file to another box. #!/usr/bin/ksh while read line do HOST=`echo "$line" | cut -d" " -f1` USER=`echo "$line" | cut -d" " -f2` PASSWD=`echo "$line" | cut -d" " -f3` PATH=`echo "$line" | cut -d" " -f4` done <... (5 Replies)
Discussion started by: King Nothing
5 Replies

9. Shell Programming and Scripting

ftp problem

Hello, I have a very simple script that put a file in server ftp #!/bin/bash var="ITW-trail-templiers-samedi" cd /Users/$USER/Desktop ftp -n >&1 << EOF open server quote user "user" cd oberon binary put "$var" bye EOF I have error : 200 Type set to IMAGE. remote:... (2 Replies)
Discussion started by: protocomm
2 Replies

10. Shell Programming and Scripting

Ftp problem

Hi, I have a problem when i want to get a filename from an ftp server when a space is before his name. example: "spacetestFile" The ftp server return an error "no asset or no permission" though the file exist ? Why it behave in this way ? (8 Replies)
Discussion started by: protocomm
8 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)
All times are GMT -4. The time now is 11:37 AM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy