On Tue Feb 13, 2001 at 05:39:44AM -0900, William Bouterse wrote:
> > Our proftpd package is different from that you get from the proftpd
> > web site. Instead of having the core, inetd, and standalone package,
> > we combined it into one. Your best bet is to backup your
> > /etc/proftpd.conf file, uninstall your currently installed proftpd
> > packages, and then install the package from updates (single package
> > instead of the 2-3 you will have installed now). Then restore your
> > backed up /etc/proftpd.conf and fire it up. You should be good to go
> > then.
>
> Thanks that did the trick!
I thought it might. =)
> A question as a followup however;
> The "standalone" versus the "inetd version" I have
> never been clear about. I was able to enter the
> appropriate line into /etc/inetd.conf to make things work
> right away originally and have always been unclear as to the
> advantages and disadvantages of both methods.?
Low-traffic FTP sites can run from inetd so that the FTP server is a
running process only if someone connects. That saves you a little
overhead, but at the expense of speed. Standalone runs proftpd in
daemon mode so it listens to the port itself. This gives a little
overhead (not much at all), and makes connections much faster. The
only real benefit to using inetd is for tcp_wrappers, but proftpd has
good access control itself so you don't need to use tcp_wrappers like
that.
Personally, I prefer standalone, and that's how I always run it. You
can change proftpd's behaviour in your /etc/proftpd.conf file. I
forget the directive to turn on inetd mode because I've never used it.
--
[EMAIL PROTECTED], OpenPGP key available on www.keyserver.net
1024D/FE6F2AFD 88D8 0D23 8D4B 3407 5BD7 66F9 2043 D0E5 FE6F 2AFD
- Danen Consulting Services www.danen.net, www.freezer-burn.org
- MandrakeSoft, Inc. Security www.linux-mandrake.com
Current Linux kernel 2.4.1-5mdk uptime: 3 days 9 hours 54 minutes.
