Handle systemd timers about fancy-motd HOT 5 CLOSED

@rhoriguchi Take a look at this: #10. I think it should work just fine if you specify a timer in your config like in the example above.

from fancy-motd.

Merged! Happy using and thanks for help.

from fancy-motd.

I think the most intuitive solution would be to just not append the .service and allow specifying any unit names. systemctl show -p ActiveState --value {unit} actually resolves to {unit}.service by default which is the same behavior like when using e.g. systemctl status {unit}. It also works correctly for other unit types like {unit}.timer or {unit}.socket.

We would only have to come up with different way than systemctl list-unit-files to check whether the unit exists at all.

from fancy-motd.

I think the most intuitive solution would be to just not append the .service and allow specifying any unit names. systemctl show -p ActiveState --value {unit} actually resolves to {unit}.service by default which is the same behavior like when using e.g. systemctl status {unit}. It also works correctly for other unit types like {unit}.timer or {unit}.socket.

We would only have to come up with different way than systemctl list-unit-files to check whether the unit exists at all.

Sadly that does not work, probably some if with some ands. I'll try to work on something this weekend.

from fancy-motd.

Sorry if I wasn't clear enough, I just meant that if we don't append .service then you could put this in config:

services["duckdns.timer"]="Duck DNS"

from fancy-motd.