Ticket #482 (closed defect: fixed)
pyhesiodfs exception on install
Reported by: | geofft | Owned by: | |
---|---|---|---|
Priority: | low | Milestone: | The Distant Future |
Component: | -- | Keywords: | |
Cc: | Fixed in version: | ||
Upstream bug: |
Description
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.
Change History
comment:1 Changed 15 years ago by jdreed
- Priority changed from major to minor
- Milestone set to The Distant Future
comment:2 Changed 12 years ago by jdreed
So, the patch is easy, but should pyHesiodFS return non-zero under that case? I think it should, but then we have to catch that in the postinst, right?