2010/3/18 Thierry Carrez <thierry.car...@ubuntu.com>: > Anyone knows is fusesmb is still affected ?
Sure. The are only two way to avoid this problem: * single thread application * make libsmbclient threadsafe. SMBNetFS-0.5.x uses several single thread child processes to communicate with samba (and isolate buggy libsmbclient code from the rest of smbnetfs). It was done to get better performance and stability. Mikhail Kshevetskiy > -- > 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 subscribed to > smbnetfs in ubuntu. > > Status in Samba: Invalid > Status in “fusesmb” package in Ubuntu: Confirmed > Status in “samba” package in Ubuntu: Won't Fix > Status in “smbnetfs” package in Ubuntu: Fix Released > Status in Debian GNU/Linux: New > > Bug description: > Installed and enabled fusesmb Just like i have done in the past , following > the FuseSmb wiki page. However no shares or workgroups are shown now under > hardy. > As the root user, a 'ls -l' of the Mounted fusesmb point gives the odd output > of. > > ls -l > > drwxr-xr-x 2 willis willis 4096 2008-02-16 07:30 Music > d????????? ? ? ? ? ? Network > > as a user ls -l gives . > > drwxr-xr-x 2 willis willis 4096 2008-02-16 07:30 Music > drwxr-xr-x 3 willis willis 4096 2008-03-04 08:10 Network > > > the fusesmb -d option (for debugging) is not really giving any info as to > what is failing. > > Aparently related to > https://bugs.launchpad.net/ubuntu/+source/fusesmb/+bug/157494 > > fusesmb Installed: 0.8.7-1 > > > -- 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. -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
