jeza.ioFTPD.Tools

[jeza]

All scripts need MS.NET Framework 4.0 installed!


Zip Script

• Its a Zip Script

Manager
Site manager

• DUPE
• REQUEST
• NEWDAY

Archiever
Archive old releases

• MOVE
• DELETE
• COPY

Version : 4.6.50.621

x64: http://jezatools.googlecode.com/file...50.621_x64.zip
x86: http://jezatools.googlecode.com/file...50.621_x86.zip

[ArtX]

Don't know if this is a bug or a config error, but when ever i issue the site rescan command, it runs, show all the files are fine, yet the final line looks like

[L] 200-{8}TotalFiles...: {4}{8}MissingFiles.: {5}{8}OkFiles......: {6}{8}FailedFiles..: {7}

and the complete tag is not made, I have noticed that there is a .jeza.ioFTPD.Debug file in every dir i have ran rescan on.

I have tried with both x86 and x64 versions

[jeza]

It is a bug.
The line (ClientRescanFoot) was not correct formated.
And the script is not creating COMPLETE TAG at all, only .missing files are created.
I will fix it and post new version.

.jeza.ioFTPD.Debug is created in every folder where the script is used and it contains debug info about the actions that are taken.
It is a plain text file and you can open it with your favorite text editor and check if there is some error at the end...

[ArtX]

so do i get a cookie for reporting a bug?

[jeza]

Originally Posted by Carpo

so do i get a cookie for reporting a bug?

sure you do

x64: http://jezatools.googlecode.com/file...42.594_x64.zip
x86: http://jezatools.googlecode.com/file...42.594_x86.zip

Upgrade instructions:

• Create backup of file jeza.ioFTPD.ZipScript.exe.config
• Replace all *.dll and *.exe files
• In jeza.ioFTPD.ZipScript.exe.config add

    <!-- delete all files that start with this string in rescan folder -->
    <add key="TagCleanUpStringCrc32" value="]-[" />
    <add key="TagIncompleteCrc32" value="]-[iNCOMPLETE]-[ {11}% ]-[{6}FiLE(s) of {4}FiLE(s)]-[iNCOMPLETE]-[" />
    <add key="TagCompleteCrc32" value="]-[Complete]-[{11}%]-[ {9} - {6}F]-[" />

[ArtX]

working here, so far, is there a way to change the tag to a folder and not a file? If not can i add this as a request?

edit: rescan works fine, although something else has cropped up

edit2: for some reason the security on this board wont let me post the out put here, so here it is on pastebin http://pastebin.com/Faw9332C

[jeza]

i always used file as tag, so i never added support for folder
i will do my best to make it configurable file/fodler

try to add a ticket with .jeza.ioFTPD.Debug file as attachment here if the forum does not allow it

[ArtX]

bug filed

[jeza]

it seems that you have more than one sfv in that folder. is this correct?
script checks the number of SFV files in race folder.
if number of SFVs in the folder is not equal to 1, this message is shown to user.

[ArtX]

incorrect, i have no sfv's in that folder, just 55 .missing files an .ioFTPD file, .jeza.ioFTPD.Debug and.jeza.ioFTPD.Race , flash fxp says its transferred it, your script says its there, yet when i look using flashfxp or in windows explorer its not there

I did attempt to re upload it, it said same as before, its there expecting 55 files, I have even deleted the folder and started again, same issue.

I do have a fresh box installing at the moment, so i will try with a fresh install of both your script and ioFTPD, see if that does the trick

[Yil]

This is great. A .NET zipscript. I've been sort of curious about the performance of C# for events. Obviously TCL is not fast, but it has the benefit of an already running interpreter which means that for trivial things it's fast enough, but on something more complex like the archiver it's quite slow (though speed isn't really necessary there).

I haven't spent much time on ioFTPD lately, let alone got to playing with a new C# library, but I did want to point out that I think I've thought up a way to expand on the module idea and allow for user-defined modules to be called the same way TCL/EXEC would be called now. This would enable a relatively simple shim dll who could kick the args to a persistent event-driven application which would eliminate the overhead involved in things like C# which have a prohibitive startup cost. I've wanted something like this way back before I even released v6.0 because I thought the regular EXEC overhead was too high for trivial things but abandoned the idea when things were good enough and TCL scripts were the most common.

The only reason I mention this now is because if you find C# too slow for some things there is a way around that.

[jeza]

i do not really care about performance, but i did some tests...

it takes ~600ms to process OnUploadComplete event

it would be nice to speed up things a little, because if i remember correct same zipscript in c++ completed the OnUploadComplete event in ~30ms

[ArtX]

Originally Posted by jeza

Upgrade instructions:

• In jeza.ioFTPD.ZipScript.exe.config add

    <!-- delete all files that start with this string in rescan folder -->
    <add key="TagCleanUpStringCrc32" value="]-[" />
    <add key="TagIncompleteCrc32" value="]-[iNCOMPLETE]-[ {11}% ]-[{6}FiLE(s) of {4}FiLE(s)]-[iNCOMPLETE]-[" />
    <add key="TagCompleteCrc32" value="]-[Complete]-[{11}%]-[ {9} - {6}F]-[" />

^^^
is what threw me off, in the file you sent me it is different, mine doesn't have Crc32 on the end, i thought I had to replace the lines, but i didn't, still all working fine now, well apart for the folder as tag thing

[jeza]

they are together with other rescan settings

<!--
    Rescan
    -->
    <add key="ClientCrc32Head" value=" Expected Actual   Status   FileName " />
    <add key="ClientCrc32Body" value=" {1,-8} {2,-8} {3,-8} {0,-60:B60}" />
    <add key="ClientCrc32Foot" value="{8}TotalFiles...: {4}{8}MissingFiles.: {5}{8}OkFiles......: {6}{8}FailedFiles..: {7}" />
    <!-- delete all files that start with this string in rescan folder -->
    <add key="TagCleanUpStringCrc32" value="]-[" />
    <add key="TagIncompleteCrc32" value="]-[iNCOMPLETE]-[ {11}% ]-[{6}FiLE(s) of {4}FiLE(s)]-[iNCOMPLETE]-[" />
    <add key="TagCompleteCrc32" value="]-[Complete]-[{11}%]-[ {9} - {6}F]-[" />

[ArtX]

After going back and checking i know what i did wrong now, looked at wrong section, meh, these things happen, now about the folder as tag.......