-
Notifications
You must be signed in to change notification settings - Fork 1.5k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
No systemd service file in 22.05 rpm package #3816
Comments
The idea was to have the RPM package install the service unit in the proper location. Seems it's missing from the package indeed, I'll look into it. |
You could test this updated package if you like: https://ejabberd.messaging.one/download/package/ejabberd-22.05-2.x86_64.rpm You'd enable and start the systemd service like this:
|
P.S. I just installed ejabberd_22.05-2_amd64.deb and also noticed the ejabberd.service was gone. (I created it manually using the template). |
That would be another, unrelated bug. I wouldn't have expected that, as I tested several installations of the DEB package. Would've expected the systemd service to be auto-started on installation. I'll see whether I can reproduce the problem, but won't be able to test things before Wednesday. |
@weiss perhaps because I had manually created a softlink in /etc/systemd/system (systemd.service -> /opt/ejabberd-21.12/bin/systemd.service). I do not want to cause you to waste your time trying to reproduce it. |
Ah, yes, I guess you just need to remove that softlink, then. To double-check, I've installed ejabberd_22.05-2_amd64.deb on a fresh Debian system and ended up with a I'll close this issue, please open a new one if you still run into problems. |
ejabberd-21.07-0.x86_64.rpm has systemd service file
/opt/ejabberd-21.07/bin/ejabberd.service
, but ejabberd-22.05-1.x86_64.rpm no longer has it. I see it was changed in #3781 and apparently systemd service file is generated byejabberd-2x.xx-1-linux-x64.run
file. It would be nice to have it back in rpm package as well.The text was updated successfully, but these errors were encountered: