o1bigtenor via Dng said on Sun, 18 Jul 2021 06:17:02 -0500

>Greetings
>
>I have, at least temporarily, abandoned installing 'Evergreen' - -
>library software.
>
>Far too many books around here never mind a huge collection of papers
>most often pdfs.
>
>The Evergreen 'system' uses ejabberd as a communication tool and it
>would seem to me (new at digging under the hood as it were) that
>ejabberd is quite intertwined into this system.
>
>Ejabberd was installed as part of the install but then in the setup
>it is necessary to shut it off.
>The install workflow used 'systemctl' etc etc as a control
>I used 'service ejabberd stop' which worked but when I wanted to
>restart the service the complaints started.
>
>Is there a simple way to change this reliance on systemd or is this
>something better left to someone who does know what they're doing (not
>me - - - grin!)?

I don't understand the problem, and additionally, in certain respects
I'm a "hammer is my one tool" type of guy, so to me everything looks
like a nail. With those provisos, I have a suggestion:

Use runit to control ejabberd. sv up ejabberd or sv down ejabberd or sv
status ejabberd, etc. If you don't want to switch init systems just
now, which would be completely understandable, you can put a respawn
command for runsvdir (the runit supervisor program) in /etc/inittab,
and then just add the ejabberd daemon to runit and disable the ejabberd
daemon in sysvinit. Anyway...

Now this could be slick. Create a shellscript called systemctl on your
path. Your systemctl shellscript would parse its systemd-specific
arguments and output them as sv commands for runit. I have a feeling
all your ejabberd "systemctl" problems would instantly vanish. And as
you're writing the shellscript, visualize what you're doing as kicking
Poettering, FreeDesktop.org and Redhat right in the petunias.

SteveT

Steve Litt
Spring 2021 featured book: Troubleshooting Techniques of the Successful
Technologist http://www.troubleshooters.com/techniques