Custom Query (1145 matches)


Show under each result:

Results (253 - 255 of 1145)

Ticket Resolution Summary Owner Reporter
#461 fixed pyhesiodfs should pass -o nonempty to fuse andersk

Reported by andersk, 14 years ago.


pyhesiodfs fails to start up on a nonempty /mit.

root@ringworld:/etc/init.d# /usr/bin/pyhesiodfs /mnt
fuse: mountpoint is not empty
fuse: if you are sure this is safe, use the 'nonempty' mount option
Traceback (most recent call last):
  File "/usr/bin/pyhesiodfs", line 226, in <module>
  File "/usr/bin/pyhesiodfs", line 223, in main
  File "/usr/lib/python2.6/dist-packages/", line 713, in main
fuse.FuseError: filesystem initialization failed

From fuse/README:


  Allows mounts over a non-empty file or directory.  By default these
  mounts are rejected (from version 2.3.1) to prevent accidental
  covering up of data, which could for example prevent automatic
#465 fixed come up with a coherent plan for debathena-printing-config geofft

Reported by geofft, 14 years ago.


Right now our lpr wrapper is a descendant of a descendant of a hack, solving lots of little use cases but with no particular overarching intention about what it's doing. While we shouldn't forget about the edge cases we're supporting and break them in a rewrite (cf. #455), it's about time to have a clear design and spec for what it's doing rather than continuing its descent into feature creep.

As I see it the two main issues with the current setup is that user-visible behavior depends on users being aware of whether a queue is CUPS and LPRng and that answering questions about the behavior usually requires looking at the source.

This includes: (some of the following are inspired by TODOs in the current printing-config lpr wrapper)

  • Should we support the traditional LPRng arguments that Athena's used for years, e.g., -Zduplex (ticket #444)? Forever?
  • Should we try to get these arguments upstream somehow, or is a cross-platform Athena lpr script that you can put early in your PATH sufficient? (Or do we not care for non-Athena platforms?)
  • Should the LPROPT environment variable be supported? Currently if you are printing to a CUPS queue, and if passed to lpr can be interpreted purely as CUPS arguments (such as if you just do lpr -Pfoo), then the arguments in LPROPT aren't inserted into the processed command-line arguments (see also  RT:1098339). We could desupport it, or support it all the time.
  • How do you default to double-sided printing, etc., for all queues? In theory LPROPT is an answer, but converting LPRng args to CUPS ones in perpetuity is silly and prevents you from actually specifying default CUPS arguments.
  • Are we keeping LPRng clients installed forever, or at some point will we say that if you want to print to an lpd printer, you should add a CUPS queue, and that Kerberized lpd printing is desupported (unless CUPS grows support for it)? (We can also keep the clients around while making lpr.debathena never call them.)
  • Are we keeping Hesiod pcap entries forever?
  • Are we keeping the "Print to LPR..." gtk backend forever? This saved me last week when some subtle BrowsePolling? bug caused only three faraway printers to show up in the pick list, but this is a config change from upstream and one that I think we intended to be temporary.
  • Can CUPS be made to zephyr (ticket #184)
  • Can CUPS be made to have an equivalent of -Zbanner=?
#467 duplicate Unclean shutdown of reactivate-2 causes time-consuming schroot cleanup jdreed

Reported by jdreed, 14 years ago.


Rebooting an uncleanly shutdown reactivate-2 machine causes it to attempt to recover schroot sessions. Recovery fails because the directory /var/lib/schroot/union/overlay/login-{$uuid} does not exist, but it's still somewhat time consuming to do this on a slower (620, HP) machine. Can we skip this step, since presumably we never care about recovering schroot sessions on cluster machines?

Note: See TracQuery for help on using queries.