similar to: HPUX shared memory creates error

STEENHUYSE VAN DE VELDE Luc wrote: > > While testing the latest releases however we ran into a weird problem > related to semaphores. As soon as we try to do something with samba > HP-UX allocates all available semaphores and other services are having > trouble because of this. E.g. Oracle won't start anymore as it cannot > allocate any semaphores. I tested this on two

Ole.H.Nielsen@fysik.dtu.dk wrote: > > SAMBA grabs ALL available semaphores minus 1 on SunOS 4.1.3, > where the kernel has 60, see /usr/include/sys/sem.h: > #define SEMMNS 60 /* # of semaphores in system */ > > This is a MAJOR PROBLEM to us, since our backup software > (IBM ADSM) also needs available semaphores for the client > part to work. Hence we can

Ole, Semaphores are a very cheap system resource in SunOS 4.1.x. You can easily bump up the max number using adb, without even recompiling the kernel. _seminfo: _seminfo+0 semmap 30 _seminfo+4 semmni 256 _seminfo+8 semmns 1024 _seminfo+0xc semmnu 1024 _seminfo+0x10 semmsl 1024 _seminfo+0x14 semopm 100 _seminfo+0x18 semume 256 _seminfo+0x1c semusz 2064

Phillip.Link@alcatel.fr wrote: > The problem > ----------- > I've been trying to install the latest samba distrib (2.0.5a) on a hpux > 10.20 machine, but the connection times out, apparently because of > shared memory access. > > Trying to make an smbclient connection (or using the windows nt explorer > to connect generates the following log.smb (smbd launched as smbd

Hi all, I have a problem when trying to run my squid-cache with wccp. The problem is that after running for 1 hour the network hangs . I have in the message log "/kernel: xl0: watchdog timeout" and in the squid logs " No buffer space available" The system is dual xeon @500Mhz with 2.5GB of RAM and 10x9.1GB SCSI, FreeBSD 4.9-PRERELEASE from Thu Sep 11 and squid-2.5.STABLE3 build

Hi, I have updated my old 2.4.7 kernel to 2.4.19 using the full download from kernel.org and installed samba-2.2.6 Using my old kernel i can access every share and everything works fine. Using my new kernel also everything works but samba,. i can telnet the system, ftp also works ok, but windows 2k tells me server not found if i try to acces the shares. i think, i forgot something to compile to

I just upgraded to Debian 2.2 and Samba 2.0.7-3, but Samba isn't working. When I try and connect to a share from my windows box, I get a message "The specified computer did not receive your request. Please try again later." when I try to connect as I boot and "Permanent connection not available" if I try and connect later. Here are the messages from my log file. Does

I've just installed Samba on Solaris-8. When i start 'smbd' the following errors appear in the 'log.smb' log file: # tail ../var/log.smb [2000/07/13 13:53:19, 0] locking/shmem_sysv.c:sysv_shm_open(597) ERROR: root did not create the semaphore [2000/07/13 13:53:19, 0] locking/locking.c:locking_init(174) ERROR: Failed to initialise share modes

Hi Folks, I'm new to the list, and am writing because of some trouble I am having. An old version of Samba is involved, and I am not sure that I can upgrade. I am trying to explore the issue further. I am currently using Samba 1.9.18p10 (I can hear the smack of 1,000 hands slapping foreheads now -- please read on). The problem is that the Samba server hangs when I copy a large file (~100

bob@hobbes.dtcc.edu wrote: > > this samba was built on a solaris 2.5 system and was running fine on a > solaris 7 3/99 system. when i installed the solaris 7 5/99 maintenance > update something broke. > > log.smb: > > [1999/08/06 11:04:41, 1] smbd/server.c:main(628) > smbd version 2.0.5a started. > Copyright Andrew Tridgell 1992-1998 > [1999/08/06 11:36:49,

I installed and configured samba 2.0.5a on a rather unstable Sun box on Thursday/Friday last week to link two NT cd writer machines to a filesystem on the E4000. After a bit of wierdness regarding the usernames the NT machines where offering to Samba, and some creative use of a username.map file I got what they wanted set up. The users were happy and 5 minutes of job satisfaction were achieved. I

On 09/03/2015 04:00 AM, Nicolas Thierry-Mieg wrote: > On 09/03/2015 03:04 AM, Robert Nichols wrote: >> In CentOS 6.7, if I start emacs from a terminal session, I always see >> a message, "(emacs:{PID}): Gdk-WARNING **: shmget failed: error 28 (No >> space left on device)" >> >> The message is also logged to .xsession-errors, and that occurs >>

Robert Nichols wrote: > On 09/03/2015 04:00 AM, Nicolas Thierry-Mieg wrote: >> On 09/03/2015 03:04 AM, Robert Nichols wrote: >>> In CentOS 6.7, if I start emacs from a terminal session, I always see >>> a message, "(emacs:{PID}): Gdk-WARNING **: shmget failed: error 28 (No >>> space left on device)" >>> >>> The message is also logged

> This is fixed in CVS. You might consider upgrading to LLVM CVS, > especially if you are interested in looking at performance issues: several > important performance related patches have gone in since LLVM 1.2. OK, now i've really upgraded to CVS, but it looks like state of sources is "not compilable" :( indeed: *************************** Linking llc release executable

I start Samba process smbd and nmbd correctly But smbstatus did not run, it return : # ./smbstatus Samba version 2.0.5a Service uid gid pid machine ---------------------------------------------- ERROR: root did not create the semaphore ERROR: Failed to initialise share modes Can't initialise shared memory - exiting Here is an extract of log.smb : [2001/12/20

I've been having problems installing Samba on AIX 4.32. I have spent well over two weeks on the issue and have not had any major success. I can get samba 1.9 series of source code and binaries to work fine but the new Samba 2.0 series code is causing me problems. I have the following system and problem. I have a H50 with 2 NICs; one is ether and the other is token. I can't seem to browse

At 03:33 AM 11/01/1999 +1100, you wrote: > >From: Hai Nguyen <hhn1@yahoo.com> >To: samba-technical@samba.org, samba@samba.org >Subject: root did not create the semaphore >Message-ID: <19991030210628.3575.rocketmail@web705.mail.yahoo.com> >MIME-Version: 1.0 >Content-Type: text/plain; charset=us-ascii > >Hello, >I am new to samba and need assistance

Hi - I found the "maxusers" defined in meetme.c, but I'm not sure how this value is set. Does anybody know if one can limit the number of users permitted in a meetme conference? I know there's MeetmeCount(), but I'd rather avoid the dialplan logic and just set maxusers instead. Thanks, Noah

What can i do about this... ~~ # smbstatus Can't create or use IPC area. Error was File exists ERROR: Failed to initialise share modes Can't initialise shared memory - exiting In log-uri: Jan 24 07:22:41 lapd smbd[19406]: [2001/01/24 07:22:41, 0] locking/shmem_sysv.c:sysv_shm_open(667) Jan 24 07:22:41 lapd smbd[19406]: Can't create or use IPC area. Error was File exists Jan 24

Hello, I've a problem with Samba version 2.0.6, where smbd does not start from inetd. nmbd starts from inetd and "smbd -D" works fine as well. And I didn't have that problem with 2.0.4b. The following is an extraction of the smb.log, which shows an "read_socket_data: recv failure for 4. Error = Invalid argument" error. Regarding this problem, what is the difference