3 ms·
This is more a case of "nohup was broken anyway, so we are well within our rights to do whatever we want. We'll write our own new API for it in a version or two
by tremon 10y ago
This is more a case of "nohup was broken anyway, so we are well within our rights to do whatever we want. We'll write our own new API for it in a version or two."
- wtallis 10y agoSo where's the explanation of how nohup is broken enough to be worth breaking the rest of the way and replacing with a more complex non-portable alternative?
- tremon 10y agoI was speaking in general, you probably won't be getting that explanation until enough people post a bug about it on Red Hat's bugzilla. Then we'll get the usual dance of systemd maintainers saying it's working as intended, users saying it used to work differently, systemd maintainers saying that the old behaviour was wrong and users were stupid to rely on it, etc. So, like this one: https://bugzilla.redhat.com/show_bug.cgi?id=753882#c29 https://bugzilla.redhat.com/show_bug.cgi?id=753882#c29