[wplug] GAWP 2 aka hdicafs

[Elwin Green]

THE GREAT AMERICAN WEBSERVER PROJECT, PART 2. (aka,
"How do I configure an ftp server?") 

Now that my fabulous LBox is flawlessly serving up my
slightly modified version of Debian's placeholder
webpage, I'm back to the question of how to allow
myself and a select few others (not everyone in the
world) to upload content to the sucker. Someone
mentioned ssh, but I'm not sure if my merry band and I
will always have access to ssh-enabled machines when
the mood/muse/irresistable urge to create strikes us.
ftp, on the other hand, is pretty much everywhere. So
I am still inclined to favor that option.

At least 3 different programs were mentioned before:
anonftp, proftpd, and muddleftp (I think I'm getting
those right). However, at this point I would rather
use Debian's standard built-in ftp server if I can.
I'm trying to keep this as simple as possible, if only
to minimize opportunities for confusion.

Confusion has found its way in, anyhow.

My O'Reilly text has slightly less than 2 pages to
setting up an ftp server. It says: "Selecting the
Basic profile during Debian GNU/Linux installation
causes installation of a standard FTP server."

I'm preeettty sure that option was not selected for
this install.

The book suggests testing the server, then says: "If
your FTP server fails to respond properly, check the
line you added to the inetd.conf file."

(The book doesn't say what the added line should look
like.) 

The server did fail, I checked inetd.conf, and saw
that it contained no entry at all for ftp. I scrounged
debian.org and found a sample inetd.conf with this
line:

ftp  stream  tcp  nowait  root  /usr/sbin/tcpd 
/usr/sbin/in.ftpd

I added that to my inetd.conf (after copying
inetd.conf to inetd.default in case I was screwing
up).

I rebooted.

Now when I test ftp with this:

ftp> open 127.0.0.1

I get this:

421 Service not available, remote server has closed
connection

This time, I actually believe that I know what the
problem is. But I don't know how to solve it.

I think this is the problem: There's no in.ftpd in
/usr/sbin. tcpd is there, but not in.ftpd.

The evident solution is to put it there; but I don't
know how (I also don't know what it *is*, but that's a
different matter).

Help??

Coming real close to having fun now (I hope!),
Elwin










--- Matthew Danish <mdanish at andrew.cmu.edu> wrote:
> On Tue, Apr 29, 2003 at 06:55:49PM -0700, Elwin
> Green wrote:
> > Okay, I finally got apache installed on my
> > webserver-to-be: inserted appropriate info for
> > DocumentRoot, ServerAdmin, ServerName. Switched to
> a
> > working server and printed out access.conf,
> cron.conf,
> > httpd.conf and srm.conf so that I could have
> something
> > to compare the new server's configuration to. All
> four
> > files look right. And when I rebooted, this
> message
> > came up just before the login prompt:
> > 
> > /usr/sbin/apachectl start: httpd could not be
> started
> > 
> > That's all. No clue about *why* it could not be
> > started.
> 
> See /var/log/apache/, particularly error.log.
> 
> -- 
> ; Matthew Danish <mdanish at andrew.cmu.edu>
> ; OpenPGP public key: C24B6010 on keyring.debian.org
> ; Signed or encrypted mail welcome.
> ; "There is no dark side of the moon really; matter
> of fact, it's all dark."
> _______________________________________________
> wplug mailing list
> wplug at wplug.org
> http://www.wplug.org/mailman/listinfo/wplug



__________________________________
Do you Yahoo!?
The New Yahoo! Search - Faster. Easier. Bingo.
http://search.yahoo.com