Timeline for Prevent systemd timer to run on a metered connection
Current License: CC BY-SA 4.0
7 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Mar 9, 2023 at 7:43 | answer | added | cyqsimon | timeline score: 4 | |
| May 10, 2022 at 10:17 | answer | added | marc.fargas | timeline score: 4 | |
| Jun 10, 2019 at 3:00 | history | tweeted | twitter.com/StackUnix/status/1137917488442871810 | ||
| Nov 21, 2018 at 11:19 | comment | added | don_crissti | Yes, sorry for not being clear, what I meant was that you'd actually need an additional unit like systemd-networkd-wait-online.service and try to do something like this but you still have to use an external tool (like nmcli) to detect whether the connection via certain interface is metered as afaik you cannot do this systemd-only. That's why I said it's not going to be less complicated. | |
| Nov 21, 2018 at 4:21 | comment | added | Gergely Polonkai | I do use a service unit; the timer actually starts a oneshot service. | |
| Nov 20, 2018 at 15:22 | history | edited | filbranden | CC BY-SA 4.0 | format unit file |
| Nov 20, 2018 at 11:31 | history | asked | Gergely Polonkai | CC BY-SA 4.0 |