Use celeryd's /etc/defaults to start processes instead of separate initscripts

Bug #1449493 reported by Caio Begotti
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
Capomastro
Confirmed
Low
Caio Begotti

Bug Description

It was suggested we should use /etc/default/celeryd and /etc/default/celerybeat to start both the worker and the beat processes of Capomastro so we don't have to maintain a single initscript. I'm just filing this bug in case anyone want to work on it, testing it and making sure upgrades will work ok. Personally I don't think it's much worth, really. I fail to see the real point behind it but I know nothing about Celery, so... :-)

Revision history for this message
Zygmunt Krynicki (zyga) wrote :

Probably the most likely advantage is free maintenance that happens in Debian. The systemd transition and script simplification is one more thing I can think of.

Daniel Manrique (roadmr)
Changed in capomastro:
milestone: none → future
importance: Undecided → Low
status: New → Confirmed
Caio Begotti (caio1982)
Changed in capomastro:
assignee: nobody → Caio Begotti (caio1982)
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.