[Bug 198351] Re: fusesmb/smbnetfs SIGABORT in getattr() because libsmbclient is not thread safe
** Changed in: debian Status: Fix Committed = Fix Released -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to samba in Ubuntu. https://bugs.launchpad.net/bugs/198351 Title: fusesmb/smbnetfs SIGABORT in getattr() because libsmbclient is not thread safe To manage notifications about this bug go to: https://bugs.launchpad.net/samba/+bug/198351/+subscriptions -- 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
[Bug 198351] Re: fusesmb/smbnetfs SIGABORT in getattr() because libsmbclient is not thread safe
** Changed in: debian Status: New = Fix Committed -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to samba in Ubuntu. https://bugs.launchpad.net/bugs/198351 Title: fusesmb/smbnetfs SIGABORT in getattr() because libsmbclient is not thread safe To manage notifications about this bug go to: https://bugs.launchpad.net/samba/+bug/198351/+subscriptions -- 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
[Bug 198351] Re: fusesmb/smbnetfs SIGABORT in getattr() because libsmbclient is not thread safe
** Changed in: samba Importance: Unknown = High -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to samba in ubuntu. https://bugs.launchpad.net/bugs/198351 Title: fusesmb/smbnetfs SIGABORT in getattr() because libsmbclient is not thread safe -- 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
[Bug 198351] Re: fusesmb/smbnetfs SIGABORT in getattr() because libsmbclient is not thread safe
** Changed in: samba Status: Invalid = Unknown -- 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
[Bug 198351] Re: fusesmb/smbnetfs SIGABORT in getattr() because libsmbclient is not thread safe
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) administra...@administrator-laptop:~/.smb$ ls fusesmb.cache.pid fusesmb.conf administra...@administrator-laptop:~/.smb$ cat fusesmb.cache.pid 2721 administra...@administrator-laptop:~/.smb$ ps -e | grep fuse 2801 pts/000:00:00 fusesmb administra...@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. -- 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
[Bug 198351] Re: fusesmb/smbnetfs SIGABORT in getattr() because libsmbclient is not thread safe
Marking smbnetfs fixed in Lucid per comments 32 and 35 ** Changed in: smbnetfs (Ubuntu) Status: Confirmed = Fix Released -- 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
[Bug 198351] Re: fusesmb/smbnetfs SIGABORT in getattr() because libsmbclient is not thread safe
Marking the samba part as wontfix since libsmbclient is not threadsafe by design and upstream doesn't consider it a bug. ** Changed in: samba (Ubuntu) Status: Confirmed = Won't Fix -- 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
[Bug 198351] Re: fusesmb/smbnetfs SIGABORT in getattr() because libsmbclient is not thread safe
Anyone knows is fusesmb is still affected ? -- 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
[Bug 198351] Re: fusesmb/smbnetfs SIGABORT in getattr() because libsmbclient is not thread safe
Actually Samba upstream does consider the non-threadsafeness of libsmbclient as a bug, it's just that it's going to take a while to fix it :-). We're slowly but surely moving towards getting a thread safe libsmbclient, Can't promise when it will be done, but it is our intent to get there. So at the moment, libsmbclient is not thread safe. So using separate processes in SMBNetFS is the *only* way to safely use libsmbclient, so I'd argue that libsmbclient in this case isn't exactly buggy, but just not working in the way you want :-). When we finally announce libsmbclient is thread-safe, and your threaded code using it breaks, *then* you can call it buggy :-). But not before please - unless you have specific single-threaded bugs you know about and need fixing. But if that is the case please report them to bugzilla.samba.org and we'll fix them ! Jeremy. -- 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
[Bug 198351] Re: fusesmb/smbnetfs SIGABORT in getattr() because libsmbclient is not thread safe
same problems in lucid-current -- 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
[Bug 198351] Re: fusesmb/smbnetfs SIGABORT in getattr() because libsmbclient is not thread safe
adding -s parameter is a workaround for problem in lucid -- 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
Re: [Bug 198351] Re: fusesmb/smbnetfs SIGABORT in getattr() because libsmbclient is not thread safe
On Wed, 10 Mar 2010 21:09:58 - Robert Garshaw launch...@blaze.co.nz wrote: Smbnetfs has been fine for me since I upgraded to karmic. But I'm not sure if I still have any fixes in place. As far as I'm aware it's all stock. This problem was fixed in smbnetfs-0.5.x. Use smbnetfs-0.5.2 or latest git 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: Confirmed Status in “smbnetfs” package in Ubuntu: Confirmed 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
[Bug 198351] Re: fusesmb/smbnetfs SIGABORT in getattr() because libsmbclient is not thread safe
Smbnetfs has been fine for me since I upgraded to karmic. But I'm not sure if I still have any fixes in place. As far as I'm aware it's all stock. -- 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
