Can’t create shared memory: system shmget (Macintosh) - Revision history

Jord: removing broken link to original faq

2017-08-16T21:35:58Z

removing broken link to original faq

Jord: removing font

2016-11-22T00:25:35Z

removing font

Jord: adding font and breaks

2016-09-12T15:32:44Z

adding font and breaks

Jord: fixing broken formatting

2016-08-29T22:05:59Z

fixing broken formatting

Jord: adding table, fixing formatting

2016-08-29T22:05:22Z

adding table, fixing formatting

Vaxfan: Saving FAQ 276

2016-05-21T22:57:21Z

Saving FAQ 276

New page

BOINC science applications use shared memory to communicate with the core client, and a certain amount is reserved for each current task, whether running or waiting. The default configuration of a multi-CPU Mac (regardless of how much RAM is installed) is sometimes inadequate to support several projects at once.

If you get this error message, which is usually followed by a â€œCouldn't start or resume: -144â€ error in the current computation, it may help to set your BOINC general preference â€œLeave applications in memory while suspended?â€ to no; however, the problem will probably just become less frequent rather than being solved, and moreover some projectsâ€™ applications, those that save checkpoints infrequently (or erratically), may not take well to this setting.

A better solution is availableâ€”if you donâ€™t mind reconfiguring your systemâ€™s kernel a little. The method, accompanied by a more detailed description of the issue, is outlined in Configuring Shared Memory on Mac OS X from Spy Hill Research (hosts of the BOINC Pirates@home project). It involves creating a text file â€œ/etc/sysctl.confâ€ that contains the following commands:

kern.sysv.shmmax=16777216
kern.sysv.shmmin=1
kern.sysv.shmmni=128
kern.sysv.shmseg=32
kern.sysv.shmall=4096
and rebooting the computer. This will quadruple the default allocation of shared memory.

Note that the problem may manifest with slightly different error messages: â€œCan't create shared memory: system shmatâ€ followed by â€œCouldn't start or resume: -146â€.

| Odysseus
| 5
| 1
| 22:28:07
| 2007-09-16
| 94042
| 1
| 276
| 2007-09-16 22:28:07
| 2007-09-16 22:28:07
|-

@@ Line 21: / Line 21: @@
   |-
   | Odysseus
-  | [http://boincfaq.mundayweb.com/index.php?language=1&view=276 276]
+  | 276
   | 16-09-2007
   |-
   |}

@@ Line 1: / Line 1: @@
 BOINC science applications use shared memory to communicate with the core client, and a certain amount is reserved for each current task, whether running or waiting. The default configuration of a multi-CPU Mac (regardless of how much RAM is installed) is sometimes inadequate to support several projects at once.<br>
 <br>
@@ Line 26: / Line 25: @@
   |-
   |}

@@ Line 1: / Line 1: @@
-BOINC science applications use shared memory to communicate with the core client, and a certain amount is reserved for each current task, whether running or waiting. The default configuration of a multi-CPU Mac (regardless of how much RAM is installed) is sometimes inadequate to support several projects at once.
+<div style=" line-height: 1.1rem; font-family: verdana;">
+BOINC science applications use shared memory to communicate with the core client, and a certain amount is reserved for each current task, whether running or waiting. The default configuration of a multi-CPU Mac (regardless of how much RAM is installed) is sometimes inadequate to support several projects at once.<br>
-If you get this error message, which is usually followed by a "Couldn't start or resume: -144" error in the current computation, it may help to set your BOINC general preference "Leave applications in memory while suspended?" to no; however, the problem will probably just become less frequent rather than being solved, and moreover some projects' applications, those that save checkpoints infrequently (or erratically), may not take well to this setting.
+<br>
+If you get this error message, which is usually followed by a "Couldn't start or resume: -144" error in the current computation, it may help to set your BOINC general preference "Leave applications in memory while suspended?" to no; however, the problem will probably just become less frequent rather than being solved, and moreover some projects' applications, those that save checkpoints infrequently (or erratically), may not take well to this setting.<br>
-A better solution is available if you don't mind reconfiguring your system's kernel a little. The method, accompanied by a more detailed description of the issue, is outlined in Configuring Shared Memory on Mac OS X from Spy Hill Research (hosts of the BOINC Pirates@home project). It involves creating a text file /etc/sysctl.conf that contains the following commands:
+<br>
+A better solution is available if you don't mind reconfiguring your system's kernel a little. The method, accompanied by a more detailed description of the issue, is outlined in Configuring Shared Memory on Mac OS X from Spy Hill Research (hosts of the BOINC Pirates@home project). It involves creating a text file /etc/sysctl.conf that contains the following commands:<br>
-kern.sysv.shmmax=16777216<br>
+<br>
-kern.sysv.shmmin=1<br>
+ kern.sysv.shmmax=16777216
-kern.sysv.shmmni=128<br>
+ kern.sysv.shmmin=1
-kern.sysv.shmseg=32<br>
+ kern.sysv.shmmni=128
-kern.sysv.shmall=4096<br>
+ kern.sysv.shmseg=32
-and rebooting the computer. This will quadruple the default allocation of shared memory.
+ kern.sysv.shmall=4096
+ and rebooting the computer. This will quadruple the default allocation of shared memory.
-Note that the problem may manifest with slightly different error messages: "Can't create shared memory: system shmat" followed by "Couldn't start or resume: -146".
+<br>
+Note that the problem may manifest with slightly different error messages: "Can't create shared memory: system shmat" followed by "Couldn't start or resume: -146".<br>
+<br>
 {| class="wikitable" style="text-align: center;"
   ! Original writer
@@ Line 25: / Line 26: @@
   |-
   |}

@@ Line 5: / Line 5: @@
 A better solution is available if you don't mind reconfiguring your system's kernel a little. The method, accompanied by a more detailed description of the issue, is outlined in Configuring Shared Memory on Mac OS X from Spy Hill Research (hosts of the BOINC Pirates@home project). It involves creating a text file /etc/sysctl.conf that contains the following commands:
-kern.sysv.shmmax=16777216
+kern.sysv.shmmax=16777216<br>
-kern.sysv.shmmin=1
+kern.sysv.shmmin=1<br>
-kern.sysv.shmmni=128
+kern.sysv.shmmni=128<br>
-kern.sysv.shmseg=32
+kern.sysv.shmseg=32<br>
-kern.sysv.shmall=4096
+kern.sysv.shmall=4096<br>
 and rebooting the computer. This will quadruple the default allocation of shared memory.