[Koha-devel] Replace some koha-* scripts that use "daemon" with systemd unit files

[dcook at prosentient.com.au]

Unfortunately, I was exaggerating, when I said “task scheduler”. What I really have right now is just a FIFO worker that handles a long-running task for a custom local tool. I want to start small and build up, rather than trying to design something that will meet every use case. 

 

But I have contributed my thoughts to https://bugs.koha-community.org/bugzilla3//show_bug.cgi?id=22417 <https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=22417> .  

 

And actually I would really like to collaborate with you, Tomas, on creating functionality that would make Koha Plugins first class citizens for background tasks, as I think that will actually help us focus on the message queue and task scheduling systems rather than the tasks themselves. 

 

David Cook

Systems Librarian

Prosentient Systems

72/330 Wattle St

Ultimo, NSW 2007

Australia

 

Office: 02 9212 0899

Online: 02 8005 0595

 

From: Tomas Cohen Arazi <tomascohen at gmail.com> 
Sent: Thursday, 4 June 2020 12:44 PM
To: David Cook <dcook at prosentient.com.au>
Cc: Koha Devel <koha-devel at lists.koha-community.org>; Victor Grousset <victor.grousset at biblibre.com>
Subject: Re: [Koha-devel] Replace some koha-* scripts that use "daemon" with systemd unit files

 

Yeah, and contribute that task schedule in the meantime 

 

El mié., 3 de junio de 2020 23:31, <dcook at prosentient.com.au <mailto:dcook at prosentient.com.au> > escribió:

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 at .service <mailto:/etc/systemd/system/koha-mq-scheduler at .service>  and I can just invoke “systemctl start koha-mq-scheduler at INSTANCE.service <mailto:koha-mq-scheduler at 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

 

_______________________________________________
Koha-devel mailing list
Koha-devel at lists.koha-community.org <mailto:Koha-devel at 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/

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.koha-community.org/pipermail/koha-devel/attachments/20200604/df3bbe0f/attachment-0001.htm>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 484 bytes
Desc: not available
URL: <http://lists.koha-community.org/pipermail/koha-devel/attachments/20200604/df3bbe0f/attachment-0001.sig>