Description of problem: A signal is currently used to tell ccsd to update a config file. This has a number of limitations: 1. signals are asynchornous, making it hard to error results 2. Although I believe most issues have been worked out, signals can be recieved at any time, making the code more complex because it has to do various forms of locking to ensure that processing doesn't happen while things are changing The code complexities and various hacks to do meaningful error reporting should be replaced by a more eligant solution. That solution involves ccs_tool taking an update file and sending it to ccsd for processing. Because a sizeable amount of code will have to be changed to facilitate this, it may not be advisable to change the code so close to a release.
update now uses socket to communicate with ccsd to do updates rather than signals.