ioFTPD v6.1.0 Beta Released - Page 5

pointBreak · 05-09-2007, 11:37 AM

6.1.4

Code:

Unhandled exception 3221225477 at address 0x20b0b9c8 (0x00000000)
0x00000001 0x00000008

PSA9 · 05-09-2007, 10:34 PM

is it just me or does ioFTPD still dont let u rename CAPS!

[edited]

Ft i want to change to ft but it doesn't seem to work!
that was something uploaded back on the ioFTPD 5.
would i have to redo it due to the ioFTPD small file?

Yil · 05-10-2007, 12:24 AM

PSA9: Yup, it's in the suggestion thread. I didn't know about the problem till like yesterday when someone brought it up there. Definitely annoying and on the todo soon list... There are a few suggestions of mine on workarounds until the next release.

I can't fix stuff nobody complains about, so keep em coming because I'd be annoyed when I found this problem on my own at some point in the future...

l.d.m · 05-10-2007, 01:27 PM

Windows Server 2003, clean install, ioFTPD6.1.4, nxTools1.0.5 + ioSFV v2.0beta1.55

seems to crash when more than one user is downloading:

Code:

Unhandled exception 3221225477 at address 0x7c83248b (0x00000000)
0x00000000 0x00000001

Yil · 05-11-2007, 02:48 AM

I "fixed" the rename issue when renaming a file that just differs in case of letters. However, when testing it I ran into several other issues I think need addressing.

1) When you rename a file/dir (even just by case) it will try to move the file to the last filesystem listed in a merged/raided directory. I've already identified the place to add logic to attempt to preserve the filesystem a file is on to prevent this behavior. It's a bit trickier since moving a directory across mountpoints or something should try to keep the files local as well and that's more of a move than a rename...

2) I specifically disallow renaming of mount points. Whatever is listed in the VFS is how you should see things. You can still move/rename the target of a mountpoint if it's visible somewhere else in the VFS which will break the association if you do it, but I think that's OK.

3) The code to determine which filesystem to move a file to in #1 is probably the place to add logic to test for free space issues I've added to the wishlist. Why try to move a directory to a filesystem that doesn't have room for it when another raided one does? Right now it will test for the space before the move, but not proceed to the next filesystem and test again.

To really fix the problem the correct place to make some changes looks to be in the path resolver and changing that might have issues... Therefore I'm going to not release a quick fix for this and try to solve it right later on in a 6.2 release.

P.S. The test for a stale cache entry is case insensitive and renaming a file doesn't update the file's timestamp. Therefore my suggestion of using a script to do the rename won't work. You'll need to rename test to testA to Test to force the update which sucks on non-leaf directories since the odds of someone else being in it go up which will prevent the rename from working...

Flow · 05-13-2007, 09:27 AM

Hi Yil!
Tweak, Optimize .dll and .exe and make a -stable 6.1.5 rel for now?

Zer0Racer · 05-15-2007, 10:20 AM

Quote:

Originally Posted by l.d.m

Windows Server 2003, clean install, ioFTPD6.1.4, nxTools1.0.5 + ioSFV v2.0beta1.55

seems to crash when more than one user is downloading:

Code:

Unhandled exception 3221225477 at address 0x7c83248b (0x00000000)
0x00000000 0x00000001

0x7 suggests that the problem is a script. ioSFV is updated to work with io6. So my guess is that the problem is something in nxTools. Does io still crash if you disable nxTools?

/ZR

hellord · 05-17-2007, 10:28 AM

disabled all scripts, still crash.
ioFTPD 6.1.4 , windows 2003 enterpise edition.

Code:

Unhandled exception 3221225477 at address 0x0041bc53 (0x00000000) 0x00000000 0x01c76bc7

Yil · 05-17-2007, 02:34 PM

hellord: I'll look into that crash. The 0x004... address is inside ioFTPD itself and without any scripts means something is indeed going wrong.

Flow · 05-26-2007, 03:13 AM

Hi Yil! Whare you at?, whats going on ?, Is 6.14 it for now? AND do i haveto use the new ## section ## format?`default = 0 0 0 *

Why i ask?, since some script is still based on the old section format (nxTools-v1.0.5a), which is a GREAT script combined with ioSFV.

Yil · 05-28-2007, 04:34 PM

Flow: Yea, 6.1.4 is what to use currently.

I tried to keep compatibility with existing scripts so you don't have to use the new "share credit" feature for sections. Just like specifying a different <stats section> is optional, you don't have to specify a <share section>. However if you wish to specify a <share section> you will have to specify a <stats section> so just duplicate the <credit section> if you're not doing anything special with it.

Thus: 0 /* , 0 0 /*, and 0 0 0 /* are all the same and if you aren't using the new feature you don't have to change anything at all.

tmgomez · 05-28-2007, 04:35 PM

if you want to test any releases, download and install it yourself, do not offer sites here

tuff

zombies · 05-31-2007, 02:18 AM

I seem to be having problems running v6.1.4 as a service with SSL/TLS. I can login without SSL/TLS just fine and do just about anything on the server but once I turn on SSL in my client, I get AUTH TLS unsupported. I've tried switching to SSL and that's not supported either.

I'm positive I have the SSL certificate installed correctly because it worked fine when I had an older version of ioFTPD installed (5.x). I've tried using the user, group and configuration files from my old setup as well as fresh ones from the new version. Both yield the same result.

I believe it's a problem with the service installer in this version because if I run ioFTPD as a regular executable (not a service) then I can login with SSL/TLS just fine. I've even tried installing the new version as a service using instsrv and I got connection refused (probably because the server didn't even start).

I'm running ioFTPD without any scripts on Windows XP x64.

Yil · 05-31-2007, 10:08 AM

zombies: It's a problem with the cert. When you use the default service installation you are running as "Local Service" which is a special account on all windows machines for services. However, you installed the cert under YOUR user account and thus ioFTPD can't find it. There are 2 solutions:

1) Install the cert under the Local Service account as well, this is the same as installing it for a different user via the site command / .bat file method described somewhere...

2) Change the user the service runs as to yourself (or another real user account and install the cert there). This can be done from services under admin tools in the control panel. I know I talked about how to do this in the ServiceInstall-README file. This is probably the easiest solution and also has the benefit of uploaded files being created with you as the owner instead of the system.

zombies · 05-31-2007, 07:55 PM

I went with option number 2 and it worked just fine. Thanks for the help.

One suggestion would be to have that information listed somewhere in the ServiceInstall-README file. I know the instructions on how to change the user the service runs as were there but the rest wasn't quite as easy as connecting the dots.

Lastly, you've done a fantastic job picking up the development of ioFTPD