Support for systemd

[conqp]

Hello folks,

I shortly moved my own minecraft server manager project (minectl) to sourceforge: http://sourceforge.net/p/minectl/code
On the way to publicizing it, I stumbled over the msm project, which I find quite interesting and is somewhat more extensive than mine.
Unfortunately it does not seem to support systemd yet, which I use on my Fedora-powered game server. Maybe you consider adding that.
Feel free to have a look at the code maybe you find some ideas useful and want to add it to msm.

Best regards,

Richard

[IronTetsubo]

I've been poking at this a bit, as a part of adding fedora support. It ends up swapping around functionality a bit, in that at it's heart, msm is the init script, so it needs to exist even on non sysvinit systems. Accordingly, thoughts about changing the installer to install to /usr/local/bin/msm, and then link back to /etc/init.d (or whatever's appropriate for that system)? Current defaults are the reverse. Also, see issue #197 for more general installer discussion.

[FSMaxB]

If you want to use systemd, a service unit is provided in the "init" directory of the repository. Just copy "msm.service" to "/etc/systemd/system/" and make sure that the msm init script is available as "/usr/local/bin/msm" either by creating a symlink (automatically done by installer and described on the page about installation) or by simply installting the init script to "/usr/local/bin/msm" (the second method might break the automatic update functionality).

Adittionaly to doing the service unit, I also did an arch linux install script which, however, installs the msm init script to "/etc/init.d/msm" and only symlinks to "/usr/loca/bin/msm" because in order to not install it into init.d I would have had to rewrite most of the common installation functions what I didn't want to do because I'm not that familiar with them and didn't want to break them (also the init scripts update functionalitiy is installing stuff to /etc/init.d so I would have had to mess with it, too)!

[DarkSpir]

No, msm.service should not go to /etc/systemd/system/ but to /usr/local/lib/systemd/system/. Reason is: If you change properties using systemctl set-properties they will go as a configuration snippet to /etc/systemd/system/ and this will fail if there's already a msm.service file present. One thing you have to keep in mind: /usr/local/ has to be part of the root partition, otherwise systemd won't be able to see this during system startup. There are distributions (like openSUSE when you install it with their btrfs layout) that puts /usr/local on a separate subvolume so you should check mount and change this if necessary.

[conqp]

After nine years I am no longer using msm (and neither Fedora). So I'll take the liberty of closing this one.