Skip to content

NEWS followup and a small man addition#9268

Merged
poettering merged 3 commits intosystemd:masterfrom
keszybz:news
Jun 12, 2018
Merged

NEWS followup and a small man addition#9268
poettering merged 3 commits intosystemd:masterfrom
keszybz:news

Conversation

@keszybz
Copy link
Member

@keszybz keszybz commented Jun 12, 2018

No description provided.

* Units gained a new load state "bad-setting", which is used when a
unit file was loaded, but contained fatal errors which prevent it
from being started (for example, an ExecStart= path which references
a non-existent executable).
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

the example isn't right. This state is entered if a service unit has no ExecStart=/ExecStop= line at all, but whether an executable exists at all is only determined when we are going to start it. And that's a good thing as the binary might not exist during early boot yet because its file system is not mounted yet

Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

So I did test this, before committing. ExecStart=asfdasfasd fails (early), but ExecStart=/bin/fasdfasdfsdf "succeeds" (fails late). But you're right, the example is wrong as written.

@poettering poettering merged commit ceb9d45 into systemd:master Jun 12, 2018
@keszybz keszybz deleted the news branch June 12, 2018 14:16
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Development

Successfully merging this pull request may close these issues.

2 participants