similar to: Bug or me???

Hello, SORRY IF YOU HAVE ALREADY HAD THIS, BUT I A NOT SURE WHETHER THE LAST POST WORKED... I am trying to install Samba and have started going through the DIAGNOSE.TXT file.. However, I am can not get past step 3, but am getting some really wierd stuff, so I don't know whether it is some sort of bug, or it is me doing something wrong.... I downloaded the latest, samba-2.0.6 from the web

Hello, I am using a clean install Slackware Linux 7.0 which uses Kernel 2.2.13 I just downloaded samba 2.0.6, un-tar'd, cd source, ran the configure script, then: "make", "make install" However, I am having wierd problems and can not ket it working (see earlier post)... Is anyone else using Slackware 7, did it work OK first time, and did you use any special options when

While installing Samba 2.0.6 using 'security=server', I at first used a domain name (whatever.epicentric.com) for the 'password server' parameter, before realizing that it should be the NetBIOS name (WHATEVER). An incorrect value appears to cause a segfault (on Solaris). The workaround is "don't do that then" but thought I'd report it in case other people run

Hello, ** Please reply directly to ian@ichilton.co.uk ** Does anyone use PDQ for printing with Samba? If so, please could you tell me what options to use in smb.conf?? Mainly, what do I use for the printing option? Can I just use: printing = bsd print command = pdq -P%p %s; rm %s Or, can I not use PDQ, because there is no setting for it on the printing parameter??? Thanks! Bye for Now,

Hi, It looks like smbd in Samba 2.0.4a is segfaulting after receiving a SIGTERM signal (kill -TERM <pid of smbd>): [1999/05/18 23:40:46, 1] smbd/server.c:main(621) smbd version 2.0.4a started. Copyright Andrew Tridgell 1992-1998 [1999/05/18 23:40:46, 1] smbd/files.c:file_init(216) file_init: Information only: requested 10000 open files, 1014 are available. [1999/05/18 23:41:11, 0]

Samba: binary kit from samba.org Samba version: 2.0.6 computer: SGI indigo2 with a 250MHz 4400 CPU, 64MB RAM, Irix 6.5.6m me: tarjei.jensen@kvaerner.com It looks like every time smbd spawns, the child process seems to die a horrible death and leave a core file. As a result I am unable to use any netbios services on the machine. The core file which I have examined says that the process died with

Hello. My smbd dies with SIG11. This occurs in 1.9.18p10 as well in 2.0.0beta2. I've read the Samba archive and found the article "Re: 1.9.17p4 - SIGNAL 11 error ??" from Luke and recompiled it with "-g -g". Here the results: After a "smbclient -L localhost" or any other tries to connect to the server the server dies an --- output of "gdb smbd core"

I'm running samba on a SPARC20 running Solaris 2.4. I have been running v2.0.5a successfully for quite some time. I've tried a couple of times to move up to 2.0.6 but there seems to be a problem that I can't diagnose easily. 2.0.6 builds with no problems 2.0.6 installs with no problems 2.0.6 starts up with no problems smbstatus returns correct info with no problems smbclient -L

> I have just upgraded to Samba 2.0.6 and can no longer connect to Samba > shares on my FreeBSD 3.4-RELEASE machine. When I attempt to connect, the > smb.log contains the following information: > > [2000/01/04 17:54:42, 3] libsmb/namequery.c:resolve_lmhosts(566) > resolve_lmhosts: Attempting lmhosts lookup for name > NTWEB2.AIS.MSU.EDU<0x20> > [2000/01/04

> Our site has a RH 6.1 linux box running Samba 2.0.6. It functions quite well I was using 2.0.6 with FreeBSD with Win2K Pro with no problems until today. Domain authentications no longer work, giving me the following errors in the log.<workstation> file: [2000/03/06 10:17:02, 0] libsmb/clientgen.c:attempt_netbios_session_request(3258) [2000/03/06 10:17:02, 0]

Hi All, We have been running samba-1.9.18p10 beautifully for the past year or so. Finally decided to upgrade to samba-2.0.6 and am having no luck. We are using security=server such that the users are using their NT login/password to authenticate. When I test the 2.0.6 installation with smbclient, I get the "protocol negotiation failure" message. Does anyone know what this means? I

Hello all We have experienced some problems with samba recently. People were unable to access their files. Here is the story: [2000/03/02 09:12:26, 1] smbd/service.c:make_connection(535) pdc (192.168.21.210) connect to service Document as user root (uid=0, gid=0) ( pid 1987) [2000/03/02 09:12:51, 0] locking/shmem_sysv.c:sem_change(124) ERROR: sem_change(6,-1) failed (Identifier removed)

Hello, ** Please reply direct to ian@ichilton.co.uk as I am only subscribed to the list in digest mode ** I am trying to compile Samba 2.0.7 on my SGI Indy running IRIX 6.5 I did a: ./configure --with-smbmount (I want smbmount) then, after an hour compiling, it gave this: Compiling client/smbmount.c client/smbmount.c:27: asm/types.h: No such file or directory client/smbmount.c:28:

Hello folks, I'm seeing a couple of things that I can't figure out. Samba version - 2.2.a3 (samba-2.2.0.cvs040920001.tar.bz2 is where the source is built from) PDC is Win2k server Client is Win2k pro Samba share on linux 2.4.1 Security = share I cannot connect at all from clients. If I do a net view from the client to the samba server I get: System error 64 has occurred The

I have read the BUGS.txt file, used 'testparm' (successfully), and run through all the steps in DIAGNOSIS.txt. I don't see any problems that those tools have identified. The BUGS.txt file indicated that INTERNAL ERROR was almost certainly the result of a bug. I'm hopeful I have sent you the information you need. Let me know if there is something more I need to send. What

Hello, I am running a Debian Testin/Unstable system with ii samba 3.0.1-2 a LanManager-like file and printer server fo ii samba-common 3.0.1-2 Samba common files used by both the server a And lately (more or less since the first 3.0 Samba i have been getting a _lot_ of segfaults.. Does someone have any clue as to what the below might be caused by? Isnt SIG11 usually

I realized that my choice of options for grep did not do a very good job of including the last error message before the INTERNAL ERROR. I've included it in this email. Sorry. create_policy_hnd: ERROR: too many handles (1025) on this pipe. [2003/04/21 15:35:21, 0, pid=2798, effective(502, 501), real(0, 0)] rpc_server/srv_lsa_hnd.c:create_policy_hnd(109) create_policy_hnd: ERROR: too many

Dear all, I'm having problem with samba 3.0.23c. The smbd process will crash when I have the following definition for a specific share: [user1] comment = User1 Home Directory path = /u/management/user1 valid users = domain+user1,sher+user2 force user = domain+user1 force group = sher+management read only = no create mask = 0660

On Fri, Jan 16, 2004 at 04:54:12PM -0800, Mike Fedyk wrote: > On Wed, Nov 05, 2003 at 06:15:47PM -0600, Steve Langasek wrote: > > Ok, then, you *must* build debugging-enabled packages by running... :) > > > > The binaries are compiled with debugging turned on -- the debugging > > symbols are stripped out for packaging. > > Package: samba > Version:

I just upgraded to Samba 3.0.2a last week. about mid week I started seeing problems like this in printing to one printer only. Any Ideas what could be wrong?? The Client was Windows 2k sp 4 the server is LINUX 7.3, samba-3.0.2a, lpr Shane [2004/02/29 08:35:45, 0] lib/fault.c:fault_report(36) =============================================================== [2004/02/29 08:35:45, 0]