From owner-freebsd-questions Sat Aug 26 13:56: 6 2000 Delivered-To: freebsd-questions@freebsd.org Received: from pop.hccnet.nl (pop.hccnet.nl [193.172.127.94]) by hub.freebsd.org (Postfix) with ESMTP id 2001737B43E for ; Sat, 26 Aug 2000 13:55:55 -0700 (PDT) Received: from parmenides.utp.net by pop.hccnet.nl via uds41-115.dial.hccnet.nl [193.173.115.41] with ESMTP id WAA17960 (8.8.5/1.13); Sat, 26 Aug 2000 22:55:53 +0200 (MET DST) Received: from localhost (janko@localhost) by parmenides.utp.net (8.9.3/8.9.3) with ESMTP id WAA00392; Sat, 26 Aug 2000 22:57:28 GMT (envelope-from janko@compuserve.com) X-Authentication-Warning: parmenides.utp.net: janko owned process doing -bs Date: Sat, 26 Aug 2000 22:57:28 +0000 (GMT) From: Janko van Roosmalen X-Sender: janko@parmenides.utp.net To: David Lebel Cc: freebsd-questions@FreeBSD.ORG Subject: Re: problems with Samba 2.0.7... In-Reply-To: <20000826104107.A1097@lebel.org> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-questions@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG If you run "top" how much free memory do you have? Samba starts/launches a new child process for each connection. I am rather new to FreeBSD but I compiled a custom kernel and saw that the GENERIC kernel has the following options: # This provides support for System V shared memory and message queues. # options SYSVSHM options SYSVMSG options SYSVSEM You did not happen to comment these out? The error message complains about "sysv_shm". If this shot in the dark does not work, you will have to call in the specialists...... Janko van Roosmalen - Holland On Sat, 26 Aug 2000, David Lebel wrote: > > Hello, > > I have some problems with Samba 2.0.7 on my FreeBSD 4.1-STABLE > machine. When I reboot, I'm able to connect using a Windows machine > (or locally from smbclient), but after some times, I'm no longer able > to connect and I get the following error in my log.smb file: > > ---cut--- > [2000/08/26 09:56:26, 0] locking/shmem_sysv.c:sysv_shm_open(667) > Can't create or use IPC area. Error was Cannot allocate memory > [2000/08/26 09:56:26, 0] locking/locking.c:locking_init(174) > ERROR: Failed to initialise share modes > ---cut--- > > Then, I have to reboot to be able to access again the machine. I > never got this kind of problems before on other architectures (like > Linux or Solaris). Is there something I could do to solve this issue? > > Thanks! > > Ciao, > ...David > > -- > // david lebel // nobiaze' Inc. > // http://www.lebel.org/ // http://www.nobiaze.com/ > // pgp: 3633 6999 D47E 73ED 099F // vox: (514) 943.3045 > 4341 08A4 8E48 EF56 61D1 // fax: (514) 938.8881 > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-questions" in the body of the message > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-questions" in the body of the message