-
Notifications
You must be signed in to change notification settings - Fork 423
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
Enable chef setting for tcp_listen linger option #321
Conversation
@jjasghar could you please review this ? |
I'll take a look at this, and do some research on this. @michaelklishin any thoughts on this option? This is the first i've heard of it. |
@michaelklishin fyi...I had sent out an email to openstack-operators mailing list as well. |
Thanks @jjasghar |
Socket lingering is primarily useful to clients but I have no objections to this. Keep in mind that as of |
@michaelklishin do we know for sure that linger {true, 0} is always the default setting in rabbitmq config ? |
Thanks @michaelklishin. |
I'm going to run this through our testing today. Any chance you can create an integration/unit test for this? I really don't like adding things to this cookbook without test coverage. |
@jjasghar sure...will add unit tests. I tried to look for existing tests related to rabbitmq config and did not find any. So, had skipped it. Let me dig more. |
Sounds good, just Unit tests are probably fine. When you get them added I'll go through my release process and get this pushed out. |
@jjasghar have updated the change with unit tests. Could you please review it again ? Thanks. |
Awesome, thanks. I'll run some final tests and push out a new version ASAP. |
Enable chef setting for tcp_listen linger option
No description provided.