Recent posts

Pipeline output looked sorted except where it obviously wasn't. Took me a while to narrow down. >>> nan = float('nan') >>> sorted([3, nan, 1, 2]) [3, nan, 1, 2] All comparisons with NaN return False, …

bump

Added, thanks. Line count check still on the list.

unbound-checkconf on the generated file before the reload would catch the worst of it.

On points perhaps. My timers are still running.

I'll take it. Thread closed, I win.

OnFailure= pointing to a unit that sends a mail. You have to write that unit. I'll give you that one, cron wins on this.

Fine. One real point: cron mails me on failure and it's built in. What do you do with a timer?

need last errors first. file is like 3gb. readlines runs out of memory

Mostly so I remember what I did. Someone might also want it. - fetch.sh pulls three hosts lists, strips comments, dedupes with sort -u - writes /etc/unbound/blocklist.conf as local-zone lines - runs n…

user timers need loginctl enable-linger or they stop when you log out. that one cost me a week of missing backups

Cron's environment has caught me more than anything else on this list. PATH with nothing in it, wrong cwd. A service unit can have the same issue but at least you can test it with systemctl start and …

The log file can.

For the record here's what the whole thing actually is: # backup.service [Service] Type=oneshot ExecStart=/usr/local/bin/backup.sh # backup.timer [Timer] OnCalendar=--* 02:15:00 Persistent=true Random…

Nice. Post the numbers after a month on the battery, I'd like to see how close it gets to the sum.

GOT IT. 14uA with the 1M divider and DHT on a GPIO!!! kris you are a legend. Marking this solved. Burden voltage was also real, it kept resetting until I shorted the meter during wake.

Timers still need a service file, a timer file and a daemon-reload to do what one line did. I'm with sysv. Grudgingly, since I don't agree with him about anything else.

No. I found out about flock when four rsyncs were running at once.

And you remember it every time? Honest question.

flock -n /tmp/x.lock cmd. Eleven characters plus a filename.

The other one for me is overlap. A timer won't start the service again while it's still running. With cron a slow job stacks up unless you remember to wrap it in flock.

So install anacron.

I had the same view until a sensor box was off for a night and missed its backup. Persistent=true runs the missed job at next boot. With cron you need anacron for that.

Every six months somebody tells me to move my jobs to timers. So: two files instead of one line, and a unit name I now have to think of, so that I can read the output through journalctl instead of a p…

nils, we all have that guestbook.