[1003] in BarnOwl Developers
New BarnOwl locker build -- Please Read
daemon@ATHENA.MIT.EDU (Nelson Elhage)
Thu Oct 29 18:12:02 2009
Resent-From: nelhage@mit.edu
Resent-To: barnowl-dev-mtg@charon.mit.edu
X-Original-To: nelhage@nelhage.com
Date: Sun, 23 Mar 2008 19:25:18 -0400
From: Nelson Elhage <nelhage@MIT.EDU>
To: barnowl-users@mit.edu
[SUMMARY: If you're running a locker barnowl, :reload-modules WILL
BREAK JABBER unless you restart]
Hey all,
Tonight asedeno and I pushed new BarnOwl builds to the barnowl locker
on Athena. The new build (r989) is the first locker build with the
select() main loop. This should have two main effects:
* BarnOwl should now use a _lot_ less CPU. Whereas the old barnowl
tended to use a steady 1-4% of CPU on linerva while idle, the new
one should be pretty much 0% in top in steady state.
* select() and non-select() BarnOwl have INCOMPATIBLE Jabber
modules. This means that if you are running an old locker barnowl,
:reload-modules WILL BREAK JABBER until you restart into a new
select() barnowl. We apologize for this inconvenience.
- Nelson
for the Dirty Owl Hackers
