Add HTTP support and improve compatibility with older BMCs #8
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Fixes for X9-series boards with older firmware (tested on X9DR3-LN4F+ with BMC 3.61).
Changes:
KVM_PROTOCOLenv var to allow HTTP connections (many older BMCs don't do HTTPS properly)LD_LIBRARY_PATHfor more reliable native library loading-Djava.library.pathexplicitly in startapp.shExample usage for HTTP-only BMC:
Relates to #3 and #7 - the HTTP support and pack200 fixes should resolve the setup script failures, and the argument parsing changes should fix the
$5: parameter not setcrash on BMCs that only provide 4 arguments in the JNLP.Note on flickering: If the console appears to flicker or the window keeps resizing, the BMC may be losing video sync as the OS switches modes during boot. This shows as "no signal" in the Java viewer's floating toolbar (not always obvious with the docked toolbar). On TrueNAS we fixed this with
nomodeset vga=794in kernel parameters - other distributions may vary.