All releases of IPA
Release Notes: This release corrects compilation when --with-ipa-pthread or --with-ipastat-pthread was specified, corrects access to free memory in ipa when a dynamic rule is deleted, and adds minor optimizations.
Release Notes: The source code was optimized and simplified. New parameters were added. The logic of work was improved.
Release Notes: A race condition with signal handling in ipa was corrected. Output of autorules from parsed configuration file in ipa was corrected. Checks whether used modules support rules were added. Limit and thresholds were added in ipastat.
Release Notes: Time events in ipa.conf for +h, +D, and +W could be incorrectly scheduled (plus one extra hour for +h and plus one extra day for +D and +W); this was corrected. If threshold's tm_from time and tm_updated time are equal and their month day is the last day in a month, then ipa incorrectly calculated previous threshold_time_width value during threshold's initialization.
Release Notes: If, during initialization, a limit has a time of START, REACH, or UPDATED event greater than the current time, then ipa will not restart such a limit immediately. If, during initialization, an unreached limit has a time of START event greater than the current time, then ipa will change the time of this event to the current time and will not restart such a limit immediately.
Release Notes: When time went back or changed too quickly, IPA incorrectly used too much CPU time and generated a lot of log messages. This has been fixed Now several databases can be written in db_list parameter's value in ipa.conf.
Release Notes: One file descriptor leak was fixed. Several bugs with limits implementation were fixed.
Release Notes: IPA can now be used on Cygwin (previously, it only could be built on this system). The closefrom system call is used if the system supports it. During startup, ipa can unlink a locked PID file which was locked by another ipa process.
Release Notes: The following bugs were corrected: if a value in the command line for ipactl is given in time units, then ipactl ignored overflow during parsing; if limits and thresholds were disabled during compilation, then ipactl did not accept the -r option; the "limit" section in ipastat.conf placed in an incorrect place could cause a segmentation fault.
Release Notes: Several minor bugs were corrected. The most serious of these was that if a positive counter of some rule was overflowed, then statistics for this rule were incorrectly updated in databases.
