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鈥檒l occasionally send you account related emails.
Already on GitHub? Sign in to your account
Improvement to Documentation #4564
Comments
@Saranya-jena can you PTAL? @alininja would you like to raise a PR on this? |
@prithvi1307 sure thing. I was trying to find the source for the documentation, but could not find it. Would you be able to link me to it? Thanks 馃檹 |
Hi @alininja you can raise a PR here: https://github.com/litmuschaos/litmus-docs |
Thank you @Saranya-jena for the link to the repo. Sorry, but I am still unable to find the source file that corresponds to these pages:
Sorry for the newbie confusion. 馃檹 |
Hey @neelanjan00 Can you please help here? |
Hi @alininja, sorry I missed this! Here are the docs link: Thanks for the contribution! 馃檹馃徑 |
Thanks @neelanjan00 for the links. I hope that works. It sounds like the original alternative kill command had typo's so I replaced it instead of adding an additional alternative kill command. Thank you for making such a wonderful product 馃檹 |
Hi 馃憢
I was using these docs to get Litmus working on an OpenShift cluster:
In order for the kill command to work on my OpenShift cluster and pod, I had to update the suggested alternative kill commands to the following:
kill -9 $(ps afx | grep "[dd] if=/dev/zero" | awk '{print $1}' | tr '\n' ' ')
$(ps afx | grep "[md5sum] /dev/zero" | awk '{print $1}' | tr '\n' ' ')
I am not familiar enough to know if the suggested alternative kill commands have a typo or is intended for Windows or is intended for other pod configurations or something else.
kill -9 $(ps afx | grep \"[dd] if=/dev/zero\" | awk '{print $1}' | tr '\n' ' ')
kill -9 \((ps afx | grep \"[md5sum] /dev/zero\" | awk '{print\)1}' | tr '\n' ' ')
Hopefully, this can be helpful to someone else.
Thank you for making this project 馃檹
The text was updated successfully, but these errors were encountered: