Obsolete Service/jabber: Difference between revisions
Appearance
| Line 43: | Line 43: | ||
== Upgrade notes == | == Upgrade notes == | ||
{| class="wikitable" | |||
|- | |||
!scope="row" | yum | |||
|{{Code|ejabberd}} | |||
|- | |||
|} | |||
Revision as of 06:32, 29 April 2011
Hostnames
Hosted on
Administrative contact
jabber AT sugarlabs DOT org
Sysadmins
For non-emergency calls, preferably send email to the administrative contact.
Notes
ejabberd instance default for upstream sugar shell.
| Daemon | ejabberd
|
|---|---|
| Logs | /var/log/ejabberd
|
| Ports | 5222 5280
|
Initial install configuration that was done:
- create admin user
- add Online shared roster group from web ui.
There's a problem with scaling up after more than a few dozens of users have been registered. Thus, ejabberd database is being resetting from daily cron task using /backup/ejabberd-spool.tar.gz initial db.
Upgrade notes
| yum | ejabberd
|
|---|