© 2004
Canonical Ltd.
•
Terms of use
•
Data privacy
•
Contact Launchpad Support
•
Blog
•
Careers
•
System status
•
0e1f616
(Get the code!)
Copying my comment from the related question as well: if libdrizzle is waiting for data to arrive, then the socket is likely always writable. If you just wait for everything including writability, you'll never block, and will just spin in select/read burning cpu, which isn't really acceptable behavior in most cases...