Custom Query (1145 matches)
Results (133 - 135 of 1145)
Ticket | Resolution | Summary | Owner | Reporter |
---|---|---|---|---|
#155 | duplicate | acroread attempts to use CUPS-specific optoins to lpr | broder | |
Description |
acroread seems to sort of half-grok CUPS - well enough to query the library for a list of CUPS printers, but instead of printing through the library, it shells out to lpr. It also passes -o options of one sort or another, which doesn't work currently, because our lpr almost always shells out to mit-lpr, so you get a popup to the effect of: The following error occurred while printing... 'lpr: illegal option 'o' Usage: lpr [-Pprinter@host]] [-A] [-B] [-Cclass] [-Fformat] [-G] [-Jinfo] etc. I'm...not sure if I'm actually interested in investing effort in fixing this, given that the long-term strategy is to actually use CUPS. |
|||
#156 | fixed | Everything should check ATHENA_USER | broder | broder |
Description |
We've established $ATHENA_USER as your Athena username when it's distinct from $USER. debathena-dotfiles will currently set ATHENA_USER=$USER if it's otherwise unset, but I think that the various clients that check $USER should be modified to check $ATHENA_USER first in case debathena-dotfiles isn't installed. |
|||
#163 | fixed | debathena-auto-update should know about apt-release clusterinfo | geofft | broder |
Description |
Soon, hopefully, machines in various Moira clusters around campus will have "production", "proposed", and/or "development" values for the "apt-release" key in clusterinfo. debathena-auto-update should know about that key, and adjust /etc/apt/sources.list.d/debathena.list accordingly when it runs. This allows us to configure cluster machines (and other workstations) to take updates from -proposed and -development without having to ever physically manipulate the machines. |