Skip to main content

systemd run once

I'm building a reporting system that uses systemd timers to schedule the individual reports; each report being a self contained statically linked binary.

At first I discovered the monotonic timers documented in systemd.timer but as I read and reread the man page I realized I was wrong. I had originally thought I could use
However that's just wrong.  The OnCalendar field does not support monotonic timers. The only fields that support this functionality are:
OnActiveSec=, OnBootSec=, OnStartupSec=, OnUnitActiveSec=, OnUnitInactiveSec=
However, each of these have different behavior. For example OnBoot and OnStartup will trigger the timer regardless if the computed time is prior to now. While Boot and Startup will partially solve the problem they are not complete. I'm trying to run a report NOW; Boot and Startup will run it now and after a reboot or restart of systemd.

The other 3 types require that the computed time is in the future. In one testcase I tried "1sec" which should have configured the timer 1 second in the future. The problem here is that by the time systemd reads the file and makes sense of the computed time the time may have already expired and so the report may not run. Several test cases failed and several passed. I cannot quite explain it except that.

There is one other parameter that may play a role in this. Since I'm trying to run the report 1s after the active state... checking the AccuracySec field I see that the default accuracy is set to 1min. Meaning that the timing of the 1s monotonic timer is even more critical. Setting the AccuracySec to 1s might consume considerable resources so that's not a good idea although possible.

Finally, use OnActiveSec means that if I stop/start the timer that the report will run. Meaning it will run after a reboot or restart.

In conclusion, with the exception of setting the exact one-time run based on the wallclock there isn't a way to accomplish a "run now - run exactly once".


Popular posts from this blog

Entry level cost for CoreOS+Tectonic

CoreOS and Tectonic start their pricing at 10 servers. Managed CoreOS starts at $1000 per month for those first 10 servers and Tectonic is $5000 for the same 10 servers. Annualized that is $85K or at least one employee depending on your market. As a single employee company I'd rather hire the employee. Specially since I only have 3 servers.

The pricing is biased toward the largest servers with the largest capacities; my dual core 32GB i5 IntelNuc can never be mistaken for a 96-CPU dual or quad core DELL

If CoreOS does not figure out a different barrier of entry they are going to follow the Borland path to obscurity.

UPDATE 2017-10-30: With gratitude the CoreOS team has provided updated information on their pricing, however, I stand by my conclusion that the effective cost is lower when you deploy monster machines. The cost per node of my 1 CPU Intel NUC is the same as a 96 CPU server when you get beyond 10 nodes. I'll also reiterate that while my pricing notes are not currently…

Agile is still dead and has been since 1991

[updated 2011.09.30] yet another response to Agile is good.
When you have so much of you career invested in something like Agile, XP etc... it can be hard to see the forest for the trees. I had a consulting job in The Haag many years ago. IBM was the incumbent contractor at the customer site (a bank) but after 5 years on the job they had not written a single line of functioning code. In the office there were two teams of software people... both behind closed doors. The first team was the Data team and the second team was Functional. They rarely spoke and they never shared information. I was there for a week, introduced the client to OO and we had a functioning prototype. Smart people do smart things, You cannot make an underachiever exceptional by using Agile. Either they get "it" or they don't.
I just commented on a blog. I'm sure there is some validity to his post beyond observing that Agile Scrum is broken. It certainly is not what it was originally intended but for…

eGalax touch on default Ubuntu 14.04.2 LTS

I have not had success with the touch drivers as yet.  The touch works and evtest also seems to report events, however, I have noticed that the button click is not working and no matter what I do xinput refuses to configure the buttons correctly.  When I downgraded to ubuntu 10.04 LTS everything sort of worked... there must have been something in the kermel as 10.04 was in the 2.6 kernel and 4.04 is in the 3.x branch.

One thing ... all of the documentation pointed to the wrong website or one in Taiwanese. I was finally able to locate the drivers again: (it would have been nice if they provided the install instructions in text rather than PDF)
Please open the document "EETI_eGTouch_Programming_Guide" under the Guide directory, and follow the Guidline to install driver.
download the appropriate versionunzip the fileread the programming manual And from that I'm distilling to the following: execute the answer all of the questio…