Fritz,
Thank you I will try that.
Thomas that was a well detailed email with good information. I am not new
to ASSP.
Again if you re-read my emails I had said this server was running 1.4.3.1
with exactly the same number of connections per day and was running
perfectly fine. I've been using
Masood,
I upgraded to v2 these same
files that are not in a db would cause problems
These files (as Perl - hashes) and many other variables and hashes must be
shared between all threads (13 in your case). This could be done using the
magic Tie with Threads::shared (flat files are used and
ASSP development mailing list assp-test@lists.sourceforge.net
schreibt:
keep in mind V 1.7.x.x will need some more system resources than 1.4
Yes, but it is much faster and even ClamAV is running now quite good
(thanks to Thomas for modifying the module code).
And it is quite nice, that ALL
Yes, but it is much faster and even ClamAV is running now quite good
(thanks to Thomas for modifying the module code).
Yeah, luckily that darn ClamAV issue at end got fixed we had bad
times tracking it and figuring out what was causing it, luckily at end
we found the culprit... just... pity
On 2010-03-13 10:30 AM, K Post wrote:
We'd have
2.0.2 DEV Build 15 which is clearly older than
2.0.2 DEV Build 14 and for the public release
2.0.1 Release 15
Make sense?
Not really... I hate text in version numbers.
Since even are dev versions and odd are release versions, why not just
We use the 8 digit number in our automatic update system. ASSP just
compares the numbers and decides which is higher.
I wonder how it does this, if there is so much difficulties to decide
which is higher or lower.
--
On Mar 13, 2010, at 2:45 PM, Fritz Borgstedt wrote:
We use the 8 digit number in our automatic update system. ASSP just
compares the numbers and decides which is higher.
Systems are very good at this, humans are very poor at this.
Fritz Borgstedt previously wrote:
The version in ASSP
