6.10.54: Unterschied zwischen den Versionen
Zur Navigation springen
Zur Suche springen
(Die Seite wurde neu angelegt: „ Zur Übersicht * client: enable bandwidth quota limit only if both #MB and #days are nonzero. * client: fix memory leak“) |
Keine Bearbeitungszusammenfassung |
||
Zeile 3: | Zeile 3: | ||
* client: enable bandwidth quota limit only if both #MB and #days are nonzero. | * client: enable bandwidth quota limit only if both #MB and #days are nonzero. | ||
* client: fix memory leak | * client: fix memory leak | ||
* client: on resume from net bandwidth quota suspend, apply same random backoff to all transfers. | |||
* client: when changing ncpus via config file, don't modify host_info.p_ncpus | |||
* client: show effective #CPUs separately from physical # | |||
* client: clear config before rereading config file. This means that, e.g. if you remove <ncpus> it will revert to the actual number. However, it also means that any config params set via command line will be overridden. | |||
* client: fix crashing bug. Deleting records in ~COPROCS() was bad, since we copy HOST_INFO to APP_INIT_DATA, leading to a double deletion. |
Aktuelle Version vom 12. Mai 2010, 21:31 Uhr
- client: enable bandwidth quota limit only if both #MB and #days are nonzero.
- client: fix memory leak
- client: on resume from net bandwidth quota suspend, apply same random backoff to all transfers.
- client: when changing ncpus via config file, don't modify host_info.p_ncpus
- client: show effective #CPUs separately from physical #
- client: clear config before rereading config file. This means that, e.g. if you remove <ncpus> it will revert to the actual number. However, it also means that any config params set via command line will be overridden.
- client: fix crashing bug. Deleting records in ~COPROCS() was bad, since we copy HOST_INFO to APP_INIT_DATA, leading to a double deletion.