-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
I've been trying to upgrade from our working install of 2.1.6
since 2.1.7 came out -- and haven't had any luck.
around .18 I tried on a PC, and while I can't just migrate my
users to the PC, it at least could launch resolver without spiking
the CPU to 100%.
Likewise strace did not show any instance of this:
select(5, [], [4], [4], {5, 0}) = 1 (left {5, 0})
which is all I get on the production server.
Now, I see there have been DB changes (postgres 8.1.4) and I'm
not averse to a dump / load but I want to test that the new binaries
work before I change anything ...
So my first question, is: the only thing hitting the database are
c2s and sm, right? so if resolver can't talk to router, it's not a
DB problem, correct?
Thinking it might be a nuance of the conf.xml files I have run
./configure --prefix=/tmp/jabber and made a second instance, and
configured everything to talk to different ports as specified in
modified-from-.dist files ... but I still can't get it to run on
my slackware (10.2) server.
Any thoughts as to how I can upgrade?
And since I'm writing to you guys anyway, I may as well ask now
about LDAP: can the latest & greatest be configured to pass
authentication off to a windows (active directory) server? If so,
does anybody do that and care to pass along tips?
TIA,
Jad Shipman, Information Technology Specialist
Fort Vancouver Regional Library District
PS: "had change" is incorrect grammar, and bugs me not so slightly
"what changed" would work tho. Err ... yeah, thanks. :-)
-----BEGIN PGP SIGNATURE-----
Version: PGP 8.0.2
iQA/AwUBR2wzqtRPHc/RSQHbEQLmMwCglFmSXLYa8I4dgDjkuVRXuZdOeoMAoJWs
E0zvNDKjERhDfL5ns5mZFSdK
=b3Zj
-----END PGP SIGNATURE-----
_______________________________________________
Jabberd2 mailing list
[email protected]
http://lists.xiaoka.com/listinfo.cgi/jabberd2-xiaoka.com
