4.3. Configuring IPC Tuneables on Solaris 10The new framework enables us to dynamically configure IPC tuneable parameters by using the resource control framework. Ideally, we want these to be statically defined for our applications. We can also put these definitions within a network database (LDAP), to remove any per-machine settings. The following example shows how to observe the System V Shared memory max parameter for a given login instance by using the prctl command. sol10$ id -p uid=0(root) gid=0(root) projid=3(default) sol10# prctl -n project.max-shm-memory -i project 3 project: 3: default NAME PRIVILEGE VALUE FLAG ACTION RECIPIENT project.max-shm-memory privileged 246MB - deny - system 16.0EB max deny - The shared memory maximum for this login has defaulted to 246 Mbytes. The following example shows how we can dynamically raise the shared memory limit. sol10# prctl -n project.max-shm-memory -r -v 500mb -i project 3 sol10# prctl -n project.max-shm-memory -i project 3 project: 3: default NAME PRIVILEGE VALUE FLAG ACTION RECIPIENT project.max-shm-memory privileged 500MB - deny - system 16.0EB max deny - To make this permanent, we would create a project entry for the user or project in question. sol10# projadd -c "My database" -U oracle user.oracle sol10# projmod -sK "project.max-shm-memory=(privileged,64G,deny)" user.oracle sol10# su - oracle oracle$ prctl -n project.max-shm-memory -i project user.oracle project: 101: user.oracle NAME PRIVILEGE VALUE FLAG ACTION RECIPIENT project.max-shm-memory privileged 64.0GB - deny - system 16.0EB max deny - |