Hi all,

 

What do people think about replacing some of the koha-* script files with
systemd unit files?

 

I'm creating a service for a RabbitMQ-based task scheduler and my unit file
is 17 declarative configuration lines. Creating a koha-mq-scheduler file
looks like it'll be hundreds of lines of shell script code.

 

My unit file is actually a "template" file, which means I have 1 file in
/etc/systemd/system/koha-mq-scheduler@.service and I can just invoke
"systemctl start koha-mq-scheduler@INSTANCE.service" to start the service.
You can use the %i placeholder in the unit file and it will be replaced with
INSTANCE, so you can set paths, environmental variables, et cetera very
easily. It's so easy and convenient.

 

I think all modern Linux OSes use systemd for their init system, so I think
it would be pretty safe to use. 

 

I'm happy to work on this one, but I guess I'd like to see if other people
have interest in this.

 

David Cook

Systems Librarian

Prosentient Systems

72/330 Wattle St

Ultimo, NSW 2007

Australia

 

Office: 02 9212 0899

Online: 02 8005 0595

 

Attachment: signature.asc
Description: PGP signature

_______________________________________________
Koha-devel mailing list
Koha-devel@lists.koha-community.org
https://lists.koha-community.org/cgi-bin/mailman/listinfo/koha-devel
website : http://www.koha-community.org/
git : http://git.koha-community.org/
bugs : http://bugs.koha-community.org/

Reply via email to