[Fixed] RaidenFTPD <=> ioFTPD - Page 2

[mRg] · 11-09-2003, 12:08 PM

Hi there,

Just to add a little note to this problem .. I have tried raising this issue on the RaidenFTPD forum only to find that..

a> the word IOFTPD is replaced with [censored] in a very childish manner.

b> after about 2 hours the post was completely deleted with no word about why but probably to hide this problem (I only hope some people read the post before it was removed)

I have really liked and recommended Raiden over the years (It was one of the only pieces of software that I have actually ever paid for) and I had a bunch of very personalised Perl scripts which i lovingly crafted over many months.

This sheer childishness and inablity to admit this problem (and a few other problems I have had in the past) has meant that you guys will be receiving some money from me very shortly and I will have to find a way to convert these scripts over to IO

They have sucessfully driven away a loyal customer.

Please excuse the ranting .. I just hope that IO will be my new choice for windows FTPD software from here on in

Regards

[mRg]

(any links for tutorials on script writting for IO are very welcome !)

Superblue · 11-12-2003, 03:14 PM

Dark: Would it be possible to have a raiden compatility mode where socket close would not be waited for, or to give us a way to adjust socket close timeout to make things more efficient?

As for me I have built a new box and put glftpd on it to use for my ftp site (tranfer speeds are 2+ times faster on this 700mhz linux box than my 2.5ghz p4 but hey whatever.) I am still using ioftpd on my comp for a personal server to transfer stuff back and forth from my home PC though. I just hate to see so many people turn away from what looks to be a very promising solution over such a small problem.

Mouton · 11-13-2003, 12:02 PM

Breaking standars to be able to work with ftpd that doesn't follow standards isn't really a good idea.

Doing thing the right way is a good idea.

Mr_X · 11-13-2003, 12:36 PM

I have an idea: why don't send a command before fxping between a raiden and a io? User have to send a command to say that is raiden and it has to use the "bad" method to close thread. What do you think of that?

Harm · 11-13-2003, 12:41 PM

You want to create a whole new standard to support only one ftpd that doesn't follow them ?

Mr_X · 11-13-2003, 12:52 PM

no, just have an alternate routine when fxping between raiden and io (If the user send the command to specify that he is fxping from/to a raiden and that io have to use alternate method)

neoxed · 11-13-2003, 08:11 PM

Quote:

Originally posted by Mr_X
no, just have an alternate routine when fxping between raiden and io (If the user send the command to specify that he is fxping from/to a raiden and that io have to use alternate method)

That would also require a special client.

And RaidenFTPD is _not_ worth the effort.

thewarden · 11-13-2003, 10:38 PM

I went throught this a week or two ago.

*** It's not the fact if RAIDEN is worth the effort or not.

It's the fact that some sites do use Raiden and that is that.

As well as what your own user base uses as a site to site xfer.

The only point here is one item at this time:

Use 1 or the other - but that is not a solution nor fix for SysOps
and not their end users.

---
The only fix is a 3rd name which is compatible with both, and that
name is older than both IO and Raiden and works with both quite
fine...
---

So, sites like mine who were waitng for the BW control, now have
to wait once again until this current nonsense has calmed down
on the part of ftpd's and as well as clients going through some
teething problems on who will end up with the biggest chomp!

There is ALWAYS a way around a problem...until things calm down.

TW

Mouton · 11-13-2003, 10:56 PM

I think you ppl miss the point here.

ioFTPD do things the right way, the way it should do things.
It's optimized to do things right and fast.
Making things any other way than that would make no sense to ioftpd developer (dark).
Dark works very hard to make his server performant and stable.
Changing the way ioftpd works to make it work with a ftpd that doesn't follow ftp/tcp standards makes no sense whatsoever.

Stop asking for it. ioFTPD won't lessen it's performance just to accomodate bad ftpd implementations.

End of story.

wvGrandja · 12-06-2003, 12:24 PM

If i am not mistakaken, in later builds of raiden this problem has been fixed. Here is a quote from raiden forum:

Quote:

Version 2.4 build 999 : fixed: FXP problem with ProFTPD 1.28

when i saw this i got very curious, i stared up a raiden server (pre build 999) and fxp'd to it. The problem occured. Then i updated the raiden server to teh latest build, and the transfers went smooth.

Mouton · 12-07-2003, 12:55 AM

yep, that solved the io to raiden issue.
case closed.