4 ms·

> Are user processes allowed to run after logout? Which DNS to use during startup? What logging in should look like? In each such case, existing behavior which

by m45t3r 6y ago

> Are user processes allowed to run after logout? Which DNS to use during startup? What logging in should look like? In each such case, existing behavior which was widely considered as not broken was replaced by a different behavior, often even without an escape hatch. The new behavior(s) in such cases should be made possible, but the default should be the old behavior. All those examples you gave are possible to disable in systemd, and in the case of DNS and user process after logout, they are not even the default. : Killing of user process are enabled by default in upstream but disabled by default in every distro that I know. And systemd-resolved, even if it is build by default, is not enabled by default even in upstream.

nine_k 6y ago
Good thing sanity prevails in distro maintainers! But not in upstream, as you duly note. I also remember that even 2-3 years ago the situation was not as nice yet. I think what became systemd could have been great software, if not for the, mmm, cavalier attitude of its creators (not necessarily personal; it might be amended by RH corporate deadlines).
- hnarn 6y ago
  "Not in upstream" doesn't seem to correspond with the comment you replied to.
  - nine_k 6y ago
    Quoting: "Killing of user process are enabled by default in upstream but disabled by default in every distro that I know."
    - hnarn 6y ago
      I really shouldn't write HN comments right after waking up.
- m45t3r 6y ago
  The fact that `KillUserProcess` is default to on is not something that systemd forces to your distro, there is even a flag to disable it at build time. It does makes sense in many situations (like IoT, embedded, etc.), that is why it is on, but distro mantainers also needs to know what is better for its users (that anyway is a really small part of Linux users, embedded is much bigger).
TingPing 6y ago
resolved has been enabled in Ubuntu for years and in the next Fedora.
- m45t3r 6y ago
  This is a decision of your distro mantainers, they could also default to unbound, dnsmasq, bind, or anything else. They use systemd-resolved because it probably solves some problem for them, even if this problem is reduced burden of maintenance.

by m45t3r 6y ago

nine_k 6y ago

Good thing sanity prevails in distro maintainers! But not in upstream, as you duly note. I also remember that even 2-3 years ago the situation was not as nice yet. I think what became systemd could have been great software, if not for the, mmm, cavalier attitude of its creators (not necessarily personal; it might be amended by RH corporate deadlines).

hnarn 6y ago
"Not in upstream" doesn't seem to correspond with the comment you replied to.
- nine_k 6y ago
  Quoting: "Killing of user process are enabled by default in upstream but disabled by default in every distro that I know."
  - hnarn 6y ago
    I really shouldn't write HN comments right after waking up.
m45t3r 6y ago
The fact that `KillUserProcess` is default to on is not something that systemd forces to your distro, there is even a flag to disable it at build time. It does makes sense in many situations (like IoT, embedded, etc.), that is why it is on, but distro mantainers also needs to know what is better for its users (that anyway is a really small part of Linux users, embedded is much bigger).

TingPing 6y ago

resolved has been enabled in Ubuntu for years and in the next Fedora.

m45t3r 6y ago
This is a decision of your distro mantainers, they could also default to unbound, dnsmasq, bind, or anything else. They use systemd-resolved because it probably solves some problem for them, even if this problem is reduced burden of maintenance.