A feature request mentioned during the user conference was to be able to get notifications when a job sent to nearest has finished printing. There are a whole bunch of generic tools for this, but they rely on the fact that the print queue keeps the job until it is fully printed. For nearest, we complete the job when we've chucked it to the correct queue. So we should investigate if we can get more "normal" behaviour from nearest without making it a system wide mutex, or as a fallback, see if there are any tools we can tweak to understand our odd setup.
