Skip site navigation (1) Skip section navigation (2)

Re: looks like apple fixed /etc/rc

From: Theodore Petrosky <tedpet5(at)yahoo(dot)com>
To: "Jim C(dot) Nasby" <decibel(at)decibel(dot)org>
Cc: pgsql -bugs <pgsql-bugs(at)postgresql(dot)org>
Subject: Re: looks like apple fixed /etc/rc
Date: 2005-04-30 18:42:36
Message-ID: 20050430184236.39240.qmail@web41010.mail.yahoo.com (view raw or flat)
Thread:
Lists: pgsql-bugs
Jim,

this is copied from /etc/rc...
\
if [ -f /etc/sysctl.conf ]; then
        awk '{ if (!index($1, "#") && index($1, "="))
print $1 }' < /etc/sysctl.conf | while read
        do
                sysctl -w ${REPLY}
        done   
fi

sysctl -w kern.sysv.shmmax=4194304
sysctl -w kern.sysv.shmmin=1
sysctl -w kern.sysv.shmmni=32
sysctl -w kern.sysv.shmseg=8
sysctl -w kern.sysv.shmall=1024


this is copied and pasted from my /etc/sysctl.conf:
kern.sysv.shmmax=33554432
kern.sysv.shmmin=1
kern.sysv.shmmni=32
kern.sysv.shmseg=8
kern.sysv.shmall=65536

here  is my responce from the terminal

 postgres$ sysctl kern.sysv.shmmax
kern.sysv.shmmax: 33554432

 postgres$ sysctl kern.sysv.shmall
kern.sysv.shmall: 65536


It looks like my settings in /etc/sysctl.conf are
sticking just fine


Ted

--- "Jim C. Nasby" <decibel(at)decibel(dot)org> wrote:

> decibel(at)phonebook(dot)1[12:31]~:1%sysctl
> kern.sysv.shmmax
> kern.sysv.shmmax: 1024000000
> 
> It wouldn't surprise me at all if there was some
> other black magic at
> work here. What I do know is that I had to comment
> out the sysctl line
> in my /etc/rc to get that value to stick. I didn't
> make notes during my
> testing (booting to single user), but if memory
> serves I was able to do
> this:
> 
> sysctl -w kern.sysv.shmmax=1024000000 #works
> sysctl -w kern.sysv.shmmax=24000000 #also works
> sysctl -w kern.sysv.shmmax=1024000000 #doesn't work
> 
> What I do know for a fact is that after putting a
> sleep in /etc/rc after
> the sysctl's I was able to verify that my setting
> from /etc/sysctl.conf
> was being applied, but that it was then being
> over-ridden by the setting
> in /etc/rc. Unfortunately, since I only have one mac
> and it's my primary
> computer and testing this requires a number of
> reboots I'm not keen on
> spending more time experimenting with it, but if
> someone has ideas on a
> more elegant fix I'm all ears.
> 
> I provided apple feedback about this, btw. Hopefully
> they'll fix it at
> some point.
> 
> On Sat, Apr 30, 2005 at 07:00:57AM -0700, Theodore
> Petrosky wrote:
> > Jim,
> > 
> > I didn't understand your comment 
> > 
> > "It appears that you can shrink shmmax but not
> expand
> > it."
> > 
> > I did not comment out the  kern.sysv.shmmax line
> and
> > it appears that my larger setting is sticking. Or
> is
> > it? What is that command to return the currrnt
> values
> > from the terminal?
> > 
> > Ted
> > 
> > --- "Jim C. Nasby" <decibel(at)decibel(dot)org> wrote:
> > > That's interesting. On my powerbook, I had to
> > > comment out the sysctl -w
> > > kern.sysv.shmmax line in /etc/rc. It appears
> that
> > > you can shrink shmmax
> > > but not expand it. This meant that it would
> properly
> > > set it based on
> > > /etc/syscttl.conf, but that (large) setting
> would
> > > then be over-written
> > > by the subsiquent sysctl -w.
> > > 
> > > On Fri, Apr 29, 2005 at 09:39:55AM -0700,
> Theodore
> > > Petrosky wrote:
> > > > I just updated to 10.3.9 and of course the
> /etc/rc
> > > was
> > > > dinged. I opened the /etc/rc and found a
> change..
> > > > 
> > > > # System tuning
> > > > sysctl -w kern.maxvnodes=$(echo $(sysctl -n
> > > > hw.physmem) '33554432 / 512 * 1024 +p'|dc)
> > > > if [ -f /etc/sysctl-macosxserver.conf ]; then
> > > >         awk '{ if (!index($1, "#") &&
> index($1,
> > > "="))
> > > > print $1 }' < /etc/sysctl-macosxserver.conf |
> > > while
> > > > read
> > > >         do
> > > >                 sysctl -w ${REPLY}
> > > >         done
> > > > fi
> > > >         
> > > > if [ -f /etc/sysctl.conf ]; then
> > > >         awk '{ if (!index($1, "#") &&
> index($1,
> > > "="))
> > > > print $1 }' < /etc/sysctl.conf | while read
> > > >         do
> > > >                 sysctl -w ${REPLY}
> > > >         done
> > > > fi
> > > > 
> > > > sysctl -w kern.sysv.shmmax=4194304
> > > > sysctl -w kern.sysv.shmmin=1
> > > > sysctl -w kern.sysv.shmmni=32
> > > > sysctl -w kern.sysv.shmseg=8
> > > > sysctl -w kern.sysv.shmall=1024
> > > > 
> > > > It appears that apple is checking for
> > > etc/sysctl.conf
> > > > before setting the sysctl values. so I created
> a
> > > > etc/sysctl.conf with this inside:
> > > > 
> > > > kern.sysv.shmmax=33554432
> > > > kern.sysv.shmmin=1
> > > > kern.sysv.shmmni=32
> > > > kern.sysv.shmseg=8
> > > > kern.sysv.shmall=65536
> > > > 
> > > > I did not alter /etc/rc. postgresql starts up
> just
> > > > fine. I hope this implys that the issue is
> > > resolved..
> > > > 
> > > > Ted
> > > > 
> > > >



__________________________________________________
Do You Yahoo!?
Tired of spam?  Yahoo! Mail has the best spam protection around 
http://mail.yahoo.com 

In response to

Responses

pgsql-bugs by date

Next:From: Jim C. NasbyDate: 2005-05-01 18:37:10
Subject: Re: looks like apple fixed /etc/rc
Previous:From: Jim C. NasbyDate: 2005-04-30 17:38:43
Subject: Re: looks like apple fixed /etc/rc

Privacy Policy | About PostgreSQL
Copyright © 1996-2014 The PostgreSQL Global Development Group