Can systemd timers be activated after a certain amount of system uptime? [on hold]











up vote
0
down vote

favorite












If I have a systemd timer to run in a recurring interval, is there a way to configure it to activate after a certain amount of system uptime? Rather than just relative to the last time it was run. This would be useful for something like sending a report from the system which depends on how much data the system generated, which depends on how long the system was up.



I'd like any way to tell it to run after every 1 hour of the system being online. So if it runs then the system shuts off 5 minutes later for a day, when the system turns back on it should run next after 55 more minutes.










share|improve this question













put on hold as unclear what you're asking by Thomas, Ouki, grochmal, Wouter Verhelst, X Tian yesterday


Please clarify your specific problem or add additional details to highlight exactly what you need. As it's currently written, it’s hard to tell exactly what you're asking. See the How to Ask page for help clarifying this question. If this question can be reworded to fit the rules in the help center, please edit the question.











  • 2




    Your example and your request are mutually exclusive: It it a typo? as "when the system turns back on it should run next after 55 more minutes" should say "65 minutes" going on your description. Please edit your question and clarify? 0:-)
    – Fabby
    2 days ago

















up vote
0
down vote

favorite












If I have a systemd timer to run in a recurring interval, is there a way to configure it to activate after a certain amount of system uptime? Rather than just relative to the last time it was run. This would be useful for something like sending a report from the system which depends on how much data the system generated, which depends on how long the system was up.



I'd like any way to tell it to run after every 1 hour of the system being online. So if it runs then the system shuts off 5 minutes later for a day, when the system turns back on it should run next after 55 more minutes.










share|improve this question













put on hold as unclear what you're asking by Thomas, Ouki, grochmal, Wouter Verhelst, X Tian yesterday


Please clarify your specific problem or add additional details to highlight exactly what you need. As it's currently written, it’s hard to tell exactly what you're asking. See the How to Ask page for help clarifying this question. If this question can be reworded to fit the rules in the help center, please edit the question.











  • 2




    Your example and your request are mutually exclusive: It it a typo? as "when the system turns back on it should run next after 55 more minutes" should say "65 minutes" going on your description. Please edit your question and clarify? 0:-)
    – Fabby
    2 days ago















up vote
0
down vote

favorite









up vote
0
down vote

favorite











If I have a systemd timer to run in a recurring interval, is there a way to configure it to activate after a certain amount of system uptime? Rather than just relative to the last time it was run. This would be useful for something like sending a report from the system which depends on how much data the system generated, which depends on how long the system was up.



I'd like any way to tell it to run after every 1 hour of the system being online. So if it runs then the system shuts off 5 minutes later for a day, when the system turns back on it should run next after 55 more minutes.










share|improve this question













If I have a systemd timer to run in a recurring interval, is there a way to configure it to activate after a certain amount of system uptime? Rather than just relative to the last time it was run. This would be useful for something like sending a report from the system which depends on how much data the system generated, which depends on how long the system was up.



I'd like any way to tell it to run after every 1 hour of the system being online. So if it runs then the system shuts off 5 minutes later for a day, when the system turns back on it should run next after 55 more minutes.







systemd cron systemd-timer






share|improve this question













share|improve this question











share|improve this question




share|improve this question










asked 2 days ago









user779159

22229




22229




put on hold as unclear what you're asking by Thomas, Ouki, grochmal, Wouter Verhelst, X Tian yesterday


Please clarify your specific problem or add additional details to highlight exactly what you need. As it's currently written, it’s hard to tell exactly what you're asking. See the How to Ask page for help clarifying this question. If this question can be reworded to fit the rules in the help center, please edit the question.






put on hold as unclear what you're asking by Thomas, Ouki, grochmal, Wouter Verhelst, X Tian yesterday


Please clarify your specific problem or add additional details to highlight exactly what you need. As it's currently written, it’s hard to tell exactly what you're asking. See the How to Ask page for help clarifying this question. If this question can be reworded to fit the rules in the help center, please edit the question.










  • 2




    Your example and your request are mutually exclusive: It it a typo? as "when the system turns back on it should run next after 55 more minutes" should say "65 minutes" going on your description. Please edit your question and clarify? 0:-)
    – Fabby
    2 days ago
















  • 2




    Your example and your request are mutually exclusive: It it a typo? as "when the system turns back on it should run next after 55 more minutes" should say "65 minutes" going on your description. Please edit your question and clarify? 0:-)
    – Fabby
    2 days ago










2




2




Your example and your request are mutually exclusive: It it a typo? as "when the system turns back on it should run next after 55 more minutes" should say "65 minutes" going on your description. Please edit your question and clarify? 0:-)
– Fabby
2 days ago






Your example and your request are mutually exclusive: It it a typo? as "when the system turns back on it should run next after 55 more minutes" should say "65 minutes" going on your description. Please edit your question and clarify? 0:-)
– Fabby
2 days ago

















active

oldest

votes






















active

oldest

votes













active

oldest

votes









active

oldest

votes






active

oldest

votes

Popular posts from this blog

Accessing regular linux commands in Huawei's Dopra Linux

Can't connect RFCOMM socket: Host is down

Kernel panic - not syncing: Fatal Exception in Interrupt