Custom Query (1145 matches)
Results (280 - 282 of 1145)
| Ticket | Resolution | Summary | Owner | Reporter |
|---|---|---|---|---|
| #355 | fixed | pyhesiodfs logs every /mit/* symlink creation to syslog | jdreed | geofft |
| Description |
I'm not sure this is necessary, and it seems vaguely undesirable for privacy reasons. |
|||
| #1552 | duplicate | pyhesiodfs install fails because fuse group is gone in jessie | andersk | |
| Description |
The fuse group is gone in jessie ( Debian:733312), so debathena-pyhesiodfs fails to install. Setting up debathena-pyhesiodfs (1.1-0debathena2~debian8.0~0.2) ... adduser: The group `fuse' does not exist. dpkg: error processing package debathena-pyhesiodfs (--configure): subprocess installed post-installation script returned error exit status 1 Duplicate of ticket:1523 |
|||
| #482 | fixed | pyhesiodfs exception on install | geofft | |
| 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. |
|||
