10 ms·
My impression is that the script is being run as root. It's going along, running everything as root... It encounters an attempt to run a command as a different
by code_duck 9y ago
My impression is that the script is being run as root. It's going along, running everything as root... It encounters an attempt to run a command as a different user, and being unable to find a user matching that, says okay, whatever, I'll just run that as root too.
- digi_owl 9y agoIt is kinda funny how systemd will bail to the emergency console if it can't figure out the dependencies chain. but it will happily run something as root if told to not do so, but can't find the user account it it told to use.
- vbernat 9y agoIf you provide a valid username (by systemd definition) of a user who doesn't exist, systemd won't run the unit. The behavior is just consistent with unknown/invalid options (IMO, User= should be an exception to this).
- qb45 9y agoIt isn't even consistent with unknown options, because the option User is known. Once this is recognized, there should be no difference between nonexistent and invalid usernames. I don't even want to know how their code is written so that it allows such error to happen and remain undetected.
- detaro 9y agoIf it can't find a matching user, it aborts as an error. When it doesn't think the value could possibly be a valid user, then it ignores the rule to run as a different user completely.