On 5/30/24 13:18, Todd Zullinger wrote:
Kevin Fenzi wrote:
[...snip loads of useful information...]
So, I think if you:
disable systemd-resolved
sudo bash -c 'mkdir -p /etc/systemd/system-preset && echo "disable systemd-resolved.service" >/etc/systemd/system-preset/20-systemd-resolved-disable.preset'
Here's one that doesn't eat yet another inode ( and saves some typing )
for f in disable stop mask; do sudo systemctl $f systemd-resolved; done
--
I just wasted at least a week with systemd-networkd trying to configure
half a dozen or so bridges, their members, some regular ports, and a mix
of static and dynamic addresses. It required dozens of .link, .network,
.netdev files, each about 50 to 100 bytes, and each consuming a 4k
inode. If systemd had a theme song it would be Queen's "Another One
Bytes the Dust". Back when 2μS SRAM came in 1kx1 dips at $2 each and a
few hundred megabytes would consume an entire fab line's output for who
knows how long we would make fun of the programmers, "give them a byte
and they'll take a k."
In the end I spent a few hours writing a script to bring everything up,
down, show status, list options and call it from a miniscule systemd
service that runs after network-online. And it only ate two inodes.
--
_______________________________________________
users mailing list -- users@xxxxxxxxxxxxxxxxxxxxxxx
To unsubscribe send an email to users-leave@xxxxxxxxxxxxxxxxxxxxxxx
Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: https://lists.fedoraproject.org/archives/list/users@xxxxxxxxxxxxxxxxxxxxxxx
Do not reply to spam, report it: https://pagure.io/fedora-infrastructure/new_issue
