toad.social

14 posts11 participants3 posts today

Kevin Karhan :verified:<a href="https://climatejustice.social/@HeatSinkAmbassador" class="u-url mention" rel="nofollow noopener noreferrer" target="_blank">@HeatSinkAmbassador</a> <a href="https://labyrinth.zone/users/halva" class="u-url mention" rel="nofollow noopener noreferrer" target="_blank">@halva</a> <a href="https://ubuntu.social/@ubuntu" class="u-url mention" rel="nofollow noopener noreferrer" target="_blank">@ubuntu</a> <a href="https://fosstodon.org/@opensuse" class="u-url mention" rel="nofollow noopener noreferrer" target="_blank">@opensuse</a> Then why did <a href="https://infosec.space/tags/Linux" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#Linux</a> standard on SystemD?<ul><li>Certainly <a href="https://social.lfx.dev/@linuxfoundation" class="u-url mention" rel="nofollow noopener noreferrer" target="_blank">@linuxfoundation</a> or whoever writes the <a href="https://infosec.space/tags/LSB" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#LSB</a> took their time re: that change and if you have ever habe to deal with huge amounts of servers, the whole benefits of the "<a href="https://infosec.space/tags/SystemD" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#SystemD</a> suite" really works well, because noone wants to deal with a shitton of filters & <a href="https://infosec.space/tags/syslog" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#syslog</a> over <code>journalctl -xe …</code></li></ul>Don't get me wrong, <a href="https://infosec.space/@OS1337" class="u-url mention" rel="nofollow noopener noreferrer" target="_blank">@OS1337</a> runs off a <a href="https://github.com/OS-1337/OS1337/blob/main/build/0.CORE/fdd/fs/etc/init" rel="nofollow noopener noreferrer" target="_blank">single <code>/etc/init</code> file...</a>, but for an embedded distro of it's tinyness, that is acceptable.

Kevin Karhan :verified:<a href="https://labyrinth.zone/users/halva" class="u-url mention" rel="nofollow noopener noreferrer" target="_blank">@halva</a> +9001%I've used <a href="https://ubuntu.social/@ubuntu" class="u-url mention" rel="nofollow noopener noreferrer" target="_blank">@ubuntu</a> 7.04 and <a href="https://fosstodon.org/@opensuse" class="u-url mention" rel="nofollow noopener noreferrer" target="_blank">@opensuse</a> 10.2 and noone wants to go back to those ages when we had <a href="https://infosec.space/tags/WiFi" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#WiFi</a> problems, had to fiddle with <a href="https://infosec.space/tags/nVidia" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#nVidia</a> drivers and <a href="https://infosec.space/tags/AMD" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#AMD</a> was just not an option!<ul><li>Same with <a href="https://infosec.space/tags/SystemD" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#SystemD</a>: <a href="https://infosec.space/tags/SysVinit" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#SysVinit</a> is shit and everyone who thinks it's reasonable amto wait 5-15+ mins for a desktop to boot is even mire delusional than <a href="https://infosec.space/tags/Xorg" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#Xorg</a> fans wanting to cancel <a href="https://infosec.space/tags/Wayland" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#Wayland</a>!</li></ul><a href="https://www.youtube.com/watch?v=o_AIw9bGogo" rel="nofollow noopener noreferrer" translate="no" target="_blank">https://www.youtube.com/watch?v=o_AIw9bGogo</a>

Neil Brown# Running vdirsyncer automatically using a systemd timerA new (and probably rather niche) blogpost, which rather does what it says on the tin.If you want a terminal-based solution for carddav and caldav, this might help.<a href="https://neilzone.co.uk/2025/06/running-vdirsyncer-automatically-using-a-systemd-timer/" rel="nofollow noopener noreferrer" translate="no" target="_blank">https://neilzone.co.uk/2025/06/running-vdirsyncer-automatically-using-a-systemd-timer/</a><a href="https://mastodon.neilzone.co.uk/tags/vdirsyncer" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#vdirsyncer</a> <a href="https://mastodon.neilzone.co.uk/tags/FOSS" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#FOSS</a> <a href="https://mastodon.neilzone.co.uk/tags/systemd" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#systemd</a> <a href="https://mastodon.neilzone.co.uk/tags/tui" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#tui</a> <a href="https://mastodon.neilzone.co.uk/tags/terminal" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#terminal</a>

