ioFTPD v6.6.1 BETA Released

[Yil]

rolan: Next time you notice it having problems issue a "site crashnow" and send me the minidump (PM me if you need the server info). If it doesn't produce a minidump and just hangs there let me know as that's the lockup bug.

[rolan]

hi,Yil, do you receive files?

[Yil]

Rolan: Yup, just haven't had time to look over the logs yet.

[rolan]

okay,thank you.

[o_dog]

Do you think it's possible to go back to tcl8.4 instead of .5?

The problem with nxtools has something to do with the dll it uses to catch freespace. And it seems neoxed is not to overeager to rewrite it. Besides, not that manyt hings were added to .5.

[Yil]

Can you elaborate a bit more on the freespace issue with nxtools? I'm not aware of it. Neoxed did release the source for his extension library so I'm guessing we can fix whatever that issue is. That's probably easier than reverting the TCL version if everything else appears to be working.

[o_dog]

he uses the dll to communicate with windows api (my guess haven't looked at the sorce) to get freespace and other hdd info. dunno if thats the only thing thats broken but i know that one crashes tcl8.5 and thereby ioftpd.

[Flow]

Hey Yil, why you so quiet lately, what you doin now?

Yil, is it possible to allow ioFTPd to start/keepruning a external .exe file (eggdrop.exe -nt) from the [Scheduler] section

Like;
BotChk = 00,15,30,45 * * * EXEC z:\ioFTPD\eggdrop\eggdrop.exe -nt

Why ?, so it bind this;
# the window name, used by third party scripts and services to communicate
# with ioFTPD. the default is fine unless you are running two copies of
# ioFTPD.
WindowName = ioFTPD::MessageWindow

[o_dog]

use something like firedaemon instead. Works better

[Yil]

Flow: There isn't a clean way to keep an exe running all the time. o_dog is right, something like firedaemon or the free MS anysrv(?) can be used to do it. Neither will catch the program locking up like a true service might, but they should work.

Alternatively you can use a .exe or TCL wrapper run via the scheduler on a periodic basis to see if something is running and restart it if necessary. I should probably add on the wishlist a scheduler feature for items scheduled as * * * * to just start at runtime and restart if they fail. The problem with something like that is if the server itself crashed or was brought down and the exe kept running how/when should you stop it? Or should it even be stopped? What about when the server is started again? There isn't one correct answer, but any logic to do that kind of stuff would require a middleman if you want to run an off the shelf thing like eggdrop.

Of course if you have to have a middleman anyway creating the simple app and tieing it to a site command and a periodic scheduler event seems pretty easy and wouldn't require any server changes to do.