On Sun, Mar 18, 2012 at 10:11:34AM -0500, pe...@easthope.ca wrote:
> From: Sven Hoexter
> Date: Sun, 18 Mar 2012 07:49:46 +0100
> > There are at least two options. ;)
>
> > 1) Stop inetd all together if you don't run any services through
> > inetd (or xinetd).
>
> To what purpose? There is no h
Gary,
> OK. Now I have 3 machines that are setup identically. The vsftpd.conf
> files have the following settings:
>
> Listen=YES
> #Listen_IPV6
> Anonymous=YES
> #Local_enabled=YES
> #Write_enabled=YES
Setting Local_enabled=YES will allow you to log in.
The configuration
On Sat, Mar 17, 2012 at 02:21:35PM -0700, Gary Roach wrote:
Hi,
> COMMAND PID USER FD TYPE DEVICE SIZE/OFF NODE NAME
> inetd 1946 root8u IPv4 130958 0t0 TCP *:ftp (LISTEN)
>
> The good machine shows that vsftpd is attached to the port.
>
> I'm not sure how to correct this but
On 01/-10/-28163 11:59 AM, Jon Dowland wrote:
On 16/03/12 01:50, Gary Roach wrote:
500 OOPS: could not bind listening IPv4 socket
Are you attempting to start it by hand as root?
If so, can you try "lsof -ni:21"? It looks like something else
has bound to your port 21.
Good suggestion, On
On 01/-10/-28163 11:59 AM, Jon Dowland wrote:
Try running /usr/sbin/vsftpd by hand (as root) from a session on your
server. Does it print any diagnostic output?
OK. Now I have 3 machines that are setup identically. The vsftpd.conf
files have the following settings:
Listen=YES
#Listen_
El 2012-03-14 a las 12:43 -0700, Gary Roach escribió:
(resending to the list)
> On 01/-10/-28163 11:59 AM, Camaleón wrote:
(...)
>>> On the client
>>>
>>> root@xx1:/etc# ftp xx2
>>> Connected to xx2.home.
>>> 421 Service not available, remote server has closed connection
>>> ftp>
>>
6 matches
Mail list logo
