Subject: Summary of wu-ftpd installation on a Sparc 5 with Solaris 2.5

From: [email-masked] (Junlei Zhang)
Date: Wed, 17 Apr 1996 10:59:49 -0400

It's been over a week since I started installing wu-ftpd.  Now that it's
completed, I'd like to thank all who kindly offered their knowledge and
help.  I'd also like to share my experiences.  Hopefully, some of the
problems and solutions will come handy for some people some day.

Background information:   System --- Solaris 2.5 on a Sparc 5.

I had already set up the vanilla version of anonymous FTP.  All was working
well.  But we wanted more access and security control.  So I decided to
get wu-ftpd.

==========================================================================
Problem 1:

The first version I downloaded was 2.4.2, "build sol" ran without any problems.
But "build install" brought the following error messages:

# ./build install
make args are : 
make opts are : 
mv -f /usr/local/etc/ftpd /usr/local/etc/ftpd-old
mv: cannot access /usr/local/etc/ftpd
*** Error code 2 (ignored)
Installing binaries.
install -o bin -g bin -m 755 bin/ftpd /usr/local/etc/ftpd
usage: install [options] file [dir1 ...]
*** Error code 2
make: Fatal error: Command failed for target `install'

Solution 1a:

	"The makefile is setup for the "old" (bsd) version of the "install"
	program.  Solaris uses the svr4 version of install that has different
	command line options.  You can edit the Makefile and change the
	install program to use "/usr/ucb/install" and things should work fine.

	INSTALL = /usr/ucb/install" ([email-masked])

This worked.  

Solution 1b:

"I ran into the same thing and had to edit the Makefile to use the correct
form of the install command for Solaris.  The real fix for me was to
compile BETA 10 instead of the official distribution.  (I wanted the new
functionality supported in this unofficial release.)  This release has the
corrected Makefile for install. " ([email-masked])

=============================================================================
Problem 2:

At some point during installation, I started getting the following with
"build sol":

Making support library.
cc -g -DDEBUG   -c fnmatch.c
cc -g -DDEBUG   -c strcasestr.c
cc -g -DDEBUG   -c strsep.c
cc -g -DDEBUG   -c authuser.c
In file included from authuser.c:7:
/usr/include/arpa/inet.h:46: warning: `struct in_addr' declared inside parameter list
/usr/include/arpa/inet.h:46: warning: its scope is only this definition or declaration,
/usr/include/arpa/inet.h:46: warning: which is probably not what you want.
/usr/include/arpa/inet.h:46: warning: parameter has incomplete type
/usr/include/arpa/inet.h:49: warning: parameter has incomplete type
/usr/include/arpa/inet.h:50: warning: parameter has incomplete type
rm -f libsupport.a
ar cq libsupport.a fnmatch.o strcasestr.o strsep.o authuser.o
touch libsupport.a

Solution 2:

"I had the same problem with Solaris 2.4.
I grabbed the latest beta of 2.4.2  and was rid of the problem."

([email-masked])

============================================================================
Problem 3:

I opted for the BETA 10.  Got this message during install:

Making support library.
cc -g -DDEBUG   -c fnmatch.c
cc -g -DDEBUG   -c strcasestr.c
cc -g -DDEBUG   -c strsep.c
cc -g -DDEBUG   -c authuser.c
In file included from authuser.c:13:
/usr/include/netdb.h:203: warning: `MAXHOSTNAMELEN' redefined
../src/config.h:35: warning: this is the location of the previous definition
cc -g -DDEBUG   -c vsnprintf.c
rm -f libsupport.a
ar cq libsupport.a fnmatch.o strcasestr.o strsep.o authuser.o vsnprintf.o
touch libsupport.a

Making ftpd.
cc -g -DDEBUG -I.. -I../support -L../support  -c  ftpd.c
In file included from ftpd.c:79:
/usr/include/netdb.h:203: warning: `MAXHOSTNAMELEN' redefined
config.h:35: warning: this is the location of the previous definition
yacc  ftpcmd.y

Solution 3:

"The configuration file for Solaris specified the MAXHOSTNAMELEN before
it was possible to check to see if was defined and this caused there to be
spurious (and benign) error messages to be generated. This has been corrected."
([email-masked] (Stan Barber)

BETA 11 fixed the bug.

=========================================================================
Problem 4:

I found that none of the files or directories specified in the pathnames.h
file were created during the installation.  

Solution 4:

[email-masked] (Stan Barber) confirmed: "Yes, you need to manually create 
these directories. wu-ftpd does not (yet) do this and won't do it in the 
2.4.2 release. That will all come in release 2.5 (yet to be started)."

=========================================================================
Problem 5:

"I compiled the wu-ftpd.  The server is up and running.  But it somehow is not
running on the specifications in the ftpaccess file.  The ckconfig shows that 
the server is pointing to the specified directories and files.  Yet the
passwd-check doesn't check on password, the messages do not get displayed,
the logfile doesn't get created, and the ftpwho doesn't show anything even
when there are users logged in... who knows what else is not working.  The
ls and dir do work, and files can be transferred."

Solution 5:

Make sure the ftp entry in /etc/inetd.conf has the -a switch to point to the
ftpaccess file.

ftp   stream  tcp nowait   root /usr/local/etc/ftpd ftpd -l -a 

([email-masked]),([email-masked])

========================================================================

Problem 6:

Messages specified in the ftpaccess file did not get displayed at login.

Solution 6:

The messages for the anonymous ftp user need to be in the chroot() area.

===========================================================================

Problem 7:

Real users got kicked off when loggin in when class entry in my ftpaccess
file look like:

class	local		real		*.domainname
class	anonymous	anonymous	*

Solution 7:

Change the local entry to

class	local	real	*

I don't think this is the right solution, but it's the only way I can enable
real user login.

===========================================================================

Problem 8:

The xferlog didn't get created and ftp traffic didn't get logged.

This turned out to be a careless mistake I made in the ftpaccess file.
I missed the final s in "log transfers".

======================================================================

At this moment, the new ftp daemon is running well.  Again, many thanks
from the bottom of my heart.

      #=======================================================#
      #                                                       # 
      #                    Junlei Zhang                       # 
      #        Electronic Records and Network Services        #
      #  New York State Archives and Records Administration   #
      #            Email: [email-masked]              #
      #                                                       #
      #=======================================================#