[Bug 198351] Re: fusesmb/smbnetfs SIGABORT in getattr() because libsmbclient is not thread safe

[Peter]

For what it is worth I have been using smbnetfs on hardy jaunty and now lucid without problems.  When I started out, on hardy fusesmb was not working, which is why I used smbnetfs. I have just revisited and tried fusesmb again. It does not work on Lucid and I am seeing this.
Running in debug mode I get repeatedly told fusesmb.cache is already running

in .smb there is a fusesmb.cache.pid file that refers to a non-existent process
there is no fusesmb.cache file
so for example on a fully up to date Kubuntu Lucid machine I get this after trying to mount my samba shares with fusesmb (smbnetfs is not yet installed on this machine)

administrator at administrator-laptop:~/.smb$ ls
fusesmb.cache.pid  fusesmb.conf
administrator at administrator-laptop:~/.smb$ cat fusesmb.cache.pid 
2721
administrator at administrator-laptop:~/.smb$ ps -e | grep fuse
 2801 pts/0    00:00:00 fusesmb
administrator at administrator-laptop:~/.smb$ 

smbnetfs continues to work fine so I will not change what I am doing
with that

-- 
fusesmb/smbnetfs SIGABORT in getattr() because libsmbclient is not thread safe
https://bugs.launchpad.net/bugs/198351
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to samba in ubuntu.