Sponsored Content
Operating Systems SCO Config FTP on SCO Like proftpd Post 303037455 by Arcanisgk on Thursday 1st of August 2019 04:25:39 PM
Old 08-01-2019
Quote:
Originally Posted by MadeInGermany
Ok, it seems that nowait is correct (inetd fires a ftpd for each connection).
What is -a option? Does it use tcp wrappers?
Did you read the man page
Code:
man ftpd

Description:

ftpd is the Internet File Transfer Protocol server process. The
server uses the TCP protocol and listens at the port specified in
the ftp service specification; see services(SFF).

ftpd is started by the super server inetd, and therefore must
have an entry in inetd's configuration file, /etc/inetd.conf. See
inetd(ADMN) and inetd.conf(SFF).
-a
Specify that the access file, /etc/ftpaccess, must be
present. This is the default behavior.
 

10 More Discussions You Might Find Interesting

1. UNIX for Dummies Questions & Answers

using ftp on sco

I'm using SCO unix - 5 as server and stallion board to connect my users on serial comm. I want some of my files generetd on unix to be copied to one of my window'95 based system. I can use crosstalk loaded on windows system to log in automatically and 'cat the file' which will be than stored... (1 Reply)
Discussion started by: skant
1 Replies

2. UNIX for Dummies Questions & Answers

[sos]How to config my Sco openserver 5.06

How to config my Sco openserver 5.06 to link on the Internet.MY Etherent sever is Winme........... Can u tell me from the configure of netcard start......... thanx for help...............thanx a lot (1 Reply)
Discussion started by: dingxf
1 Replies

3. IP Networking

RH 7.2 FTP Server Config

Is it possible to ftp from WinXp to a Linux box? I have the the ftp server set up to take the request from the WinXp box but each time I try to connect I keep getting an error, Connection established, unknown error(windows ftp program) or if I try to ftp from the DOS prompt I get ftp connect:... (3 Replies)
Discussion started by: flounder
3 Replies

4. UNIX for Advanced & Expert Users

FTP - Sco Unix to ProFTPD Error

First off I did try google for help on this topic, didn't really find anything. When I try to ftp from my SCO Unix box (SCO_SV servername 3.2 5.0.5 i386) to a proFTPD server within my company I get this error Connected to 10.?.?.?. 220 ProFTPD Server ftp.hostname.com Name (10.?.?.?:root):... (1 Reply)
Discussion started by: whegra
1 Replies

5. UNIX for Dummies Questions & Answers

Enable FTP on SCO

My goal is to use FTP to transfer file between PC and SCO Unix server.When I try to connect via FTP with root user, it failed. What should I do? How to configure ftpaccess? Thanks in advance! (2 Replies)
Discussion started by: Vladan
2 Replies

6. UNIX for Dummies Questions & Answers

FTP from SCO UNIX to Windows XP PC

I am trying to start an FTP session from my UNIX PC to a PC running XP. I aim to run a cron to manipulate remote files on the Windows M/C. I cannot connect to the Windows M/C when i start rthe FTP session on the UNIX box. I can do it fine the other way round. I have set entries in /etc/hosts... (2 Replies)
Discussion started by: farmacy
2 Replies

7. UNIX for Dummies Questions & Answers

Problem with FTP o n Unix SCO

my problem is like this while ftping locally it works, but when users from WAN try the ftp services it doesnt comes the message it displays is as follows "connection closed by remote host " please help Thanks (5 Replies)
Discussion started by: Athos19
5 Replies

8. Shell Programming and Scripting

FTP credentials from a config file

Hi, I am using the following syntax to connect to an FTP server and paste the file. Based on the value in the variable $Folder, i want to connect to different folders on the same server. The credential is different to access different folders. How to get the user name and password from a... (3 Replies)
Discussion started by: ashok.k
3 Replies

9. Solaris

RBAC with ftp/sftp using proftpd

I'm using proftpd to manage my ftp/sftp connections but would like to use RBAC to only allow ftp/sftp connections. Has anyone done this or can point me in the right direction? This is my first experience trying to use RBAC. Thanks in advance. (2 Replies)
Discussion started by: toor13
2 Replies

10. Shell Programming and Scripting

Odd looping issue with NET::FTP and Proftpd

Hello, I'm a UNIX SysAdmin at a large webhosting company and we have a vendor that provides a service which involves the ftp'ing of files from their servers to ours. They initiate FTP using a perl script with NET::FTP. When they try to transfer files (and delete files over ftp), there is... (3 Replies)
Discussion started by: tmmgeekette
3 Replies
RECONF-INETD(8) 					  System Administration Utilities					   RECONF-INETD(8)

