jabberd-2.2.1 release

Tomasz Sterna <[email protected]>
Newsgroups gmane.network.jabber.admin
Organization Xiaoka.com
Message-ID <[email protected]>
It's time for next jabberd 2.2 series release.

Get 2.2.1 release as usual at:
http://ftp.xiaoka.com/jabberd2/releases/jabberd-2.2.1.tar.gz
http://ftp.xiaoka.com/jabberd2/releases/jabberd-2.2.1.tar.bz2

and read: http://svn.xiaoka.com/jabberd2/trunk/UPGRADE


This is a big bugfix release.


ChangeLog:
      * Removed jid prep cache and mysql filters cache. These are known
        to grow without restrictions causing memory "leak".
      * Fix in jabber:iq:register example in router-filter.xml
      * Fix in lookup.resolve-ipv6 in s2s.xml handling
      * Fix c2s's byte rate limiting.
      * Make c2s's connection rate limiting and router's byte rate
        limiting work better.
      * Comments and spelling errors fixes
      * Fix a potential memory leak when attempting to read from a
        socket that has been closed.
      * Improve the documentation for <max_fds> in the configuration
        files.
      * Merged MySQL crypt()ed password full implementation. Closes #228
      * Re-use DB query the filter instead of recreating it.
      * Added --without-subst option to disable subst/ library building.
      * Do not bounce s2s error packets
      * Fixed filtered packets error reporting
      * Changed router-filter example, because resource is not matched

For a full ChangeLog see:
http://svn.xiaoka.com/jabberd2/tags/jabberd-2.2.1/ChangeLog


-- 
  /\_./o__ Tomasz Sterna
 (/^/(_^^' http://www.xiaoka.com/
._.(_.)_   im:[email protected]

_______________________________________________
JAdmin mailing list
FAQ: http://www.jabber.org/discussion-lists/jadmin-faq
Forum: http://www.jabberforum.org/forumdisplay.php?f=19
Info: http://mail.jabber.org/mailman/listinfo/jadmin
Unsubscribe: [email protected]
_______________________________________________
lmpx.com only provides a reader for public news (NNTP) servers. It is not affiliated with the servers or forums shown here and is not responsible for the content of articles, which is written by their respective authors.