Yes I do check every one of them new ones.
Keep in mind: ASSP provides no way back in versions (only forward). It is
possible that you have to backup and to restore all file and databases to
get a way back!
If you only exchange the assp.pl to go back in versions, the behavior of
assp could be unexpected.
For example with build 12202 the stucture of the SBCache has been
completely changed.
And don't forget to keep your perl modules uptodate!
As any version after 2.2.2(12169) begun producing incredible high load
averages for me
Please could you provide some more details.
In my case - since 2.2.2 build 12208 - the CPU load is reduced, because of
the improved interrupt handling ( and the changed SBCache in 12202 ).
Connection Transfer count/time:
216/0.010
without interrupt:
212/0.010
with interrupt:
4/0.030
interrupt select time:
0.025
interrupt wait time:
0.005
all interrupt related times are reduced by a devisor of 10 in relation to
the previouse versions.
I don't want to bother Thomas with it until I made sure it's not on my
side - and I'm still looking for the cause,
Ok - don't bother me (thank you) - but let the community know what
happens. We saw some module bugs and some design mistakes in the last
months - all of them are fixed or I got a workaround for them.
How should I fix something or find solutions for an issue, if I don't know
what is happen out there?
- use a system with at least 4 cores and 2GB RAM
- use a fast database behind assp (recalculate cores and RAM if you've
installed the DB server and assp at the same system)
- use a fast DNS-server
- keep your perl 5.12 or Perl 5.14 modules uptodate (simply rerun the
latest mod_inst.pl) or use the autoupdate feature of assp
- keep the modules in 'assp/lib' and if used, the plugins uptodate
Thomas
Von:Virag Andras snowfl...@snowflake.hu
An: ASSP development mailing list assp-test@lists.sourceforge.net,
Datum: 14.08.2012 10:25
Betreff:Re: [Assp-test] too old installed dev versions
Hi,
Please do not even think about introducing such retention period.
As any version after 2.2.2(12169) begun producing incredible high load
averages for me (up to stalling the system), I am stuck with that
version right now.
Yes I do check every one of them new ones.
This kind of retention would not be a good thing.
For instance currently I'm pretty sure it's my system (lin/perl 5.14),
which causes the problem,
I don't want to bother Thomas with it until I made sure it's not on my
side - and I'm still looking for the cause,
but I'm pretty busy with other things honestly.
It already happened in the past when I was tagging along for a couple
of versions until a specific issue was fixed.
Andras
On Tue, 14 Aug 2012 09:34:32 +0200, Fritz Borgstedt f...@iworld.de
wrote:
ASSP development mailing list assp-test@lists.sourceforge.net
schrei
bt:
It does not help to test and to improve assp, if the test list users
a
re
not following the development steps.
If you use any of the old versions below, please upgrade to the
latest
development version.
I propose a retention period for developer versions, after nn days it
will warn , after nn+10 it will stop working.
--
Live Security Virtual Conference
Exclusive live event will cover all the ways today's security and
threat landscape has changed and how IT managers can respond.
Discussions
will include endpoint security, mobile security and the latest in
malware
threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/
___
Assp-test mailing list
Assp-test@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/assp-test
--
Live Security Virtual Conference
Exclusive live event will cover all the ways today's security and
threat landscape has changed and how IT managers can respond. Discussions
will include endpoint security, mobile security and the latest in malware
threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/
___
Assp-test mailing list
Assp-test@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/assp-test
DISCLAIMER:
***
This email and any files transmitted with it may be confidential, legally
privileged and protected in law and are intended solely for the use of the
individual to whom it is addressed.
This email was multiple times scanned for viruses. There should be no
known virus in this email!
***
--
Live Security Virtual Conference
Exclusive live event will cover all the ways today's security and
threat landscape has changed
