71–79 of 79 posts
Earlier quoted context omitted.
Its never a good systemd-networkd default to be killing daemon whenever a netdev goes “cricket”.
It's not a networkd default. Networkd doesn't kill or even care about other services. The setting exists on the service's unit side. You have to explicitly specify how you want to depend on networking.
Earlier quoted context omitted.
It's not a networkd default. Networkd doesn't kill or even care about other services. The setting exists on the service's unit side. You have to explicitly specify how you want to depend on networking.
Try it. Pull the Ethernet cable.
Earlier quoted context omitted.
It's not a networkd default. Networkd doesn't kill or even care about other services. The setting exists on the service's unit side. You have to explicitly specify how you want to depend on networking.
Try it. Pull the Ethernet cable.
systemd is incredibly useful and powerful. If you are a developer on Linux then you really owe it to yourself to learn as much as you can about systemd. If you really understand systemd then you'll find yourself architecting your software around its capabilities. systemd, if you understand it, can mean you can completely avoid large chunks of development you might otherwise have assumed you need to do. socket activat…
Earlier quoted context omitted.
He doesn't even know how to read man pages (journald.conf(5) describes the setup he is looking for), and he doesn't know how memory usage on Linux works (shared /mmap()ed memory is counted for each process). Do you really think his issues go away when he switches to Devuan? He'll probably just yell at different clouds Other than that, Devuan is a solid choice for people who want to get rid of systemd. It comes with t…
The systemd man pages are a book. And, just for avoidance of doubt, that's not a good thing. I am never surprised when someone can't find out how to configure systemd to do what they want. It's just too enterprise grade.
People complain about how bad or non-existing Linux's man-pages are compared to the BSDs, and then systemd comes along with a really extensive and well-written set of manpages and people complain that it's too much
Can't make everyone happy I guess...
Earlier quoted context omitted.
It's not a networkd default. Networkd doesn't kill or even care about other services. The setting exists on the service's unit side. You have to explicitly specify how you want to depend on networking.
Try it. Pull the Ethernet cable.
Earlier quoted context omitted.
As someone pointed out elsewhere in the thread, so can systemd, your service did what it was configured to do. If you want the service to stay up when netdev goes down, then don't tell systemd that netdev is a hard requirement for your service.
Its never a good systemd-networkd default to be killing daemon whenever a netdev goes “ cricket ”.
There is no "system default" in the loop here at all. The service told systemd that it cannot operate without netdev, and systemd behaved accordingly. If the config was written more appropriately, it would have behaved accordingly. The "default" is what you had written in the unit file.
Earlier quoted context omitted.
>You can run quite a lot in 512MB of RAM if you use the right languages to write code in. I recently delivered a production-ready embedded system running Armbian with 512megs RAM, and indeed disabled systemd-journald for our uses, also .. but even with it enabled, our Lua-based app was (science/data analysis on sensor network) running in the best environment it has ever run, so I can confirm: 512MB is enough for a lo…
Windows 95 ran an entire OS with decent UI in 8 MB of RAM. One really has to wonder, where is all the RAM going these days? I think the knowledge of doing anything with only 8 MB of RAM has gone away, we don't know how to do it anymore.
Windows 95 also didn't do things the modern way. It didn't keep an image of every application's windows in RAM. It kept track of what covered up what, and then asked applications to redraw themselves when needed.
Another huge amount is going to features like internationalization. Unicode is a beast that takes a good amount of code to implement, and Arial Unicode is a ~20 MB TTF file.
Modern luxuries like being able to tweet in Japanese are quite expensive.