| Commit message (Collapse) | Author | Age | Files | Lines |
|---|
| |
|
|
|
| |
Now that "ejabberdctl reload_config" works the way most admins would
expect, expose the command via systemd.
|
| |
|
|
|
|
|
|
|
|
| |
Make sure the "ExecStop" command line blocks until ejabberd is actually
stopped. This prevents systemd from killing the ejabberd process(es)
immediately.
Also, let the "ExecStart" command line block until ejabberd's startup is
completed. This makes sure that services which depend on ejabberd
aren't started up too early.
|
| |
|
|
| |
16,000 file descriptors will only suffice for small setups.
|
| |
|
|
|
|
| |
The "reload_config" command doesn't work the way admins would typically
expect, so it shouldn't be exposed via systemd. Those who understand
the behavior can execute the command using ejabberdctl.
|
| |
|
|
|
| |
The "RestartSec=5" setting has no effect if "Restart" is not also
specified.
|
| |
|
|
| |
ejabberd is not a "oneshot" process.
|
| |
|
|
|
|
| |
The "NoNewPrivileges" setting breaks some PAM and extauth setups.
Fixes #1281.
|
| |
|
|
|
|
|
|
|
| |
Admins might expect ejabberd to be able to access data below /home or
/tmp. For example, they might use those locations to dump/restore
Mnesia backups, or as a document root for mod_http_fileserver or
mod_http_upload.
Fixes #1297.
|
| |
|
| |
Restrict capabilities, have a private tmp directory, private /dev, and don't accessing file system locations that really shouldn't be accessed.
|
| | |
|
| |
|
