4 ms·
> I have no idea if this bug gets triggered by those as well Why should it? The bug is not that it runs as root but that it encounters a parsing error and uses
by the_mitsuhiko 9y ago
> I have no idea if this bug gets triggered by those as well
Why should it? The bug is not that it runs as root but that it encounters a parsing error and uses the default. The default for root is root and the default for user A is user A.
- falcolas 9y ago> Why should it? Thank you for the correct, if condescending, answer. It was unclear from the original bug, or this article, if it was falling back on a hardcoded 0 or the user used when the directive is not present. Since systemd's own behavior is inconsistent, I can't depend on that behavior to derive the reasonable answer. That inconsistency stems from the fact that a "valid" user name that doesn't exist triggers different behavior than an "invalid" user name; and the definition of "valid" is different between systemd and the rest of Linux.