View Full Version : nxTools v1.0.2
neoxed
02-23-2006, 01:51 PM
Changes:
NEW: Added text templates for SITE WHO, see the text/Who.* files.
NEW: Option to set the default number of results for SITE DUPE/NEW/etc.
CHG: Updated nxHelper to v2.2.5, initialisation speed improvements.
FIX: ASCII typo in the default Requests.Header template.
FIX: Inconsistencies in the time duration functions.
Download:
http://www.inicom.net/pages/en.ioftpd-scripts.php?id=78
void4ever
02-25-2006, 09:45 PM
This isn't listed on the download page. Newest version on there is still 1.0.1.
neoxed
02-25-2006, 09:54 PM
It's definitely there, take a closer look - the files are ordered strangely (website bug?).
void4ever
02-25-2006, 09:58 PM
Ahhh your absolutly right i'm sorry about that. In the past everything was orderd correctly. Must be a bug. :)
Thanx bro for all the work u put into this script.
Void4ever
nud3l
03-05-2006, 11:29 AM
hello,
i have got the following problem:
systemerror.log
"..\scripts\nxTools\nxDupe.tcl" terminated abnormally
--------------------------- ErrorInfo ----------------------------
database is locked
while executing
"FileDb eval {INSERT INTO DupeFiles(TimeStamp,UserName,GroupName,FileName) VALUES($timeStamp,$user,$group,$fileName)}"
(procedure "UpdateFiles" line 11)
invoked from within
"UpdateFiles $command $virtualPath"
(procedure "UpdateLog" line 9)
invoked from within
"UpdateLog "UPLD" [lindex $argList 3]"
("UPLOAD" arm line 3)
how to solve this ? i am using nxtools 1.0.2.
neoxed
03-05-2006, 02:17 PM
nud3l: I need a bit more information.
Does this happen on every file uploaded, or only once in a while? If it happens on every file, restart ioFTPD and see if the problem persists.
Also what's the hardware like on the box? Lower or higher end CPUs/HDDs?
nud3l
03-05-2006, 04:48 PM
it happens sometimes and when it does, for about 2-3 hours. it is not a highend computer; 1300 mhz cpu and some hdds.
neoxed
03-05-2006, 09:51 PM
When some part of the script crashes earlier, the database will remain locked until ioFTPD is restarted. I need to see the entire log next time it happens (one entry will stand out, to me anyway).
If it happens again, please attach the whole SystemError.log file to an e-mail to neoxed@gmail.com.
vBulletin® v3.8.11 Alpha 3, Copyright ©2000-2024, vBulletin Solutions, Inc.