subdimension
Dec 17 2003, 11:09 PM
I have my server back up and running smooth(after a total reinstall twice).
But... I noticed those annoying anon ftp'ers hitting my ftp, I went to proftpd.conf and disabled the anon login but then I see they are still there, I double checked and I did it correctly(I use proftp on my home freebsd box so I am quite familiar with it). I noticed that no matter what changes I make to /etc/proftpd.conf nothing changes with proftp, not the login message, not the aliases, nothing. I cannot find another proftpd.conf and I am running proftpd according to my whm and ps -aux
I also disabled anonymous ftp in the whm and thought I had it shut down until I could get around to fooling iwth it again but now I STILL see people anon ftping and I tried it and it is still working. Whm did not disable it like it says it did. I finally killed the proftpd process until I can find out why proftpd.conf is not working.
Anyone have ideas on this? Is there another location that sm has installed a proftpd configuration file?
subdimension
Dec 17 2003, 11:14 PM
I just got a message that proftpd failed and was restarted automagically, that's quite useful 99% of the time so a nice featue. I went back and added ftp to the /etc/ftpusers which has worked but I stil need to edit proftpd configuration settings because I use a lot of aliases instead of accounts.
If anyone has edited their proftpd.conf on a sm system and it worked or not I would like to know.
Thanks
subdimension
Dec 18 2003, 12:23 AM
Duh, its pretty obvious now. On my freebsd system proftpd loads when someone accesses ftp, on the linux9 box proftpd stays loaded in memory. Therefore when I make changes on my local machine proftpd.conf is reloaded everytime, I never have to restart proftpd, but on this linux box I do have to restart proftpd after every proftpd.conf change, that fixed the problem, just a simple service restart, didnt know it stayed alive all the time...Problem solved
Jaime
Dec 18 2003, 08:40 AM
From the ProFTPD documentation:
QUOTE
The ServerType directive configures the server daemon's operating
mode. The type-identifier can be one of two values: inetd The daemon
will expect to be run from the inetd "super server." New connections
are passed from inetd to proftpd and serviced immediately. standalone
The daemon starts and begins listening to the configured port for
incoming connections. New connections result in spawned child
processes dedicated to servicing all requests from the newly connected
client.
I think your home FreeBSD box runs in "inetd" mode and your Linux server runs in "standalone" mode, just like mine.
This is a "lo-fi" version of our main content. To view the full version with more information, formatting and images, please
click here.