-
Notifications
You must be signed in to change notification settings - Fork 528
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’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Y2038: Fix cache_peer connect-timeout reporting #1494
Conversation
Ensure that the timeout value in the neighbours cachemgr report is not truncated on systems having 32-bit integers
I adjusted PR description to better match the proposed fix. Please adjust further as needed. |
It will become even better when we replace doneopts hack with a stream manipulator.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I fixed one PR bug (commit eda290d) and polished, including PR title/description. Please review and adjust further as needed.
p->connect_timeout_raw = xatoi(token + 16); AFAICT, cache_peer connect-timeout parsing is similarly broken. Fixing that can be considered outside this PR scope, but I am not against adding that fix to this PR. Your call. |
Co-authored-by: Alex Rousskov <[email protected]>
Let's keep this PR as a single focus. Added fixing the parsing to my TODO list |
... on systems with 64-bit time_t and 32-bit int. Also fixed `htcp=oldsquid` reporting broken since 2015 commit 4ac1880. This fix affects mgr:config and mgr:server_list cache manager reports.
v6 backporting doesn't apply cleanly. Aborting backport |
... on systems with 64-bit time_t and 32-bit int.
Also fixed
htcp=oldsquid
reporting broken since 2015 commit 4ac1880.This fix affects mgr:config and mgr:server_list cache manager reports.