VFS: smbd hangs when VFS module is linked against pthread lib

Rainer Link link at foo.fh-furtwangen.de
Mon Dec 1 14:00:45 GMT 2003


Hi,

are any issues known when a VFS module is linked against libpthread?
vscan-clamav.so is linked against libclamav (lib for scanning files
with Clam AV). 

# ldd vscan-clamav.so
        libclamav.so.1 => /usr/local/lib/libclamav.so.1 (0x40017000)
        libmagic.so.1 => /usr/local/lib/libmagic.so.1 (0x40035000)
        libc.so.6 => /lib/libc.so.6 (0x40041000)
        libz.so.1 => /lib/libz.so.1 (0x40177000)
        libbz2.so.1 => /usr/lib/libbz2.so.1 (0x40186000)
        libgmp.so.3 => /usr/lib/libgmp.so.3 (0x40195000)
        libpthread.so.0 => /lib/libpthread.so.0 (0x401c4000)
        /lib/ld-linux.so.2 => /lib/ld-linux.so.2 (0x80000000)

# ldd /usr/local/lib/libclamav.so.1
        libz.so.1 => /lib/libz.so.1 (0x4002b000)
        libbz2.so.1 => /usr/lib/libbz2.so.1 (0x4003b000)
        libgmp.so.3 => /usr/lib/libgmp.so.3 (0x4004a000)
        libpthread.so.0 => /lib/libpthread.so.0 (0x40079000)
        libc.so.6 => /lib/libc.so.6 (0x400c9000)
        /lib/ld-linux.so.2 => /lib/ld-linux.so.2 (0x80000000)

Actually, when smbd loads the VFS module it simply hangs (can only
be killed with kill -9). I've attached a log snippet (debug level = 10),
the last output is:

[2003/09/20 22:27:09, 3] smbd/vfs.c:vfs_init_default(201)
  Initialising default vfs hooks
[2003/09/20 22:27:09, 3] smbd/vfs.c:vfs_init_custom(227)
  Initialising custom vfs hooks from [vscan-clamav]
[2003/09/20 22:27:09, 5] lib/module.c:smb_probe_module(102)
  Probing module 'vscan-clamav'
[2003/09/20 22:27:09, 5] lib/module.c:smb_probe_module(113)
  Probing module 'vscan-clamav': Trying to load from
/usr/local/samba/lib/v
fs/vscan-clamav.so
[2003/09/20 22:27:09, 5] smbd/vfs.c:smb_register_vfs(191)
  Successfully added vfs backend 'vscan-clamav'


(please ignore the date/time stamp, I did it on a test maschine
which obviously has not the correct date ... ;))

Tested with Samba 3.0.0 and Samba 2.2.8a (log snippet is from
3.0). It might be an issue of mine, and not Samba, of course, but
I currently don't know what I've might have done wrong.

Any hints really appreciated. Thanks.

Btw, is there any prefered email address to which updates
for samba-doc should be send?

best regards,
Rainer Link

-------------- next part --------------
A non-text attachment was scrubbed...
Name: log.smbd.gz
Type: application/x-gzip
Size: 7603 bytes
Desc: not available
Url : http://lists.samba.org/archive/samba-technical/attachments/20031201/47bbf201/log.smbd.bin


More information about the samba-technical mailing list