Well what a strange world we live in. I have literally just finished getting ftp/telnet working on my SuSE 8.0 install and what do I find? This posting! So here is some additional information: By default, it appears that inetd/xinetd is NOT enabled. I use xinetd rather than inetd as there is more control over configuration. To enable startup/shutdown of inetd (xinetd) place symbolic links in /etc/init.d/rc3.d and /etc/init.d/rc5.d. The configuration file for xinetd is /etc/xinetd.conf (and for inetd is /etc/inetd.conf). Now services started by xinetd use the tcp wrappers so to get things working you will have to make some edits to the files /etc/hosts.allow and /etc/hosts.deny. See man 5 hosts_access for details of the format. I use to use proftpd as the ftp daemon but there have been some security problems to instead I now use vsftpd. Configuration file for this is /etc/vsftpd.conf Hope this is enough to get you going. If you still have problems, drop me a note and I will try and help. Kind regards, Simon Alexandr Malusek wrote:

Jay Vollmer writes:

...

...

I have installed SuSE 8.0 (Professional) on intel. When trying to telnet or ftp, I am getting an error message "Connection Refused".

Please help me configure FTP and Telnet or point me to the resources which would help me do the same.

Services such as these are enabled by editing the /etc/inetd.conf file.

I'll only add the "Start/stop services (inetd)" module of YaST2 in Network/Basic can be used instead.

If I remember it right, some server packages must be installed, they are not in the default configuration. Anyway, ssh and scp or vsftp are safer alternatives.

-- Alexandr.Malusek@imv.liu.se

Silviu Marin-Caea wrote:

Simon Heaton wrote:

...

By default, it appears that inetd/xinetd is NOT enabled. I use xinetd rather than inetd as there is more control over configuration. To enable startup/shutdown of inetd (xinetd) place symbolic links in /etc/init.d/rc3.d and /etc/init.d/rc5.d. The configuration file for xinetd is /etc/xinetd.conf (and for inetd is /etc/inetd.conf).

Manually putting symbolic links in /etc/rcX.d is not the elegant way.

chkconfig --add xinetd

I must confess that I have not stumbled across this utility before. Looks useful thank you. How does it determine dependencies, same as insserv? Kind regards, Simon

Anders Johansson wrote:

On Tuesday 16 July 2002 18.44, Simon Heaton wrote:

chkconfig is a "compatibility" app. It's there because some redhat rpms look for it. The underlying code is insserv, AFAICS

I know otherwise: it's not a compatibility app, but a new wrapper that appeared in SuSE 8. -- Silviu Marin-Caea Systems Engineer Linux/Unix http://www.genesys.ro Phone +40723-267961

* Silviu Marin-Caea [07-17-02 00:23]:

Anders Johansson wrote:

...

On Tuesday 16 July 2002 18.44, Simon Heaton wrote:

...

chkconfig is a "compatibility" app. It's there because some redhat rpms look for it. The underlying code is insserv, AFAICS

I know otherwise: it's not a compatibility app, but a new wrapper that appeared in SuSE 8.

SuSE 7.3: #!/bin/sh # /sbin/chkconfig is for RedHat based systems only. The method is # not compatible with SuSE Linux, since we use LSB conform init # scripts. There is no way to convert chkconfig based init scripts # to LSB conform one. You have to do it yourself (look at # /etc/init.d/skeleton for a good documented example). # # This file here is only to make RPM happy and to give user the # chance to install RPMs which requieres /sbin/chkconfig. exit 0 -- Patrick Shanahan Registered Linux User #207535 @ http://counter.li.org