1 of 1 people found this helpful
The shell does'nt lose characters if used correctly. It's nomal that there are limitations on the input buffer, and the person or script writing commands into the shell interactively (which is simulated by ADDM) must take care for this.
I really believe there is something broken in the interaction between the scanner and the scanned machine. I'm betting on some kind of over-optimisation, which pumps more commands into the target host than it can process, leading in lost bytes in the buffer.
I'm working with the support on this issue, and I have tried many, many different options. Changing the shell to bash, setting the session time limit, force subshell on/off. None of them worked 100% or is acceptable, and I have serious problems with "reducing the chance this issue occurs", which translates to me as "pah, be happy that 99% works - it could be worse!".
I have a very good solution, which removes the problem absolutely reliable, but that's not enough for me. It's still a workaround. I want BMC to fix the PROBLEM.
My request is: how many other customers suffer from this issue? If I know of a bunch of other customers, we can probably make BMC fix the underlying bug, resulting in a more reliable product - that's something, we all want, I assume.
Haven't noticed this issue until just now, we have seen this happen very randomly and infrequently but it still happens. We do not have the Force Shell option turned on. Interested to see if this is still an issue or if a "solution" has been provided?