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

Why is running as a service no longer an option? #125

Closed
bschonec opened this issue Nov 28, 2016 · 1 comment
Closed

Why is running as a service no longer an option? #125

bschonec opened this issue Nov 28, 2016 · 1 comment

Comments

@bschonec
Copy link

Quoting the README.md:

The agent does not run as a service. There is no good reason for running the service. Instead cron should be used to better manage how and when the agent runs.

Why is cron the better choice? I've been running the puppet client as a service for years. Wouldn't it make sense to let the user make the choice as to how to run the client instead of remove that choice entirely?

@ghoneycutt
Copy link
Owner

Hi @bschonec

This is a rewrite of the module for Puppet v4 only and takes on my very opinionated approach. Running through cron allows you to know when the puppet agent will run while still allowing for randomization of the runs. The method for doing this running the service is to use splay, though it does not allow you to know when the agent will run. Why do you run the service other than it being the default?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants