Obsolete Service/jabber: Difference between revisions
No edit summary |
|||
| Line 23: | Line 23: | ||
{| class="wikitable" | {| class="wikitable" | ||
|- | |- | ||
!scope="row" | | !scope="row" | Daemon | ||
| | |{{Code|ejabberd}} | ||
|- | |- | ||
!scope="row" | Logs | !scope="row" | Logs | ||
|{{Code|/var/log/ejabberd}} | |{{Code|/var/log/ejabberd}} | ||
|- | |- | ||
!scope="row" | | !scope="row" | Ports | ||
|{{Code| | |{{Code|5222}} {{Code|5280}} | ||
|- | |- | ||
|} | |} | ||
Revision as of 07: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
Regular updates from native packages.