[RADIATOR] radiator.service/radiator at .service enhancement

[Stefan Paetow]

Patrik, that’s indeed a very useful little enhancement!

:-)

Stefan Paetow
Federated Roaming Technical Specialist

t: +44 (0)1235 822 125
gpg: 0x3FCE5142
xmpp: stefanp at jabber.dev.ja.net
skype: stefan.paetow.janet
In line with government advice, at Jisc we’re now working from home and our offices are currently closed. Read our statement on coronavirus<https://www.jisc.ac.uk/about/corporate/coronavirus-statement>.

jisc.ac.uk

Jisc is a registered charity (number 1149740) and a company limited by guarantee which is registered in England under Company No. 5747339, VAT No. GB 197 0632 86. Jisc’s registered office is: One Castlepark, Tower Hill, Bristol, BS2 0JA. T 0203 697 5800.


From: radiator <radiator-bounces at lists.open.com.au> on behalf of Patrik Forsberg <patrik.forsberg at globalconnect.se>
Date: Friday, 27 August 2021 at 10:39
To: "radiator at lists.open.com.au" <radiator at lists.open.com.au>
Subject: [RADIATOR] radiator.service/radiator at .service enhancement

Hello,
Thought I’d share a small but nice feature enhancement to systemD’s radiator.service/radiator at .service.
Might be an idea to add to the standard distribution 😊

Do systemctl edit radiator.service (and later radiator at .service if you use multi-instance variation)
Add
“
[Service]
ExecReload=kill -HUP $MAINPID
“

You can now do “systemctl reload radiator” or “systemctl reload radiator at instance” when doing configuration changes instead of having to restart Radiator completely 😊

---
Best Regards,
Patrik

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.open.com.au/pipermail/radiator/attachments/20210827/0e550f9a/attachment.html>