Very Computer

We have a bunch of Sun SPARCs running Solaris 2.5.  Wu-ftpd 2.4.2b11
is installed on each of them.  There are more SSes coming, so I want to
centralize the system management.  On one machine, I setup the NISkit
1.2, and plan to export user directories from this machine.  To make
sure things, I set aside one machine for testing.

A test account was created for staff (myself, gid 10).  No problems.
FTPing from another machines to the test machine works.  

I then created another test account using a different group (gid =
3000).  After Logging in the test machine from other machines, a dir
or ls always produces the infamous

425 Can't create data socket (0.0.0.0,20): Bad file number.

Changing the gid for this test account from 3000 to 10 (staff), then
both dir and ls worked again!

I did ypcat group, the test group (gid 3000) is in the listing.  So, it
can't be caused by missing gid. I was able to login, so password was
taken from the NIS without doubt.

I would appreciate it very much for some hints why this is so and whether
there is a way to fix the problem.

Thanks,

Chin Fang

I'm also running SPARCs on Solaris 2.5 with Wu-ftpd 2.4.2b11, and *not*
having this problem.  However, I'm also *not* using NIS+.  Have you
posted this to the wu-ftpd%wugate.wustl.edu list?  I know that in
Solaris 2.4 there were NIS+ patches that solved a number of things for
us when we using Solaris 2.4.  Good luck.

                                      Regards,

                                              Michael J. Wolski

           ----  The older I get, the better I was  ----

[my early woe removed]

: I'm also running SPARCs on Solaris 2.5 with Wu-ftpd 2.4.2b11, and *not*
: having this problem.  However, I'm also *not* using NIS+.  Have you
: posted this to the wu-ftpd%wugate.wustl.edu list?  I know that in
: Solaris 2.4 there were NIS+ patches that solved a number of things for
: us when we using Solaris 2.4.  Good luck.

Well, I didn't give up after posting the message.  Hmmm... fighting
with computers is really *ive :)

At least guest group works :)  I had to go to bed around 3:30 AM :(

I will see if it's caused by guestgrop specified in the /etc/ftpaccess
today.  

Thanks for the note!

Regards,

Chin Fang

: At least guest group works :)  I had to go to bed around 3:30 AM :(

: I will see if it's caused by guestgrop specified in the /etc/ftpaccess
: today.  

Well, after some strong coffee, usualy better results came out :-)

The problem was caused by a silly mistake of mine :-(  When I created
a test account in the wu-ftpd's sense of a real user, I accidentally
assigned a gid of guest user (i.e. these with chrooted environ after
login) to the "real" user account.  That messed things up.  I became
suspicious about this possibility after turning off the -a switch
in the /etc/inetd.conf and hupped inetd.  I knew then wu-ftpd wouldn't
check the /etc/ftpaccess file.

I must admit that last night, before the testing, I had some beer  :)

Chin Fang