On Mon, Dec 06, 2010 at 12:47:22AM -0500, Ricky Zhou wrote: > On 2010-12-05 11:16:23 PM, Jeffrey Ollie wrote: > > Either Ejabberd or Jabberd2 are pretty easy to set up, at least in a > > standalone single-node mode. > For what it's worth, I'm running an ejabberd, and have a trivial > puppet module for it. For writing a notification service using jabber, > it's probably easier to just develop on an existing server and only put > up our own when it's moved onto infrastructure. I recently decided against using ejabberd, because it opens two TCP ports for erlang management purposes which afaik cannot be switched of. One is usually static but the other one is random. Upstream (erlang) knows about this and does not care. :-/ How did you work around this? Regards Till
Attachment:
pgpSnG1d7koSG.pgp
Description: PGP signature
_______________________________________________ infrastructure mailing list infrastructure@xxxxxxxxxxxxxxxxxxxxxxx https://admin.fedoraproject.org/mailman/listinfo/infrastructure