NAME
reconf-inetd - utility to update /etc/inetd.conf and restart inetd SYNOPSIS
reconf-inetd [--verbose] reconf-inetd --sanity-check=fragment [... fragment] DESCRIPTION
reconf-inetd is a maintainer tool that updates inetd.conf. Such updates are based on xinetd.conf-like configuration fragments in /usr/share/reconf-inetd (where server packages install their fragments) and /usr/lib/reconf-inetd (where reconf-inetd keeps track of which inetd.conf entries have been added by itself). reconf-inetd identifies every inetd.conf entry based on the combination of three fields: service name, protocol, and server path. This allows multiple inetd.conf entries for the same service, eg. for IPv4 and IPv6 versions, as well as for different upstreams (eg. proftpd versus ftpd-ssl). reconf-inetd will not add inetd.conf entries for services whose server path is non-existent, or whose combination of protocol, service name and server path matches an existing inetd.conf entry. reconf-inetd does not support internal services. OPTIONS
-h, --help show this help message and exit -c FRAGMENTS_TO_CHECK, --sanity-check=FRAGMENTS_TO_CHECK test the validity of the xinetd.conf-like configuration fragments, as specified by a space-separated list of files -v, --verbose explain what happens -V, --version show version and exit FILES
reconf-inetd declares a file-based dpkg trigger on /usr/share/reconf-inetd. Shadow fragment files are stored in /var/lib/reconf-inetd. A log file is kept at /var/log/reconf-inetd.log FRAGMENT STRUCTURE
reconf-inetd fragments are a much simplified version of xinetd.conf(5) fragments. They have this structure: service <service_name> { <attribute> = <value> <value> ... ... } Of the wide range of fields foreseen by xinetd.conf(5), reconf-inetd honors only these fields: socket_type protocol (optional, except for RPC and unlisted services) port (optional, except for unlisted non-RPC services) wait user server server_args (optional) If the protocol field is omitted and the service is listed, reconf-inetd will assume the protocol of the first matching entry from /etc/services. That will be tcp or udp, which currently implies IPv4, so if the intention is IPv6, then tcp6 or udp6 should be explicitly specified in the protocol field. Unlike, regular xinetd fragment files, reconf-inetd fragment files must have only one service per file. A package that provides more than one service must install a separate fragment file for each service. This is the case to allow for removal of individual services, by simply removing the related file. /usr/share/reconf-inetd fragments are not configuration files; they're just input to reconf-inetd. Local admin configuration should be applied to inetd.conf tcpd-configured service fragments will typically have server set to /usr/sbin/tcpd and server_args will start with the path to the actual server executable. Follows a reproduction of valid atrribute values from xinetd.conf(5): socket_type Possible values for this attribute include: stream stream-based service dgram datagram-based service raw service that requires direct access to IP seqpacket service that requires reliable sequential datagram transmission protocol determines the protocol that is employed by the service. The protocol must exist in /etc/protocols. If this attribute is not defined, the default protocol employed by the service will be used. port determines the service port. wait This attribute determines if the service is single-threaded or multi-threaded and whether or not xinetd accepts the connection or the server program accepts the connection. If its value is yes, the service is single-threaded; this means that xinetd will start the server and then it will stop handling requests for the service until the server dies and that the server software will accept the connection. If the attribute value is no, the service is multi-threaded and xinetd will keep handling new service requests and xinetd will accept the connection. It should be noted that udp/dgram services normally expect the value to be yes since udp is not connection oriented, while tcp/stream servers normally expect the value to be no. user determines the uid for the server process. The user attribute can either be numeric or a name. If a name is given (recommended), the user name must exist in /etc/passwd. This attribute is ineffective if the effective user ID of xinetd is not super-user. server determines the program to execute for this service. server_args determines the arguments passed to the server. FRAGMENT EXAMPLES
Here is an example fragment: service finger { socket_type = stream protocol = tcp6 wait = no user = nobody server = /usr/sbin/fingerd } and it's tcpd-enabled version: service finger { socket_type = stream protocol = tcp6 wait = no user = nobody server = /usr/sbin/tcpd server_args = /usr/sbin/fingerd } BUGS
Known issues and missing features are listed in /usr/share/doc/reconf-inetd/TODO HISTORY
reconf-inetd is a replacement for update-inetd. The motivation for and design of reconf-inetd is detailed at the Debian Enhancement Pro- posal 9, at http://dep.debian.net/deps/dep9/, a copy of which is locally available at /usr/share/doc/reconf-inetd/dep9.html AUTHOR
reconf-inetd was designed, documented and implemented by Serafeim Zanikolas <sez@debian.org> SEE ALSO
inetd.conf(5), xinetd.conf(5), inetd(8), update-inetd(8), deb-triggers(5) reconf-inetd 1.120603 June 2012 RECONF-INETD(8)
All times are GMT -4. The time now is 04:18 PM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy