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.






systemd cron systemd-timer







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.






systemd cron systemd-timer







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.






systemd cron systemd-timer







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




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

サソリ

Image
この記事は検証可能な参考文献や出典が全く示されていないか、不十分です。 出典を追加して記事の信頼性向上にご協力ください。 （ 2019年1月 ） 「 サソリ 」のその他の用法については「サソリ (曖昧さ回避)」をご覧ください。 「 スコーピオン 」と「 スコルピオン 」はこの項目へ転送されています。その他の用法については「スコーピオン」をご覧ください。 サソリ目 生息年代: 430–0 Ma PreЄ Є O S D C P T J K Pg N シルル紀前期-現世 ダイオウサソリ（ Pandinus Imperator ） 分類 界 : 動物界 Animalia 門 : 節足動物門 Arthropoda 亜門 : 鋏角亜門 Chelicerata 綱 : クモガタ綱 Arachnida 目 : サソリ目 Scorpiones 学名 Scorpiones C. L. Koch, 1837 英名 Scorpion 上科 Pseudochactoidea キョクトウサソリ上科 Buthoidea Chaeriloidea Chactoidea Iuroidea Scorpionoidea サソリ （ サソリ類 、 蠍 、 蝎 、 scorpion ）は、鋏角亜門・クモガタ綱の サソリ目 （ Scorpiones ）に属する節足動物の総称である。体の前端に鋏型の触肢、後端に毒針を有する捕食者である。 1700種以上を含め、最古の化石記録は4億3千万年前のシルル紀まで遡る。有毒生物として広く知られるが、人間の命にかかわる毒を持つものはごく一部の種類に過ぎない。 目次 1 形態 1.1 前体 1.2 後体 1.2.1 中体 1.2.2 終体 2 雌雄 3 生態 3.1 天敵 3.2 生殖 4 分布 5 毒 6 蛍光現象 7 分類
Read more

広島県道265号伴広島線

Image
一般県道 広島県道265号伴広島線 路線延長 km 起点 広島県広島市安佐南区伴東7丁目 終点 広島県広島市中区榎町 接続する 主な道路 （記法） 広島県道38号広島豊平線 広島県道71号広島湯来線 山陽自動車道五日市IC 国道183号（ 国道261号重複） ■テンプレート（■ノート ■使い方） ■PJ道路 広島県道265号伴広島線 （ひろしまけんどう265ごう ともひろしません）は広島県広島市安佐南区から広島県広島市中区を結ぶ一般県道である。 目次 1 路線データ 2 通過する自治体 3 見どころ 4 接続道路 4.1 本線 4.2 旧道 5 別名 6 関連項目 路線データ 本線 起点：広島市安佐南区伴東7丁目・大原下橋南詰交差点（広島県道38号広島豊平線（本線・旧道）交点） 終点：広島市中区榎町・十日市交差点（国道183号（国道261号重用）交点） 総延長： 旧道 起点：広島市安佐南区伴東4丁目・新細坂交差点（広島県道38号広島豊平線交点） 終点：広島市安佐南区伴中央4丁目・寺組橋(南)交差点（広島県道265号伴広島線（本線）交点） 総延長： 通過する自治体 広島県 広島市（安佐南区、佐伯区、西区、中区） 見どころ 広島高速交通広島新交通1号線（アストラムライン） 広島広域公園 広島広域公園陸上競技場（広島ビッグアーチ） 己斐峠 己斐橋（太田川放水路） 天満橋（天満川） 接続道路 本線 広島県道38号広島豊平線（本線・旧道）（広島市安佐南区伴東7丁目・大原下橋南詰交差点〔起点〕） 広島県道71号広島湯来線（本線）（広島市安佐南区伴中央2丁目・伴交番入口交差点 - 広島市安佐南区伴中央4丁目・寺組橋(南)交差点間で重用） 広島県道71号広島湯来線（旧道）（広島県道265号伴広島線（旧道）重用）（広島市安佐南区伴中央4丁目・寺組橋(南)交差点） 広島県道71号広島湯来線（広島市安佐南区伴中央4丁目・寺組橋(南)交差点 - 広島市佐伯区五日市町石内・五月が丘(南)交差点間で重用）
Read more

Accessing regular linux commands in Huawei's Dopra Linux

Image
4 Backstory: I have a Huawei HG8245 router in my house and I want to change the default username/password. I've tried following this guide but the config file always gets reset. My ISP isn't helping either so I'm looking for other ways to accomplish this. The router has telnet access so this seems like a way to change the credentials. The first shell I gain access to looks like this: WAP> Pressing "?" gives me a list of available commands which I've pasted here, the two interesting ones are "su" and "shell". I can't seem to get su access, even after logging in as root (challenge password prompt, and then nothing happens), but shell gives me a proper linux shell. WAP>shell BusyBox v1.18.4 (2017-12-26 17:06:34 CST) built-in shell (ash) Enter 'hel
Read more