* script reports app is stopped right after you run start. Debian had some pre-made wrappers that mostly did the right thing) and fixed by us because people saying "it's so easy" to write init script ARE LYING.Īnd some apps, like Pacemaker (app for making other things HA), are really sensitive on scripts not being done fully correctly We had, no joking, thousands lines of init scripts that were just ripped out of distro (mostly CentOS/RHEL. Every program needed it's own little way of doing things and writing an init script for a daemon was a hassle of bash scripting and copy pasting. > I have used init scripts, I have written init scripts. runit, based on The DJB Way, is much closer to my ideal. The next time I configure a workstation from scratch, I'm going to voidlinux. For many years I've simply copied my home dir to new computers and moved on. I use linux for my work, both in embedded targets and in my development workstation. This was Red Hat's intention, now IBM's intention. Everyone will simply put the kernel together w/ systemd for a complete operating system. If the rootfs you're configuring, isn't the one currently active, those binary executables are going to havee trouble.Īs soon as we have systemd-packagemanagerd, there will be 0 difference between systemd based distributions. If you've configured a rootfs for a machine other than the one you're doing this work on (maybe a different CPU architecture, or simply a rootfs for another machine) you're going to run into complications. Is the "init" system in charge of network name resolution? What about making fundamental configuration setting to the OS? Another example of the binary required to access logs, is any change to a non-running root filesystem. This isn't feature creep, it's by design. Systemd if far far beyond an "init" system, it is striving to be the "kernel" of user space, in charge of all system functions that are not in the kernel. The binary interface to logs is a good example, not only for the popular dislike for needing to run a binary to view the log, but also, central to my dislike, is the issue with the "init" system being in charge of logging at all. I've been using it (including writing unit files etc) since archlinux adopted it, so over 10 years now. Which is shame coz I like many of the other parts. It's an abomination and affront to good engineering. But hey if you waste RAM to cache every journal file on your machine in RAM instead of, dunno, actually useful stuff, those commands are fast. I can literally grep a bunch of text files faster than it can look thru it's "efficient" binary logs. It opens SEVENTY ONE FILES TO GET LOGS ABOUT ONE APPLICATIONįOR WHICH IT HAS NO LOGS IN THE FIRST PLACE Strace systemctl status 2>&1 |grep /var/log/journal |wc -l They could literally just drop in SQLite there and now your entire's system's logs have power of being queried via SQL which would be amazing and easy to use with countless tools that can be used with SQLite but NO, (probably) Lennart wanted to have some fun writing shitty binary format coz of his chronic NIH. It might have actual indexing, who the fuck knows, but it don't have any useful one They made binary format THAT DON'T HAVE ANY FUCKING PROPER INDEXING. I mostly like systemd but journalctl/journald unequivocally sucks arse with passion.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |