#613 closed Defect (fixed)
BOINC network/cpu times
Reported by: | Ageless | Owned by: | davea |
---|---|---|---|
Priority: | Minor | Milestone: | Undetermined |
Component: | Client - Daemon | Version: | 5.10.45 |
Keywords: | Cc: |
Description (last modified by )
As reported by Markj at the BOINC Dev forums:
When I set the "network usage allowed" times they don't seem to work with certain combinations. In boingmgr -> advanced -> preferences and click on the network usage tab (also does this for processor usage). Select time examples as below, click the okay button. Reselect and they have changed. 06:20/22:20 becomes 06:19/22:19. 06:35/22:35 becomes 06:34/22:34. 06:50/22:50 becomes 06:49/22:49. The times are stored in decimal, when they are converted back to a time they are not shown correctly. 06:20 is stored as 6.333333 and when it converts from decimal back to a time it stuffs them up (ie .333333 x 60 mins = 19.999998) so it shows as 06:19. See global_pref_override.xml exerpt below. I have seen this using BOINC versions 5.10.30 and 5.10.45 under Windows. <global_preferences> <run_on_batteries>0</run_on_batteries> <run_if_user_active>0</run_if_user_active> <idle_time_to_run>3.000000</idle_time_to_run> <start_hour>0.000000</start_hour> <end_hour>0.000000</end_hour> <net_start_hour>6.333333</net_start_hour> <net_end_hour>22.333333</net_end_hour>
Change History (8)
comment:1 Changed 17 years ago by
Description: | modified (diff) |
---|
comment:2 follow-up: 3 Changed 17 years ago by
comment:3 Changed 17 years ago by
Replying to Nicolas:
Ugh, it should be stored as hours*60+minutes.
Actually, I take that back. It should be stored as a ISO 8601 time, instead of a number. XML formats shouldn't be 1:1 mappings of the internal structures.
comment:6 Changed 16 years ago by
Milestone: | 6.6 → Undetermined |
---|
comment:7 Changed 16 years ago by
Resolution: | → fixed |
---|---|
Status: | new → closed |
comment:8 Changed 16 years ago by
Note: See
TracTickets for help on using
tickets.
Ugh, it should be stored as hours*60+minutes. But I don't think that can be changed without breaking compatibility...