Pawb.Social Reports @transparency

3 posts3 participants0 posts today

argv minus oneI wonder why systemd-sysv-generator is deprecated for removal.I mean, it's not particularly consequential—it's a separate program and can therefore be forked if anyone still cares about it—but what's the point of dropping it?Is it burdensome on the <a href="https://mastodon.sdf.org/tags/systemd" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#systemd</a> maintainers somehow? Pretty hard to imagine, seeing as how the LSB specification is frozen and the systemd unit specification is guaranteed backward compatible.

Morten LinderudSo, guys.How much further do I take this?<a href="https://chaos.social/tags/golang" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#golang</a> <a href="https://chaos.social/tags/systemd" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#systemd</a> <a href="https://chaos.social/tags/rust" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#rust</a>

JdeBP<a href="https://wandering.shop/@cstross" class="u-url mention" rel="nofollow noopener noreferrer" target="_blank">@cstross</a> <a href="https://toot.cat/@RefurioAnachro" class="u-url mention" rel="nofollow noopener noreferrer" target="_blank">@RefurioAnachro</a> <a href="https://mastodon.social/@Quixoticgeek" class="u-url mention" rel="nofollow noopener noreferrer" target="_blank">@Quixoticgeek</a> I once joked about systemd-emacsd. There would be an emacsctl tool to go with it, of course. And no more LISP when simple declarative .INI files are superior and friendlier to modern developers whose laptops might not have a close round bracket key, you know. /usr/lib/systemd/emacsd.conf and /usr/lib/systemd/emacsd.conf.d/ are the future.But then I once joked about putting an XML parser into process #1; and someone then did that.<a href="https://tty0.social/tags/emacs" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#emacs</a> <a href="https://tty0.social/tags/systemd" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#systemd</a>

