Hi all,
fixed in assp 2.2.2 build 12168:
- it was not possible to define more than one value for 'myNameAlso'
- in some cases a wrong domain name was shown if a black domain was found
- workers were restarted or assp was dieing if the same mail from the same
IP was delivered in two or more
different threads at exactly the same time
changed:
- a new ASSP_MIB file is released
added:
a new hidden config variable is implemented:
$lockDatabases = 1; # (0/1) - locks databases on access in every worker to
prevent access violation
Set this value to zero if you run in to performance problems - because
workers are waiting too long for database answers.
'ConfigChangeSchedule','Schedule Configuration Changes*',
'Use this option to schedule configuration changes. You must use the file
option like 'file:files/configchangeschedule.txt'
to define schedules - an empty value disables this feature.
Define one schedule per line - comments are not allowed in a schedule
definition line!
The line has to start with the schedule string ( see ReStartSchedule )
followed by the variable (or hidden variable )
name to change, followed by ':=', followed by the value to change the
variable to - like:
8 0 * * * myNameAlso:=otherhost1.mydomain.tld
0 6 * * *|0 10 * * * myNameAlso:=otherhost2.mydomain.tld
0 1 * * * debug:=1
0 2 * * * debug:=
The schedule string can contain multiple schedule definitions separated
by pipe'|'. You will get errors if:
- the schedule definiton is wrong
- the variable name is wrong (does not exists)
- the syntax of the value is wrong
Notice - assp will only check the syntax at definition time - the logical
correctness of the value will be checked
at the scheduled time! So, assp will (for example) not check any
dependencies at definition time - if a dependency
is wrong, the change request at the scheduled time will fail!
Notice - all configuration changes are done with 'root' permission! For
this reason, this configuration parameter
is only visable to root and it is stored encrypted!
For advanced users ONLY:
Using the following extension, requires a deep internal knowledge of the
assp code!
It is also possible to schedule a call to an internal assp subroutine.
The name of the subroutine has to begin with a '&',
the parameters that should passed to the subroutine must be in '()' -
like:
0 6 * * * &subname(var1,var2,..,...)
0 7 * * * &subname()
Notice: the subroutine will be called in the MainThread and syntax check
will be done at run time -
possible errors are shown in the log!'
Thomas
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 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
[email protected]
https://lists.sourceforge.net/lists/listinfo/assp-test
