On Sep 3, 2015, at 11:09 PM, David Anderson <da...@ssl.berkeley.edu> wrote: > This is due to bad design in the Manager. > When you change a log flag or an exclusive app, > it should change only that particular XML element, > and shouldn't add a bunch of other stuff.
Actually, this would need to be a change in the client, not the Manager. By convention, the Manager is not allowed to directly read or write the cc_config.xml file (or the global_prefs_override.xml file.) The Manager uses RPCs to get the data associated with these files from the client, and to send the updated values to the client. The client does the actual file I/O. The Manager currently has no way of knowing which XML tags exist in the cc_config.xml file, or even whether or not that file exists. The implementation would need to be done in the client by having it write only those tags whose values are different from the defaults. Cheers, --Charlie On Sep 3, 2015, at 11:09 PM, David Anderson <da...@ssl.berkeley.edu> wrote: > This is due to bad design in the Manager. > When you change a log flag or an exclusive app, > it should change only that particular XML element, > and shouldn't add a bunch of other stuff. > > This is a medium size task. > If someone wants to take it on, or add an issue to Github, feel free. > > -- David > > On 03-Sep-2015 2:06 PM, Juha wrote: >> If the same option, say allow_multiple_clients, is specified both in >> cc_config.xml and on the client's command line, then whatever is in >> cc_config.xml takes precedence. >> >> I think the normal order is: >> >> command line >> environment variables >> config files >> built-in defaults >> >> And how come there was cc_config.xml? Toggled log flags in Manager and >> promptly forgot it. Had to fire up debugger to see what's going on. :[ >> >> -Juha >> _______________________________________________ >> boinc_alpha mailing list >> boinc_al...@ssl.berkeley.edu >> http://lists.ssl.berkeley.edu/mailman/listinfo/boinc_alpha >> To unsubscribe, visit the above URL and >> (near bottom of page) enter your email address. > > _______________________________________________ > boinc_dev mailing list > boinc_dev@ssl.berkeley.edu > http://lists.ssl.berkeley.edu/mailman/listinfo/boinc_dev > To unsubscribe, visit the above URL and > (near bottom of page) enter your email address. > _______________________________________________ boinc_dev mailing list boinc_dev@ssl.berkeley.edu http://lists.ssl.berkeley.edu/mailman/listinfo/boinc_dev To unsubscribe, visit the above URL and (near bottom of page) enter your email address.
