You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Jan 15, 2019. It is now read-only.
which may harm it too, when hitting huge long_output and perfdata here.
at least, such strings should not be ended with \0 but rather with the IDO_API_ENDDATA flag in order to let ido2db know that the data was sent and ends here (not swapping into the next section).
This issue has been migrated from Redmine: https://dev.icinga.com/issues/3517
Created by mfriedrich on 2013-01-02 20:20:37 +00:00
Assignee: (none)
Status: Rejected (closed on 2014-07-19 12:33:29 +00:00)
Target Version: (none)
Last Update: 2014-12-08 14:46:52 +00:00 (in Redmine)
the current handling of the socket buffer is a bit creepy, just cutting off the buffer and revoking the protocol information for ido2db.
there should be a way to determine the length of the expected buffer, or even cut it in chunks for output, long_output, perf_data.
the current solution in #2342 limits that to
which may harm it too, when hitting huge long_output and perfdata here.
at least, such strings should not be ended with \0 but rather with the IDO_API_ENDDATA flag in order to let ido2db know that the data was sent and ends here (not swapping into the next section).
Relations:
The text was updated successfully, but these errors were encountered: