Jerry LeVan <[EMAIL PROTECTED]> writes:
> There have been some recent discussions on Shared Memory problems
> in Darwin on the darwin-kernel list at lists.apple.com.
> The subject is : shm_open and mmap: Invalid argument?
> Tain't clear to me if this is relevant to the MacOS X and
> Postgresql sh
There have been some recent discussions on Shared Memory problems
in Darwin on the darwin-kernel list at lists.apple.com.
The subject is : shm_open and mmap: Invalid argument?
Tain't clear to me if this is relevant to the MacOS X and
Postgresql shared memory problem that I see mentioned here
from t
On 1/21/05 1:50 AM, "Jonel Rienton" <[EMAIL PROTECTED]> wrote:
> I have found this at the docs of Postgres:
Yes, I knew about that. My email was in regards to an earlier discussion on
why you had to update /etc/rc as of 10.3 (probably should have dug that one
up and replied to it). The previous
On 1/20/05 10:27 PM, "Jonel Rienton" <[EMAIL PROTECTED]> wrote:
> have you tried using /etc/sysctl.conf and saving the shmax value there?
Unfortunately, the -p parameter does not appear to be valid, nor does
'strings -a' show 'conf' in the binary (unlike the RedHat sysctl).
Wes
--
have you tried using /etc/sysctl.conf and saving the shmax value there?
On Thu, 20 Jan 2005 21:51:02 -0600, Wes wrote
> The problem with not being able to set shmmax and shmall in a
> startup script in Mac OS X is not that you are setting them too late
> in the boot process. It is that you can s
The problem with not being able to set shmmax and shmall in a startup script
in Mac OS X is not that you are setting them too late in the boot process.
It is that you can set them only once. In fact, you can set them from a
terminal window after booting and logging in - as long as they haven't
alr
