Custom Query (981 matches)
Results (34 - 36 of 981)
| Ticket | Resolution | Summary | Owner | Reporter |
|---|---|---|---|---|
| #1144 | fixed | 6.12.35 on OS X 10.6.8 is leaking file descriptors | ||
| Description |
The file descriptor acquired to open a slot directory is not always closed. They slowly accumulate until the boinc client exits or in some cases hangs. |
|||
| #746 | fixed | 6.x sorting by head column broken | ||
| Description |
In 5.x I could sort the tasks by the head column in the client manager. In 6.x (using Windows Vista SP1) I cannot. |
|||
| #230 | fixed | 64-bit Linux client fails to connect via HTTPS | ||
| Description |
Running 64-bit Linux client 5.9.11 on 64-bit Ubuntu 7.04 system, connecting to the net via a proxy. When trying to attach to the Worldcommunitygrid project, my system logs an error: Sun May 27 20:45:22 2007||[http_debug] [ID#32] info: SSLv2, Client hello (1): Sun May 27 20:45:22 2007||[http_debug] [ID#32] info: error:140770FC:SSL routines:SSL23_GET_SERVER_HELLO:unknown protocol Sun May 27 20:45:22 2007||[http_debug] [ID#32] info: Expire cleared Sun May 27 20:45:22 2007||[http_debug] [ID#32] info: Closing connection #0 Sun May 27 20:45:22 2007||[http_debug] HTTP error: SSL connect error Someone more familiar with HTTPS suggested that the error might have something to do with how the SSL version is being specified (i.e., by the boinc client). Anyway, I was able to successfully attach (through the same proxy) to the WCG project on a (different) system running the 32-bit Linux client 5.10.0. That says to me that my WCG account, and my proxy, are working properly -- leaving the 64-bit client as the probable cause of my HTTPS connect problem. |
|||
