… | |
… | |
1281 | uint64_t counter = 1; |
1281 | uint64_t counter = 1; |
1282 | write (evfd, &counter, sizeof (uint64_t)); |
1282 | write (evfd, &counter, sizeof (uint64_t)); |
1283 | } |
1283 | } |
1284 | else |
1284 | else |
1285 | #endif |
1285 | #endif |
|
|
1286 | /* win32 people keep sending patches that change this write() to send() */ |
|
|
1287 | /* and then run away. but send() is wrong, it wants a socket handle on win32 */ |
|
|
1288 | /* so when you think this write should be a send instead, please find out */ |
|
|
1289 | /* where your send() is from - it's definitely not the microsoft send, and */ |
|
|
1290 | /* tell me. thank you. */ |
1286 | write (evpipe [1], &dummy, 1); |
1291 | write (evpipe [1], &dummy, 1); |
1287 | |
1292 | |
1288 | errno = old_errno; |
1293 | errno = old_errno; |
1289 | } |
1294 | } |
1290 | } |
1295 | } |
… | |
… | |
1304 | } |
1309 | } |
1305 | else |
1310 | else |
1306 | #endif |
1311 | #endif |
1307 | { |
1312 | { |
1308 | char dummy; |
1313 | char dummy; |
|
|
1314 | /* see discussion in evpipe_write when you think this read should be recv in win32 */ |
1309 | read (evpipe [0], &dummy, 1); |
1315 | read (evpipe [0], &dummy, 1); |
1310 | } |
1316 | } |
1311 | |
1317 | |
1312 | if (sig_pending) |
1318 | if (sig_pending) |
1313 | { |
1319 | { |