Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

sometimes propagate JobTimeoutSec=0 into JobRunningTimeoutSec= #6931

Merged
merged 2 commits into from
Oct 5, 2017

Conversation

poettering
Copy link
Member

A fix for #6402. Not pretty, but should work.

return 0;
}

if (usec == USEC_INFINITY) {
Copy link
Member

Choose a reason for hiding this comment

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

This should solve the immediate issue, but I had the same thought as @Werkov in #6402 (comment): shouldn't this if be dropped`? This patch restores compatibility for the specific case of timeout=infinity, but not for other values.

…ngTimeoutSec= too

We added JobRunningTimeoutSec= late, and Dracut configured only
JobTimeoutSec= to turn of root device timeouts before. With this change
we'll propagate a reset of JobTimeoutSec= into JobRunningTimeoutSec=,
but only if the latter wasn't set explicitly.

This should restore compatibility with older systemd versions.

Fixes: systemd#6402
@poettering
Copy link
Member Author

Force pushed a new version making the suggested change. PTAL

}

/* If the user explicitly changed JobTimeoutSec= also change JobRunningTimeoutSec=, for compatibility with old
* versions. If JobRunningTimeoutSec= was explicitly set, avoid this however as whatever the usec picked should
Copy link
Contributor

Choose a reason for hiding this comment

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

s/usec/user/

Copy link
Member

Choose a reason for hiding this comment

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

Fixed in merge.

@keszybz keszybz merged commit acd53ea into systemd:master Oct 5, 2017
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.

None yet

3 participants