JdeBP<a href="https://hachyderm.io/@dalias" class="u-url mention" rel="nofollow noopener noreferrer" target="_blank">@dalias</a> <a href="https://social.treehouse.systems/@ska" class="u-url mention" rel="nofollow noopener noreferrer" target="_blank">@ska</a> Well they *are* making their own versions of those two macros. I'd already read the ostensible rationale for it, and it seemed poor.They have a problem with their own code's headers having lots of cross-dependencies. (Strong coupling and low cohesion: a long-standing <a href="https://tty0.social/tags/systemd" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#systemd</a> problem.) That's not a reason for fiddling with the <a href="https://tty0.social/tags/StandardC" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#StandardC</a> library, let alone making one's own FILE and DIR macros.<a href="https://tty0.social/tags/musl" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#musl</a>

JdeBP<a href="https://social.treehouse.systems/@ska" class="u-url mention" rel="nofollow noopener noreferrer" target="_blank">@ska</a> <a href="https://hachyderm.io/@dalias" class="u-url mention" rel="nofollow noopener noreferrer" target="_blank">@dalias</a> I understood Daniel J. Bernstein's avoidance of the Standard C library, especially strings and standard I/O which had been rife with pointer mis-uses for decades.But this is not that.Why on Earth would one continue to use stdio but roll one's own version of the GNU C library's FILE and DIR macros?<a href="https://github.com/systemd/systemd/issues/37779#issuecomment-2952813363" rel="nofollow noopener noreferrer" translate="no" target="_blank">https://github.com/systemd/systemd/issues/37779#issuecomment-2952813363</a><a href="https://tty0.social/tags/StandardC" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#StandardC</a> <a href="https://tty0.social/tags/systemd" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#systemd</a> <a href="https://tty0.social/tags/musl" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#musl</a>

Taffer 🇨🇦 :godot:So, if I run my entire backup script with `systemd-run --user --slice=lowcpu --nice=19` it constrains the CPU as I've configured it in the `lowcpu.slice` I created. 👍 If I add `systemd-run --user --slice=lowcpu --nice=19` to individual `restic` invocations inside the script, it doesn't. WTF. 👎 <a href="https://mastodon.gamedev.place/tags/systemd" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#systemd</a> <a href="https://mastodon.gamedev.place/tags/cgroups" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#cgroups</a>

Taffer 🇨🇦 :godot:systemd: takes over cgroupsalso systemd: doesn't work to control cpu.maxBack to reading manpages, I guess.<a href="https://mastodon.gamedev.place/tags/systemd" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#systemd</a> <a href="https://mastodon.gamedev.place/tags/cgroups" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#cgroups</a>

Linux MagazineUsing an SSH credential brute-force attack, Go-based PumaBot is exploiting IoT devices everywhere <a href="https://www.linux-magazine.com/Online/News/Go-Based-Botnet-Attacking-IoT-Devices?utm_source=mlm" rel="nofollow noopener noreferrer" translate="no" target="_blank">https://www.linux-magazine.com/Online/News/Go-Based-Botnet-Attacking-IoT-Devices?utm_source=mlm</a> <a href="https://fosstodon.org/tags/malware" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#malware</a> <a href="https://fosstodon.org/tags/PumaBot" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#PumaBot</a> <a href="https://fosstodon.org/tags/IoT" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#IoT</a> <a href="https://fosstodon.org/tags/security" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#security</a> <a href="https://fosstodon.org/tags/SSH" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#SSH</a> <a href="https://fosstodon.org/tags/systemd" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#systemd</a> <a href="https://fosstodon.org/tags/firewall" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#firewall</a>

Gary Hawkins<a href="https://mastodon.neilzone.co.uk/@neil" class="u-url mention" rel="nofollow noopener noreferrer" target="_blank">@neil</a> But I thought there were no bugs in <a href="https://mastodon.garyhawkins.uk/tags/systemd" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#systemd</a>, Lennart Pöttering says you're just doing it wrong? 😂

Neil BrownUnexpected item in debugging area.<a href="https://mastodon.neilzone.co.uk/tags/systemd" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#systemd</a>

Adam HonseUpgraded all of my working arm64 <a href="https://mastodon.social/tags/postmarketOS" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#postmarketOS</a> devices to the latest <a href="https://mastodon.social/tags/phosh" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#phosh</a> <a href="https://mastodon.social/tags/systemd" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#systemd</a> edge! Also wrote a small script to do all my preferred app installs and some configurations (my custom squeekboard layout, autostart TouchpadEmulator, set default scaling to 200%) to make reinstalling less painful.

st1nger :unverified: 🏴‍☠️ :linux: :freebsd:Two information disclosure flaws have been identified in <a href="https://infosec.exchange/tags/apport" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#apport</a> and <a href="https://infosec.exchange/tags/systemd" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#systemd</a>-coredump, the core dump handlers in <a href="https://infosec.exchange/tags/Ubuntu" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#Ubuntu</a>, <a href="https://infosec.exchange/tags/RedHat" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#RedHat</a> Enterprise <a href="https://infosec.exchange/tags/Linux" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#Linux</a>, and <a href="https://infosec.exchange/tags/Fedora" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#Fedora</a>, according to the <a href="https://infosec.exchange/tags/Qualys" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#Qualys</a> Threat Research Unit (TRU).Tracked as CVE-2025-5054 and CVE-2025-4598, both <a href="https://infosec.exchange/tags/vulnerabilities" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#vulnerabilities</a> are race condition bugs that could enable a local attacker to obtain access to access sensitive information. Tools like Apport and systemd-coredump are designed to handle crash reporting and core dumps in Linux systems.<a href="https://thehackernews.com/2025/05/new-linux-flaws-allow-password-hash.html" rel="nofollow noopener noreferrer" translate="no" target="_blank">https://thehackernews.com/2025/05/new-linux-flaws-allow-password-hash.html</a>

argv minus oneSo, if <a href="https://mastodon.sdf.org/tags/Samba" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#Samba</a> could go ahead and stop spitting out multiple <a href="https://mastodon.sdf.org/tags/systemd" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#systemd</a> journal entries for a single event and using the wrong priorities, that'd be great.“Samba name server SERVER is now a local master browser” is not an error and does not need to be spread across no less than *six* log messages.I just ran `journalctl -b -p warning` and nearly half of the log lines are from Samba, none of which are warnings or errors. Lol wtf.<a href="https://mastodon.sdf.org/tags/Linux" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#Linux</a>

LinuxiacGrafito is a sleek, systemd journal viewer that makes reading system logs easy, with live streaming, powerful filters, and a clean web-based UI. <a href="https://linuxiac.com/grafito-systemd-journal-log-viewer-with-a-beautiful-web-ui/" rel="nofollow noopener noreferrer" translate="no" target="_blank">https://linuxiac.com/grafito-systemd-journal-log-viewer-with-a-beautiful-web-ui/</a><a href="https://mastodon.social/tags/linux" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#linux</a> <a href="https://mastodon.social/tags/systemd" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#systemd</a> <a href="https://mastodon.social/tags/log" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#log</a> <a href="https://mastodon.social/tags/opensource" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#opensource</a>

Sebastian "spaetz" Spaeth<a href="https://mastodon.social/@pid_eins" class="u-url mention" rel="nofollow noopener noreferrer" target="_blank">@pid_eins</a> it probably does not count much, but as one of the initial sceptics of <a href="https://mas.to/tags/systemd" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#systemd</a> I would like to fully apologize to you now. I love the scope and way in which systemd acts.I might still not like the management style in which this was pulled through at times, but the result is awesome.It kind of adjusted my assumption that many independent modules (which are not necessarily guided by the same architectural vision) working together is the best way to design complex systems.

furicleContinuing my fun with systemd service files - is there any way to pass the definition of the exit codes through?e.g. my unit.service does an `exit 5` in certain cases. In journalctl that shows up as 'status=5/NOTINSTALLED'I think that comes from here<a href="https://www.freedesktop.org/software/systemd/man/latest/systemd.exec.html#Process%20Exit%20Codes" rel="nofollow noopener noreferrer" translate="no" target="_blank">https://www.freedesktop.org/software/systemd/man/latest/systemd.exec.html#Process%20Exit%20Codes</a>I'd like it say 5/NOSYNCREQUIRED or similar. I'd be happy to chose codes that aren't pre-defined if that helps?Is this possible?<a href="https://mastodon.social/tags/linux" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#linux</a> <a href="https://mastodon.social/tags/systemd" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#systemd</a> <a href="https://mastodon.social/tags/exitcode" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#exitcode</a>

furicleAn update on my <a href="https://mastodon.social/tags/systemd" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#systemd</a> timer question - systemctl list-timers didn't have a 'next run' time showing, while the service unit was running, but now that it's completed, it's showing a next run time of 1 h after the prior start time. So I guess it doesn't schedule the next run until the existing run completes.

furicleI'm slightly confused by <a href="https://mastodon.social/tags/systemd" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#systemd</a> timers and OnUnitActiveSec=1h Two questions 1 If the service unit it activates takes less than an hour to complete, will it will run again one hour after the first *start* or one hour after the *end* of that run ?2 If the service unit takes longer than a hour to complete, it seems to run again right away. What happens after repeated missed runs? If the service unit takes four hours for a run, will it "stack up" three more runs to be done? or just one?

Flatcar Container Linux 🚂Alpha 4344.0.0 provides NVIDIA drivers through a <a href="https://hachyderm.io/tags/systemd" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#systemd</a> sysext image for a better user experience and stability.

Recent searches

Search options

Administered by:

Server stats:

#systemd