Displaying 5 results from an estimated 5 matches similar to: "Fwd: Segfault in Samba"
2007 Aug 06
1
File locking issue
I have a client with an older server that is running into a weird file
locking problem.
The server is running FC2, samba 3.0.7 and kernel 2.6.10.
They have recently installed AutoDesk Revit, which is apparently some
sort of collaborative design software. Revit keeps a central repository
and then allows different clients to access it.
What is happening is that only the person who created the
2004 Jul 05
3
2.2.3a connection failure from XP to 10.3.4
Hello from a neophyte!
Is there a diagnostic programme which can be run to determine if there
are any faults in Samba 2.2.3a?
I cannot connect from Win XP to my rev/b iMac (suddenly, maybe 'upgrade'
to 10.3.4 had some effect) and the smb crashlog (shown below) has a pile
of stuff which is incomprehensible to me.
Secondly, how does one upgrade to another version of Samba and is this
2004 Sep 05
1
Segfault in Samba
Hi!
My Samba setup broke after upgrading Samba from 3.0.5-1 to 3.0.6-3 using
Debian apt-get upgrade. It seems to me, that the problems lies within
winbind. Any help would be appreciated!
--
Pirkka
> The Samba 'panic action' script, /usr/share/samba/panic-action,
> was called for pid 8012 (/usr/sbin/smbd).
>
> Below is a backtrace for this process generated with gdb, which
2005 Oct 11
2
Samba segment faulting - unknown cause
Hello,
Recently our Samba server has started segment faulting. It happens occasionally, but is often enough to cause disruption.
People notice thier network drives freeze, I am unsure of the cause of the segment fault, and have no experience debugging backtraces.
Can anoyone lend a hand?
We are running Samba as a primary domain controller with an Openldap backend on another server, both on
1998 Apr 16
2
Problem with visual C++ and samba
We are having a problem with Microsoft visual C++ compiling source
code maintained on a samba server. Occasionaly the compiler reports
that it cant open the file vc50.pch. The samba server is running on a
freebsd box. Taking a look at the log files it looks like when the
operation fails the server is processing the command
open (vc50.pch for exclusive use
write
setattrE
write
open (vc50.pch