Add merged *nix agent#28
Conversation
|
One quick comment about the shebang: /bin/sh is going to fail miserably on Solaris 10 or older, as it's a pre-POSIX shell on those systems. For everything else, /bin/sh should be some variant of ksh, ash, bash or dash, which are all POSIX compliant or near enough. And even then, on older versions of supported systems (and we're talking 1990-1994 era... WHY would you have that in production???), they are all going to come packaged with a ksh88 variant. In short: if you're using this on Solaris, it'll blow up. Change the shebang to |
|
Hello Rawiri, thank you for this agent file. We will have a closer look at your patch and discuss internally on how and if we can implement it into the official code base. Internal Ref: CMK-2913 |
|
Hi, the force push a few days ago appears to have broken every existing PR's conflict checks. Are you guys able to fix this mess, or would it be easier if the PR's were recreated? |
|
Sorry, this mess was made necessary by a required force-push. We had to make some history adjustments to our Github repository (yes, you don't actually...). To fix this, you would have to rebase your local clones to the upstream branch and skip all commits except your local commits. |
There was a escaping problem while constructing the command to be executed by mrpe when specifing a non-root user. Change-Id: I1be70e1339bb28e893976db6362b5e9b7d1280e3
|
Thanks Mike, i.e. I'll have a think about a solution for this. |
|
@rawiriblundell As mentioned in the other pull request from you. In AIX 7 /bin/sh and /usr/bin/sh is linked to the korn shell. |
|
Hi @mike1098 , Thanks for that confirmation :) |
|
Closing due to lack of engagement from tribe29. |
|
I am sorry. And I know that doesn't help the cause, but I still want to say that the lack of engagement results from a lack of time, not a lack of interest (speaking for myself, there). |
|
@mo-ki I have also attempted the incremental approach and have had mixed, but mostly disappointing results :( And, I mean, I was in the middle of creating a PR for an incremental change when tribe29 literally told me to not bother: https://forum.checkmk.com/t/clarity-required-on-prs-and-bugfixes/23988 Otherwise, keep up the good work (speaking to you directly, there :) ) |
- cmk.gui.watolib.sites CMK-10313 Change-Id: I2035c98d28aa065ba5b41b025c26a7dca96d1519
Change-Id: If132a193e67ff3cf2fd6a70d841d63cb24242f4b
Change-Id: Icf8b90454d31aaec29c6f9d8904e34ea67a770c3
Change-Id: I3df9b77a0445bbf3a01f703075b4e2796e713960
In PR #21, Sven mentioned the desire to reduce agent counts down to two and to eliminate bashisms.
This PR provides a merged agent script with all but a small handful of non-POSIX-isms eliminated.
It features:
Things that are known-broken and needing attention:
Encryption, as process substitution is not defined in POSIXRTC_SECRET variable is modified within a subshellTo-do:
/Edit: Finally, I expect that if this accepted and tested sufficiently, that at some point the '.merged' will be dropped and it will simply be 'check_mk_agent'. This 'extension' is simply intended as a differentiator until that point.
^[1]I expect that this will break a few things, so I recommend testing. Lots of testing. It would be insanity to think that 11 years of shell script development could be perfectly untangled at the first attempt, but it's a start.