helix

Sure, but have you looked at the price/performance/watt ratio? Macs cost significantly more than x86 or ARM mini PCs and SBCs. And lots of the performance is gobbled up by MacOS itself. It’s not like it’s easy to install headless Asahi Linux and have everything working well.

If you buy a used M1/M2/M3 Mac that might be a good investment to use with Asahi Linux but Thunderbolt and other neat features won’t work.

Regular ARM CPUs are pretty efficient. What do you mean?

Maybe we are going to see “scanner” websites for such patch situations in the future, with a world map and statistics where are how many unpatched servers…

You mean things that already exist, like shodan.io?

Netdata, looking at dashboards when something breaks :)

Maayyyyybe because he is?

I mean, if far-left radicals call someone a fascist, that’s debatable. But everyone left of center? Maaaaaybe they’re onto something here?

Did you mean ricing?

You mean 5W?

What do you use as reverse proxy? I have been trying to get a safe reverse proxy going via traefik in --user mode but it’s been rough 😄

but without the command

Yeah, but that’s an easy one to parse, if you really need it.

I’m pretty sure if you use OnCalendar it will still be there after a reboot. Let me check.

If you inspect the generated timer you see the same format in the OnCalendar line.

What do you mean by persisted? The service and timer will both be there as long as the timer doesn’t end. Which it won’t in my example.

If you want to copy it for later reference, you can simply copy the files.

windows, yes: learn.microsoft.com/windows/wsl/systemd

for Mac you should probably use macOS’s launchd services: www.launchd.info

single line

here’s a single line for you which creates a one-shot service+timer in one go, suspending the system in 4 hours:

systemd-run --on-active=4h --unit=poweroff-after-4h /usr/bin/systemctl suspend

If you want it to run repeatedly, simply replace –on-active with –on-calendar=“*-*-* 04:00:00” for example.

But why does it need a cross platform package when systemd is available everywhere? What UX is better than the already existing cockpit?

Yes but… Systemd timers are INI-defined tasks and services with unified history and logs, the alerts can be easily added with any alerting system.

Looks good, but kind of superfluous if you just use systemd timers, lol

Systemd timers are the modern way of doing it which gives you everything you coded this tool for, logs and whatnot, in the journal.

And you can run them in a web UI like cockpit aswell.

This might be interesting in a business setting but lacks ACLs and user management in general.

It’s probably also quite easy to hack the system with it if you can inject some malicious scripts.

I mean, you’re not doing huge batches. If my life depended on meds I’d be damned if I didn’t learn how to cook them myself or with the help of my PhD friends 😄

Can you get equipment and recipes to synthesise these meds yourself or have someone do it? Befriend some pharmacists and pharma PhDs?

If you want a conduwuit sucessor, I’d choose the continuwuity project over tuwunel.

You realise that sounds insane, right?

I recently shut down my server because it’s a high traffic, high risk software. You should have an eye on it, I’d say at least half an hour every week…