{"shas":[["5ea5d97253b44147855c78637403fc82903962f2","8858498612e3a522354216649776e3032dcb7e5b@wantstofly.org","iv_work.3: Minor formatting change.\n\nSigned-off-by: Lennert Buytenhek <buytenh@wantstofly.org>","Lennert Buytenhek"],["bc64865cec3a19bb8b44de7e7c2437c21d70d1eb","8858498612e3a522354216649776e3032dcb7e5b@wantstofly.org","Include config.h in iv_private.h.\n\nSo that all lib/ code gets it included automatically.\n\nSigned-off-by: Lennert Buytenhek <buytenh@wantstofly.org>","Lennert Buytenhek"],["287bfb6845b4d00ef02e16df859fbf3334075241","c9ced0bffa833fad400e0759f75a89a845bcc267@balabit.hu","Fall back to CLOCK_REALTIME/gettimeofday(2) if CLOCK_MONOTONIC is not provided.\n\nSome time ago, ivykis switched from gettimeofday(2) to CLOCK_MONOTONIC\nfor its internal timer management, as gettimeofday(2) is not guaranteed\nto be monotonic, and using a nonmonotonic time source for ivykis timer\nmanagement can cause confusion when that time source jumps forward\n(causing timers to fire earlier than intended) or moves backward\n(causing timers to take longer to fire than intended).\n\nBut there are platforms that don't provide CLOCK_MONOTONIC, and on\nthose platforms, we should just use CLOCK_REALTIME or gettimeofday(2)\ninstead -- this may cause timers to fire early or late, but lacking\na monotonic time source, it's the best we can do on those platforms.\n\nSigned-off-by: Tamas Pal <folti@balabit.hu>\nSigned-off-by: Balazs Scheidler <bazsi@balabit.hu>\nSigned-off-by: Lennert Buytenhek <buytenh@wantstofly.org>","Balazs Scheidler"],["34c1aff4aa42c89829e3b82a64721ee421becb68","8858498612e3a522354216649776e3032dcb7e5b@wantstofly.org","Don't report POLLHUP conditions to the ->handler_err() handler.\n\nSigned-off-by: Lennert Buytenhek <buytenh@wantstofly.org>","Lennert Buytenhek"]],"repo":"buytenh/ivykis","actor":"buytenh","ref":"refs/heads/master","size":4,"head":"34c1aff4aa42c89829e3b82a64721ee421becb68","actor_gravatar":"8b81b7d9a38632693be4b8b9d496bc68","push_id":29011468}