Custom Query (1145 matches)

Reported by geofft, 15 years ago.

I installed debathena-afs-config on a stock* Karmic live CD, and in the setup process, pyhesiodfs crashed and generated a file in /var/crash. The non-irrelevant portions of that file are:

PythonArgs: ['/usr/bin/pyhesiodfs', '-f', '/mit', '-o', 'nonempty']
Traceback:
 Traceback (most recent call last):
   File "/usr/bin/pyhesiodfs", line 226, in <module>
     main()
   File "/usr/bin/pyhesiodfs", line 223, in main
     server.main()
   File "/usr/lib/python2.6/dist-packages/fuse.py", line 754, in main
     main(**d)
 FuseError: filesystem initialization failed

It would be great to catch the error and deal; it would also be okay not to make an entry in /var/crash and pop up an alert icon in my tray.

*Okay, I also installed debathena-ssh-config in advance and then loop-mounted an ext2 disk image from /tmp to /var/cache/openafs so I wouldn't have to deal with memcache. But that worked fine and isn't relevant.

Reported by broder, 15 years ago.

Right now, if anything triggers a dpkg conffile conflict, auto-update will hang indefinitely. Not the best failure mode.

On cluster machines, since we are the sysadmin, we should be passing -o Dpkg::Options::=--force-confnew to aptitude.

Reported by geofft, 15 years ago.

We have libfuse-dev and the fuse kernel module and all the other fun stuff 6.824 wants; someone should quickly double-check that they realize this and aren't telling students to use the sketchy sketchy Athena 9 installer