INTERNAL_ERROR: Signal 11 on 6076 (2.2.3a)
lib.fault.c:fault_report(41)
I am getting the above error in the logs. What gives?
I have turned oplocks off completely. There are no oplock errors.
What does this error mean? And how do I fix it?
I am running Redhat 7.2 and 2.2.3a
Thanks.
--
To
There is a parameter in the smb.conf file that you can use to feed it the
correct space left.
I can't remember what it is, but if you search for drive space in the doc
for smb.conf you will find it.
-Original Message-
From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]]On
Behalf Of [EMAIL
There is a registry setting that you need to make. Look in the
documentation.
You do NOT need to use unencrypted passwords.
-Original Message-
From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]]On
Behalf Of Danny G Smith
Sent: Monday, June 03, 2002 10:22 AM
To: [EMAIL PROTECTED]
Subject:
I have samba working fine. It even prints ok.
The problem is that Windows cannot see the print jobs in the spooler on the
Linux box.
I am using RedHat 7.2 with a bunch of versions of Samba including 2.2.3a. I
am also using the default lpd spooler and settings are in /etc/printcap
printing=bsd
I have a samba 2.2.3a server running on Red Hat 7.2
There are several normal shares that are ok.
I have one share on the samba box that is actually smbmounted from a Win2K
machine. This share seems to be giving me lots of errors. It seems to work
fine though. On at least one instance the smb
I can move the files since they are needed on the other
server. But, I will look into it.
Thanks.
-Original Message-
From: Urban Widmark [mailto:[EMAIL PROTECTED]]
Sent: Monday, May 13, 2002 1:14 PM
To: Sanjiv Bawa
Cc: [EMAIL PROTECTED]
Subject: Re: [Samba] Lock file problems? smb_open
This is the most ludicrous thing I have ever heard. How on earth are they
going to prove that someone ever read something that was publicly available.
Especially when SMB is such a widely understood protocol.
I don't think this is targeted towards samba per se, as much as microsofts
huge
There
is a registry setting that you are missing. Look in the docs. Or check the
samba.org wesite for it.
-Original Message-From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED]]On Behalf Of Guillermo
GomezSent: Thursday, April 11, 2002 9:35 AMTo:
[EMAIL PROTECTED]Subject:
Can you try turning off all oplocks altogether.
kernel oplocks
level2 oplocks
oplocks
should all be no.
Then see if you have the problem. They recently discovered another bug in
oplock code which is due to be fixed in the next version.
Pls. do provide an update. I am very interested in this
