~steering/inspircd++.git/src/socketengines/socketengine_kqueue.cpp, branch v3.17.1 Unnamed repository; edit this file 'description' to name the repository. https://www.cgit.space/~steering/inspircd++.git/atom/src/socketengines/socketengine_kqueue.cpp?h=v3.17.1 2022-12-30T11:31:28Z Update copyright headers. 2022-12-30T11:31:28Z InspIRCd Robot 2022-12-30T11:31:28Z urn:sha1:2b810b412aeee2d9c79d97fa54a80e317981a6d8 Update copyright headers. 2020-01-11T22:14:43Z InspIRCd Robot 2020-01-11T22:02:47Z urn:sha1:aa692dc1039b63deef7886e914ec499abe7facaf Tweak the workaround for NetBSD's kqueue using intptr_t for udata. 2019-10-05T19:35:09Z Peter Powell 2019-10-05T19:29:53Z urn:sha1:b9c1f4a2e8aa8d8892ae11d1570dda6341a77417 Thanks to @niacat for getting this fixed upstream. Work around NetBSD's EV_SET using intptr_t instead of void*. 2019-05-03T14:44:59Z Peter Powell 2019-05-03T14:37:25Z urn:sha1:0c992c5a3d6b30a6b14adf3181bf0b1e1fdeab48 Reported by @ensra. Deduplicate error handling in the socket engines. 2017-10-22T18:45:05Z Peter Powell 2017-10-22T02:10:48Z urn:sha1:63e300ed082b82530ad5ae0949f45686746b7c9b Convert GetMaxFds() to size_t and deduplicate setting code. 2017-10-22T18:44:45Z Peter Powell 2017-10-22T01:27:25Z urn:sha1:b1098712771ab823042fcf8614a706c76c2ff401 Improve and centralize socket engine event counters. 2017-07-11T12:22:02Z Robin Burchell 2017-03-22T16:59:08Z urn:sha1:8e8b0719bf58e2d875c06698f86377189da87e16 The write counters were close to useless because they were only incremented on a write "event" which is only triggered when writing would block. Read handling was a little more useful in that all reads must happen through the socket engine, so these were happening at the correct time, but we can clean this up by doing it in the SE itself rather than each platform port. This means that both read and write events are now easily and usefully defined as "a syscall of either read or write was attempted". We also count empty read and write events as being an event, because they still were an attempt to poll a socket in some way. This may help to identify "bad" code which is repeatedly trying to read a socket for some reason. Lastly, we check for failed read/write calls, and log them as an error event. A lot of the time, this is how sockets are determined as being disconnected (ie. at read/write time). While we're at it, split Update() in two to make the calls more self-describing. This has no real impact since only one call is made at a time anyway. Dispatch EventHandler events to dedicated virtual functions 2015-04-12T14:20:13Z Attila Molnar 2015-04-12T14:20:13Z urn:sha1:612384b3d46d06eea6fd71ee6dc60471d0f9e3d1 Remove enum EventType Kill needless #includes in source files 2014-06-14T13:30:14Z Attila Molnar 2014-06-14T13:30:14Z urn:sha1:82435b6fa8805baa65e04a582f3e4a2c84237f73 Change the number reported by SocketEngine::GetMaxFds() to be informal 2014-06-07T11:47:26Z Attila Molnar 2014-06-07T11:47:26Z urn:sha1:5a6fd54f8fd217232f98804431928609580742bc Do not exit if we can't determine it