🚀 go-pugleaf

Simon Child <simon@child.demon.co.uk> wrote ......... 
<snip>              
> Didn't work for me - I got the same as I said before. However 
> the man page gave me an idea, and it worked.

> Open two consoles, in one run top and in the other ftp localhost. 
> Spot the pid of in.ftpd and do

> strace -p[pid of in.ftpd] -o/tmp/tracelog

> I got error messages similar to before but a log was recorded and 
> I was able to log in, cd /pub/incoming, download a file, and 
> then attempt an upload of a file called dbin. Same error message 
> as before, and the (apparently) relevant part of the log from 
> strace showed as below. Does it make any sense to you? 
<snip>              

Congratulations on getting  a trace  :-)     
.. unfortunately I couldnt  make anything positive of it  :-( 

.. the connect statements eg ...
connect(-1073764696, {...}, 1075031232) = 14
dont match man pages or any doc I have for it .. first arg is an fd 
and return val - 0 is ok and -1 , with errno set if error , and neither
seem good... so maybe indicates mismatch between strace and the 
library (or my docs)...             
Also dont know what it is attempting to connect to ... but probably  
doesnt matter for this problem .            

However, I would have expected to see some access to the dir 
with either a write failure or a stat on the dir ... there is 
only one such ...
> lstat(".", {st_mode=0, st_size=0, ...}) = 0


spent some time cogitating (read- scratching my head) and couldnt
make anything of this except that probably the stat on the dir
seemed to be the only possible cause ....
Anyway tried your strace technique on my system and works fine 
and can see it stat'ing the dirs ... found I had the same symptom. 
After muchos b*ggering around it seems that the problem is the 
ftpaccess line ..                 
upload  /home/ftp  *             no
if change that to                       
upload  /home/ftp   /             no
and rely on the 
upload  /home/ftp   /bin          no
upload  /home/ftp   /etc          no
to stop unwanted uploads there, then it does upload into the 
pub/incoming dir ....                       

Hope that fixes it,
Cheers,
Steve Houseman 

-- 
                          
currently  steve.houseman at virgin net