On Sun, Apr 14, 2019 at 08:02:45PM +0200, Alec Leamas wrote: > No. ddupdate uses systemd --user to setup and run the service without > root permissions. So it's not comparable in this respect.
It is called by the main blob itself, which runs as root, and sheds permissions only to execute user services. But I'm definitely not an expert on systemd -- heck, I can't even run it on the machine I'm sitting at right now as it won't complete boot... > >> And, cron jobs are nowhere as flexible as systemd timers. > > > > You have two timers: one every 1h (the usual cron way), and another 2min > > after boot. What's the point of the second if you already have an oneshot > > service? > > > It's about having a dynamic (e. g., dhcp) address which could change > anytime. That's why services like this kind periodically checks if the > address has changed and updates the involved DNS entry if so. Yeah, that's what the 1h cronjob is for. You also have one at boot. What I'm pointing at is the second timer that runs 2min after boot -- it's redundant with the service you already have. > > I don't use ddupdate myself anymore (I don't even remember if I used > > ddupdate or one of the alternatives), thus it might be more for an actual > > user. > > You have probably never used it then, it's a pretty new tool. You might, > however, have used ddclient which is sort of similar (and widespread). There's a large number of such clients, yeah. Heck, I once wrote such a script for an own DNS server myself, even... But today, any consumer ISP at any of three places I have non-hosted machines at doesn't even support inbound IPv4 anymore, making tunnels the way to go for me. Meow. -- ⢀⣴⠾⠻⢶⣦⠀ ⣾⠁⢠⠒⠀⣿⡁ Did ya know that typing "test -j8" instead of "ctest -j8" ⢿⡄⠘⠷⠚⠋⠀ will make your testsuite pass much faster, and fix bugs? ⠈⠳⣄⠀⠀⠀⠀
