Custom Query (981 matches)
Results (25 - 27 of 981)
| Ticket | Resolution | Summary | Owner | Reporter |
|---|---|---|---|---|
| #222 | fixed | typo and missing \n" in client/cs_cmdline.C | ||
| Description |
Hi, In changeset 12771 David missed two \n" and made a mistake in the description of --exit_after_finish which should be "exit right after finishing a job" (note: after and not before). See the attached patch. Grüße, Frank |
|||
| #368 | invalid | trouble with the cisco vpn client and boinc on win xp | ||
| Description |
If I have running BOINC with several different projects and start a VPN connection to my university each application hangs / freeze (the progress do not increase). I use BOINC client 5.10.13 and CISCO client 4.8.01.300. If I suspend BOINC while I have an VPN connection and start BOINC after the connection all works right. |
|||
| #1345 | fixed | trickle_deadline_handler does not skip messages when error detected | ||
| Description |
Problem: Because of the hostid check in trickle_deadline_handler.cpp:99 sprintf(buf, " where name='%s' and hostid=%u", task_name, mfh.hostid); and how the handler framework handles such cases the handler will retry the same message again and again if the query fails. In my case it failed because somehow the hostid of the result changed between sending the trickle message and the query by the trickle handler. This was flooding the logfile. Proposed change: mark failed messsages by setting handled=2 and change the purge_trickles.php script to only delete messages with handled=1. This would allow the admin to investigate on the message. Remark: The hostid check was put in place to prevent some kind of DoS Attack by a third party by spamming the server with fake trickle messages. This would mean that we are extending results that are no longer running and would prevent another task to be created. |
|||
