Bug#296684: libsmbclient: prints out extensive debugging

2005-02-23 Thread David Gerber
Package: libsmbclient Version: 3.0.10-1 Severity: important libsmbclient prints out debugging, like: write_socket(3,45)A-V: -0.032 ct: -0.023 741/741 5% 1% 23.2% 2 0 write_socket(3,45) wrote 45 got smb length of 35 size=35 and so on.. Tested building mplayer with smbclient support. When I try

Bug#296684: libsmbclient: prints out extensive debugging

2005-02-23 Thread Andrew Bartlett
On Thu, 2005-02-24 at 00:33 +0100, David Gerber wrote: Package: libsmbclient Version: 3.0.10-1 Severity: important libsmbclient prints out debugging, like: write_socket(3,45)A-V: -0.032 ct: -0.023 741/741 5% 1% 23.2% 2 0 write_socket(3,45) wrote 45 got smb length of 35 size=35 and

Bug#296684: libsmbclient: prints out extensive debugging

2005-02-23 Thread Andrew Bartlett
On Thu, 2005-02-24 at 03:46 +0100, David Gerber wrote: On Thursday 24 February 2005 00:42, Andrew Bartlett wrote: This is controlled by your Samba debug level, just as for smbclient. Right, I get: which suggests the default debug level is not 0, but: I think it's actually 1. In any

Bug#296684: libsmbclient: prints out extensive debugging

2005-02-23 Thread David Gerber
On Thu, 2005-02-24 at 14:31 +1100, Andrew Bartlett wrote: In any case, it may be that your app is setting the high debug level - I think they can control that. int smbc_init(smbc_get_auth_data_fn fn, int debug); and mplayer uses: err = smbc_init(smb_auth_fn, 10); So it's mplayer indeed.