similar to: CentOS 6: Increase shared memory limits permanently

Hi, Anybody have success with postgresql 8.1.3 on a new Intel OS X box? All hints welcome, please! I installed postgres 8.1.3 via darwinports, and everything is great until the initdb step. Initdb fails on shmget saying it couldn''t allocate enough memory (see below). So, I edited /etc/rc and increased kern.sysv.shmmax from 4194304 to 41943040 (4MB to 40MB) After reboot and

On 17/02/16 14:32, Michael H wrote: > Hi, re-posting this with a more appropriate subject for my reply; > >> The easy answer is yes .. glibc requires so many things to be restarted, >> that is the best bet. Or certainly the easiest. >> >> Note: in CentOS 7, there is also a kernel update which is rated as >> Important .. so you should boot to that anyway:

On 2/17/2016 6:39 AM, Michael H wrote: > Some additional information; > > sysctl -a | grep kernel.shm > kernel.shmall = 8650752 > kernel.shmmax = 35433480192 > kernel.shmmni = 4096 > > which corresponds to my /etc/sysctl.conf > kernel.shmmax=35433480192 > kernel.shmall=8650752 > > but contradicts; > ulimit -a > [...] > stack size (kbytes,

Hi List, I'm tuning up a new database server and I'm finding very mixed information online. Here are the default shmmax and shmall from my new system cat /proc/sys/kernel/shmmax 4294967295 cat /proc/sys/kernel/shmall 268435456 SHMALL is close enough to being SHMMAX / 16. Now, everything I'm finding online tells me that SHMALL = SHMMAX / PAGE_SIZE. default page size is 4096.

Hello, I have the following entries in /boot/loader.conf: kern.ipc.shm_use_phys="1" kern.ipc.semmns="500" kern.ipc.semmni="40" kern.ipc.semmap="500" which are set correctly. Unfortunately, the following two entries kern.ipc.shmmax="512000000" kern.ipc.shmall="65526" do not change the corresponding values according to

> The easy answer is yes .. glibc requires so many things to be restarted, > that is the best bet. Or certainly the easiest. > > Note: in CentOS 7, there is also a kernel update which is rated as > Important .. so you should boot to that anyway: > https://lists.centos.org/pipermail/centos-announce/2016-February/021705.html > > Here is a good link to figure out what to

On 02/17/2016 08:10 AM, Michael H wrote: >> The easy answer is yes .. glibc requires so many things to be restarted, >> that is the best bet. Or certainly the easiest. >> >> Note: in CentOS 7, there is also a kernel update which is rated as >> Important .. so you should boot to that anyway: >>

Executing: ip tuntap add vpndrif mode tun return Keepalived errors show when tincd start: Jan 22 23:41:19 Keepalived_vrrp[1999]: Netlink: filter function error Jan 22 23:41:19 Keepalived_healthcheckers[1998]: Netlink: filter function error Jan 22 23:41:19 systemd-sysctl[23246]: Overwriting earlier assignment of kernel/shmmax in file '/etc/sysctl.d/99-sysctl.conf'. Jan 22 23:41:19

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

Hi All, I've been tuning a server recently and just today this has started to appear in my top/htop output. [root at db1 ~]# ps -aux | grep kernel root 1011 0.0 0.0 212048 4532 ? Ss 13:34 0:00 /usr/bin/abrt-watch-log -F BUG: WARNING: at WARNING: CPU: INFO: possible recursive locking detected ernel BUG at list_del corruption list_add corruption do_IRQ: stack overflow: ear stack overflow

we are tried setup CENTOS 4.6 with Informix Dynamic server version 10 UC8 on DELL 6800. The problem we have is while doing bdatabase backup (ontape), we have error happen. I guess the error come from "semaphoe". server semaphore are: # sysctl -a|grep sem kernel.sem = 250 32000 128 128 # sysctl -a|grep shm vm.hugetlb_shm_group = 0 kernel.shmmni = 4096

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, re-posting this with a more appropriate subject for my reply; > The easy answer is yes .. glibc requires so many things to be restarted, > that is the best bet. Or certainly the easiest. > > Note: in CentOS 7, there is also a kernel update which is rated as > Important .. so you should boot to that anyway: >

On 02/17/2016 07:08 AM, Michael H wrote: > On 17/02/16 13:01, Johnny Hughes wrote: >> I normally just let the daily announce post to this list show what >> is available for updates, but there is a CVE (CVE-2015-7547) that >> needs a bit more attention which will be on today's announce list >> of updates. >> >> We released a new glibc yesterday for

On 02/17/2016 08:39 AM, Johnny Hughes wrote: > On 02/17/2016 08:10 AM, Michael H wrote: >>> The easy answer is yes .. glibc requires so many things to be restarted, >>> that is the best bet. Or certainly the easiest. >>> >>> Note: in CentOS 7, there is also a kernel update which is rated as >>> Important .. so you should boot to that anyway:

I get this error starting tincd: tincd -n vpndr -d5 -D tincd 1.0.26 (Jan 22 2016 19:28:17) starting, debug level 5 /dev/net/tun is a Linux tun/tap device (tun mode) Executing script tinc-up System call `getaddrinfo' failed: Name or service not known Terminating Also keepalived return an error when tincd start. Starting as a daemon. Joutnalctl show this: Jan 22 23:14:49 systemd[1]:

On 17/02/16 14:44, Johnny Hughes wrote: > On 02/17/2016 08:39 AM, Johnny Hughes wrote: >> On 02/17/2016 08:10 AM, Michael H wrote: >>>> The easy answer is yes .. glibc requires so many things to be restarted, >>>> that is the best bet. Or certainly the easiest. >>>> >>>> Note: in CentOS 7, there is also a kernel update which is rated as

Hi, After kernel panic I couldn't get gdb work properly. msi$ uname -sr FreeBSD 4.7-RELEASE msi$ gdb -k /usr/src/sys/compile/MSINW/kernel.debug vmcore.0 GNU gdb 4.18 (FreeBSD) Copyright 1998 Free Software Foundation, Inc. GDB is free software, covered by the GNU General Public License, and you are welcome to change it and/or distribute copies of it under certain conditions. Type "show

dear All, I'm facing this routing problem, the setup is actualy part of ltsp, but I think this problem is Centos-specific. The server is a Dell Poweredge R210. The install is standard 6.4, updated. I have one nic facing the public internet: vi /etc/sysconfig/network-scripts/ifcfg-em1 DEVICE=em1 BOOTPROTO=none HWADDR=d4:ae:52:c1:28:2b NM_CONTROLLED=no ONBOOT=yes TYPE=Ethernet

Hello all, I have a very annoying situation (at least at my end). I set up Samba 2.0.5 on a Digital UNIX 4.0F system sitting on a Compaq DS20 server with great success.... until recently. I set up three directory file shares with no problems, when I tried to set up a forth, quite a while after setting up the inital three, I tried to access it from a NT box, I got the message server not found,