I agree that the way editing log flags is implemented surfaced this problem but it's not what I was trying to say. What I meant is:
When the client starts up, it should first apply options from cc_config.xml and then apply options from command line. This way you can have your normal options in cc_config and easily override them for one run by using command line options. Currently the client does the opposite. It would be necessary to re-apply the options from command line every time the config file is read. Looking a bit more at the code you'd need to store either all of the command line or only options from there somewhere and then apply them in read_config_file() . GUI isn't much of a problem. Client sends the contents of cc_config.xml to the GUI and then writes to cc_config.xml whatever the GUI sends it back. In both directions it's just a blob of text, it's not parsed in client. -Juha On 4 September 2015 at 09:09, David Anderson <[email protected]> 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 >> [email protected] >> 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_alpha mailing list > [email protected] > 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 [email protected] http://lists.ssl.berkeley.edu/mailman/listinfo/boinc_dev To unsubscribe, visit the above URL and (near bottom of page) enter your email address.