JdeBP<a href="https://wandering.shop/@cstross" class="u-url mention" rel="nofollow noopener noreferrer" target="_blank">@cstross</a> I enjoyed how spot-on you accidentally were. (-:Interestingly, people still argue today (as you've probably seen in these threads) as if it were van Smoorenburg rc that was the other choice for Debian et al. back in 2014; which was in reality either Upstart or OpenRC. It's a very persistent erroneous dichotomy.<a href="https://tty0.social/tags/systemd" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#systemd</a> <a href="https://tty0.social/tags/Upstart" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#Upstart</a> <a href="https://tty0.social/tags/OpenRC" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#OpenRC</a>

JdeBP<a href="https://wandering.shop/@cstross" class="u-url mention" rel="nofollow noopener noreferrer" target="_blank">@cstross</a> Right more than you know in one respect; but wrong in another.<a href="https://tty0.social/tags/systemd" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#systemd</a> came from <a href="https://tty0.social/tags/RedHat" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#RedHat</a>, not Microsoft; and the upstart was not Linux but a software package from <a href="https://tty0.social/tags/Canonical" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#Canonical</a> that was literally named "Upstart". (There's a whole backstory about the copyright licence that Canonical initially granted.)Amusingly, Windows NT's Service Controller, its WININIT, and its Session Manager are three distinct things; not like systemd's architecture at all.<a href="https://tty0.social/tags/Upstart" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#Upstart</a>

Daniël Franke :panheart:All the people hating on <a href="https://social.ainmosni.eu/tags/systemd" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#systemd</a> seem to have forgotten how ancient and painful sysV init was...<a href="https://social.ainmosni.eu/tags/linux" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#linux</a>

argv minus oneMy distribution ships a <a href="https://mastodon.sdf.org/tags/systemd" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#systemd</a> service unit file that contains a `Before=` relationship, which I wish to remove.However, writing this in a drop-in does not seem to remove it:``` [Unit] Before= ```Is there some way to remove the `Before=` or do I have to override the entire unit file?<a href="https://mastodon.sdf.org/tags/Linux" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#Linux</a>

argv minus oneIs there a way to have <a href="https://mastodon.sdf.org/tags/systemd" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#systemd</a> give me a listing of all of a unit's relationships?I know of `systemctl list-dependencies`, but it doesn't show me why a service is *not* running. I assume some other unit is conflicting with it, but I'm not sure how to find out.Edit: Found it! `systemctl show` will display this information. And there is indeed a `ConflictedBy=` line showing the conflicting unit.<a href="https://mastodon.sdf.org/tags/Linux" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#Linux</a>

Atemu<a href="https://darmstadt.social/tags/TIL" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#TIL</a> <a href="https://darmstadt.social/tags/systemd" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#systemd</a> can somehow restart itself in a running system and <a href="https://darmstadt.social/tags/NixOS" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#NixOS</a> does it automatically whenever necessary.This must have happened dozens of times already and I never noticed because it's entirely seamless.I only found out because I was curious what exactly the <a href="https://darmstadt.social/tags/NixOS" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#NixOS</a> activation script means when it says "restarting systemd" as that struck me as near impossible.I confirmed that /proc/1/exe points at the same store path that my new version of systemctl comes from; how cool is that?

AskUbuntusystemd at bootup causing issues (waiting for /dev/disk/by-uuid) <a href="https://ubuntu.social/tags/boot" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#boot</a> <a href="https://ubuntu.social/tags/systemd" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#systemd</a> <a href="https://ubuntu.social/tags/maintenance" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#maintenance</a><a href="https://askubuntu.com/q/1543857/612" rel="nofollow noopener noreferrer" translate="no" target="_blank">https://askubuntu.com/q/1543857/612</a>

AskUbuntuEnabling wake on LAN on boot using systemd service does not work #2404 <a href="https://ubuntu.social/tags/systemd" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#systemd</a> <a href="https://ubuntu.social/tags/wakeonlan" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#wakeonlan</a><a href="https://askubuntu.com/q/1543842/612" rel="nofollow noopener noreferrer" translate="no" target="_blank">https://askubuntu.com/q/1543842/612</a>

Kevin Karhan :verified:<a href="https://chaosfem.tw/@freya" class="u-url mention" rel="nofollow noopener noreferrer" target="_blank">@freya</a> <a href="https://mstdn.social/@BrodieOnLinux" class="u-url mention" rel="nofollow noopener noreferrer" target="_blank">@BrodieOnLinux</a> makes sense, ofc.<ul><li>I like SystemD but for <a href="https://infosec.space/tags/OS1337" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#OS1337</a> had to stick with the classic <code>/etc/init</code> file for space reasons alone.</li></ul>Tho in fairness I'm shure <a href="https://infosec.space/tags/SMF" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#SMF</a> did inspire <a href="https://infosec.space/tags/Apple" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#Apple</a> to do <a href="https://infosec.space/tags/LaunchD" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#LaunchD</a> which in turn was copied with <a href="https://infosec.space/tags/SystemD" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#SystemD</a>, abeit all 3 are very much centric about the Kernel and Userland they target.<ul><li>Reminds me of that legendary talk <a href="https://www.youtube.com/watch?v=o_AIw9bGogo" rel="nofollow noopener noreferrer" target="_blank">"The Tragedy of SystemD"</a>…</li></ul>

SabellaI was Today years old, when I finally dug deep enough into the systemd rat's nest, to learn that it creates a directory in /var/log/journal based on the Machine ID, located in /etc/machine-id. and, judging by the last time each directory on my system was touched, a new machine-id is generated each time you do a distro upgrade. and no effort is made to clean up the old logs.edit: the plot thickens. I was Today years old when I also learned that machine-id should be static, ie it shouldn't change if you're doing a distro upgrade.furthermore, crawling through my / partition, I discover that, while the kernal removal tool does indeed remove kernels... if you're using bleeding edge for hardware support, it leaves behind hwe-tools.I've already got several other bug reports to give the Linux Mint team so it's time to get off my lazy tail and finally make a GitHub account.<a href="https://furs.social/tags/linux" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#linux</a> <a href="https://furs.social/tags/systemd" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#systemd</a> <a href="https://furs.social/tags/linuxmint" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#linuxmint</a> <a href="https://furs.social/tags/opensource" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#opensource</a>

AskUbuntuCpu frequency yocto compared to ubuntu <a href="https://ubuntu.social/tags/systemd" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#systemd</a> <a href="https://ubuntu.social/tags/cpufreq" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#cpufreq</a> <a href="https://ubuntu.social/tags/yocto" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#yocto</a><a href="https://askubuntu.com/q/1543721/612" rel="nofollow noopener noreferrer" translate="no" target="_blank">https://askubuntu.com/q/1543721/612</a>

Krutonium://I want a <a href="https://social.treehouse.systems/tags/Minecraft" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#Minecraft</a> <a href="https://social.treehouse.systems/tags/MinecraftMod" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#MinecraftMod</a> that integrates it better with <a href="https://social.treehouse.systems/tags/Systemd" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#Systemd</a> - Things like using systemd for watchdog and stuff.

stib<a href="https://tech.lgbt/@CyrikCroc" class="u-url mention" rel="nofollow noopener noreferrer" target="_blank">@CyrikCroc</a> TIL learned that `sudo systemctl daemon-reload` is a lot easier than rebooting. <a href="https://aus.social/tags/systemd" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#systemd</a> <a href="https://aus.social/tags/linux" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#linux</a>

stibI've set up <a href="https://aus.social/tags/dovecot" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#dovecot</a> on my <a href="https://aus.social/tags/vps" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#vps</a> <a href="https://aus.social/tags/mailserver" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#mailserver</a>, and I want <a href="https://aus.social/tags/systemd" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#systemd</a> to restart it on failure or if it's killed. So in `/etc/systemd/system/dovecot.service.d/restart.conf` I have `[Service] Restart=always RestartSec=5s` But when I pkill the process it doesn't seem to be restarting. I have rebooted. Anyone know why that would be? <a href="https://aus.social/tags/AskFedi" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#AskFedi</a> <a href="https://aus.social/tags/FediTechSupport" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#FediTechSupport</a> <a href="https://aus.social/tags/Linux" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#Linux</a>

LinuxNews.deVervollständige den Satz:„Wäre ich einen Tag lang Linux-/Open-Source-Diktator würde ich …“Bei mir wäre es definitiv das zurechtstutzen von <a href="https://social.anoxinon.de/tags/systemd" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#systemd</a> zu einem reinen Initsystem innerhalb der Distributionen. Aktuell zu ausufernd, inkonsistent und unzuverlässig. Als zweites <a href="https://social.anoxinon.de/tags/rhel" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#rhel</a> SRPM‘s wieder öffentlich stellen

argv minus oneLooking at the scripts a <a href="https://mastodon.sdf.org/tags/hosting" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#hosting</a> provider uses to check if various daemons are running and restart them, and I'm like, “look what they need to mimic a fraction of <a href="https://mastodon.sdf.org/tags/systemd" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#systemd</a> 's power.”

Elias Probst<a href="https://tech.lgbt/@ShadowJonathan" class="u-url mention" rel="nofollow noopener noreferrer" target="_blank">@ShadowJonathan</a> if it's only about simulating those conditions for a single process (and its sub-processes), cgroups might be worth a look.If you don't want to fiddle around with the low-level details of them, wrap the execution of your process in "systemd-run --user --wait --pty ..." and use "--slice" to assign the process to the corresponding slice with the desired resource constraints.<a href="https://www.freedesktop.org/software/systemd/man/latest/systemd-run.html" rel="nofollow noopener noreferrer" translate="no" target="_blank">https://www.freedesktop.org/software/systemd/man/latest/systemd-run.html</a><a href="https://www.freedesktop.org/software/systemd/man/latest/systemd.resource-control.html" rel="nofollow noopener noreferrer" translate="no" target="_blank">https://www.freedesktop.org/software/systemd/man/latest/systemd.resource-control.html</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/cgroups" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#cgroups</a>

Recent searches

Search options

Administered by:

Server stats:

#systemd