|
|
|
|
|
by chaps
2257 days ago
|
|
The post is about how systemd wasted lots of time, in a thread about software that has wasted lots of time. The issues around bad documentation and the specific issue (the last one is probably the issue I had, but this was five years ago lol. Knowing me and arch linux, I probably didn't have the full man pages installed, so the cli tools were the only thing I had available.) wasted me a lot of time and very clearly others, and that's exactly the point of this discussion! Hell, to troubleshoot that issue, I even ran something like a `find / -exec strings -a '{}' ; | grep timeout` and found nothing that ended up being helpful. But I absolutely had some form of documentation, again likely the last link I provided which isn't simply a philosophical issue when it provides misleading information that would have ultimately fixed the issue if it gave more informative output! You admit yourself that the documentation can be insufficiently clear with bugs, and it's true: systemd happens to have lots of time killing bugs. The whole point of this thread. You're missing the forest for the trees, friend. |
|