Skip to content
This repository has been archived by the owner on Jan 30, 2020. It is now read-only.

agent: stop units in goroutine during init #630

Merged
merged 1 commit into from
Jul 8, 2014
Merged

Conversation

bcwaldon
Copy link
Contributor

@bcwaldon bcwaldon commented Jul 8, 2014

Fix #624

@jonboulle
Copy link
Contributor

Any idea why this wasn't the case previously?

@bcwaldon
Copy link
Contributor Author

bcwaldon commented Jul 8, 2014

@jonboulle Probably since the agent could be running some ghost units that could conflict with other units being scheduled there. I think this PR is the lesser of two evils, since we really can't allow user jobs to DoS a fleet node.

@jonboulle
Copy link
Contributor

OK, maybe we can revisit once go-systemd has a better way of handling things asynchronously

@jonboulle
Copy link
Contributor

LGTM

bcwaldon added a commit that referenced this pull request Jul 8, 2014
agent: stop units in goroutine during init
@bcwaldon bcwaldon merged commit b9c13eb into coreos:master Jul 8, 2014
@bcwaldon bcwaldon deleted the 624 branch July 8, 2014 23:01
@bcwaldon bcwaldon modified the milestones: v0.6.0, v0.5.4 Jul 14, 2014
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

fleet synchronously stops units during init
2 participants