-
Notifications
You must be signed in to change notification settings - Fork 368
Add a switch to control writing to /proc/sys #566
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
Conversation
|
Hey alexjh! Thanks for submitting this pull request! I'm here to inform the recipients of the pull request that you've already signed the CLA. |
|
We have created an issue in Pivotal Tracker to manage this. You can view the current status of your issue at: https://www.pivotaltracker.com/story/show/115951553. |
|
Hi @alexjh. Thanks for the contribution! @simonleung8 and I were looking at these two pull requests, and there were a few suggestions that we had before accepting them.
Also, in our tests this variable was not actually passed through to the template, and raised an error for us when we tried to load this in our bosh-lite instance. The scripts to generate manifests pass properties through https://github.com/cloudfoundry/cf-release/blob/master/templates/cf-properties.yml, and does not seem to automatically assign defaults from the job spec files. Are you merging in another properties file to generate your bosh manifest? It seems like you would need to add a default in properties:
......
cc:
persist_core_files: (( merge || true ))
......or
core_file_pattern: (( merge || "/var/vcap/sys/cores/core-%e-%s-%p-%t" ))Then the spec file would serve more as documentation of the properties. |
|
@alexjh It turns out that the errors we saw were caused by a different issue, so please ignore the part about cf-properties.yml above. It still would be nice for this property be named closer to what it actually does, though. Thanks! |
|
Agreed, I think that |
|
Changes proposed in cloudfoundry/diego-release#146 may also be relevant for this PR. |
|
@alexjh - would you like to close or update this per the work in cloudfoundry/diego-release#146? |
|
@SocalNick I think 4946fce reflects the suggestions made on the other PRs, ie make the setting a value and wrap it in an |
|
@alexjh - I was assuming you would just guard this with the |
|
Hi @SocalNick, I was assuming that if this wasn't wrapped already, it wouldn't be a problem for bosh-lite. I'm not sure how I can test this in the bosh-lite vagrant box, I've been looking for documentation on how to do this, but I haven't found anything yet. Do you have any pointers to where I can learn how to do this? I think that a garden equivalent of |
|
Just realized I made this PR against master. I'm going to close and open a new PR done properly. |
|
@alexjh Master will be the right branch for pull request. Go ahead and reopen this PR if you like. |
|
😓 I was reading the cf-release README. Reopening. |
|
Hey alexjh! Thanks for submitting this pull request! I'm here to inform the recipients of the pull request that you've already signed the CLA. |
78267d5 to
9f138c9
Compare
|
Hi @alexjh, @rizwanreza and I were looking at your trio of PRs, but I see that you are still editing the code. This PR is currently not valid Ruby, as the Feel free to make the change and let us know when we can test it again. Thanks, |
This also allows /proc/sys/kernel/core_pattern to be left as the default if `core_file_pattern` is `false`.
|
@adowns01 @rizwanreza I've pushed my update with the fix for |
|
This has been manually merged into master. I don't know why it didn't update here. Thanks, |
Not all environments allow writing to /proc/sys, allow these to be
controlled via config setting added in cloudfoundry/capi-release#3.