I've been troubleshooting a cpu race condition that looks like a problem
that's been around for a while on solaris.
I upgraded to 2.2.5 and was unable to get any handle on what could cause
this, I downgraded to 2.2.2 which was the last one I could remember
working well for us and got this
Hi there.
I wonder, why does a SMB/CIFS client need to perform a session setup
just to see the list of machines in a workgroup?
I am having some problems with tracing some CIFS code, and at least
Windows XP clients seem to try to do a session setup when just
double-clicking on the name of a
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
I was wrong. When setting a drop rule it just gets stuck. And after
removing the drop rule, smbd does not recover. The smbd panic occurs
when the domain controller is rebooted. In this case smbd does not
recover, too.
Today I added a route
[EMAIL PROTECTED] wrote:
I really can't see what's going wrong. I can still not reproduce the
crash. Could you provide *exact* steps (kernel version, routing table,
ip addresses, etc) to reproduce this with latest 2.2 CVS code? To get
the latest 2.2 cvs, see
we are using smbd 2.0.7 and we are getting the error messages from the
var/log below.
users are getting intermittent connection errors and we've been looking at
the network also for potential problems. these error messages appear to
indicate some shared memory exhaustion when coupled with the
This affects 3.0alpha19 and all previous versions of pam_winbind.so
AFAICS
Long running PAM clients can cause PAM to repeatedly load and unload
pam_winbind.so. When this happens the client application will leak
file descriptors if a request was made to winbindd while the library
was loaded.
On Thu, Aug 29, 2002 at 07:49:22AM -0400, [EMAIL PROTECTED] wrote about 'Re: File
descriptor leak in pam_winbind.so':
On Thu, Aug 29, 2002 at 05:44:51PM +0100, Paul Flinders wrote:
return retval;
+ }
+
+ void __attribute__ ((destructor)) unload ()
+ {
+ /* Make sure socket
On Thu, 29 Aug 2002, ian j hart wrote:
David W. Chapman Jr. wrote:
This is probably something that the samba people need to see so it can be fixed if
it hasn't already.
The first thing I tried failed.
anaonymous listing
alpha# smbclient -L //alpha
added interface
MCCALL,DON (HP-USA,ex1) wrote:
Hi Ian,
Problem is that %g macro cannot be expanded in smb.conf until AFTER a
tconnX has
happened - this means in effect that you can only use %g in share/service
definitions.
In the global section (where you would define your logon script, you would
have
Seems the number of extra bytes matches the number of bytes in the share
name.
In the example below there are 3 extra words (not 4 as stated) as there
are 3 characters in the share name: ku-ru-ma
Longer share names produce more extra byte pairs..
-Michael
Michael Cuff wrote:
Urban, List,
10 matches
Mail list logo