Join GitHub today
GitHub is home to over 20 million developers working together to host and review code, manage projects, and build software together.
knife cluster kick shouldn't rely on already running chef-client #109
This would fix several problems associated with long-running
In both cases, insisting on utilizing a long-running
What would we lose by making
This comment has been minimized.
This comment has been minimized.Show comment Hide comment
If you know that you're not going to have a running chef-client, then you don't lose anything. However if you've got a running chef client you can have badness like two simultaneous chef runs that e.g. both download a file at the same time. One finishes, tries to do something withe the downloaded file, but the second one has tried to start its own download, so the first one blows up, and the second one doesn't know to clean up any turds left, etc. In addition, without the --once flag you're going to end up with multiple chef-clients hanging around and running constantly.
For my own case, our policy is to not keep a chef-client running. I've added a "--once" option to kick which runs "chef-client --once". I will get around to turning that into a pull request.