Custom Query (22 matches)

As we add more features to Gutenbach, there are many things that need to be able to access the queue data -- client scripts, the gutenbach-queue package, and the web interface. It is better if this information is stored in a database somewhere, and is updated periodically, instead of polling CUPS every single time.

There should be a default gutenbach queue for the clients, e.g.:

gbr *.mp3

Should print to whatever the default queue is (say, sipbmp3). If someone wants to use a different queue, they can specify it:

gbr -Ppikamp3 *.mp3

There should be a utility in gutenbach-client-config to specify what the default printer is, e.g.:

gutenbach-client-config -D sipbmp3

When the Purge-Jobs command is sent, the jobs are removed, but the current mplayer instance continues playing (this is because a SIGKILL is sent instead of a SIGTERM, so it kills the parent process but not the child process). This unfortunately leads to jobs being played over each other when the CUPS server restarts. We could do something like "make sure there aren't other mplayer process running when a job starts", but that feels hacky. This might be a thing we need to change upstream.