<html><head></head><body><div style="font-family: Verdana;font-size: 12.0px;"><div>Puh, i haven´t thought the discussion became this direction.
<div>
<div> </div>
<div>Corosync is not the only software, which need shared memory, so it is part of the OS startup to provide it, not part of Corosync or Pacemaker.</div>
<div>And yes, it is too late to mount it in Pacemaker startup.</div>
<div>Even in most embedded Linux installations share memory is available, just with smaller size.</div>
<div>So, there is no need to include anything in Corosync or Pacemaker startup directly.</div>
<div> </div>
<div>My answer about shared memory is valid and neccessary only for anaconda based installations.</div>
<div>When you install a RedHat system, the installation process is done by anaconda with a running miniroot (install.img) as ram disk.</div>
<div>Within this miniroot shared memory is enabled, but they (RedHat) missed the mount.</div>
<div>If somebody wants to correct it, RedHat (more specific the maintainer of install.img) is the correct address for this gap.</div>
<div> </div>
<div>To have world read access to CRM_CORE_DIR should be enough in case a core pattern set explicit to another directory (not tested yet).</div>
<div>When calling resource agents, CRM_CORE_DIR is the current PWD (tested with echo all environment variables to a file inside monitor call).</div>
<div>If this directory is not readable during switch user inside resource agent, stupid things could happen. Anyhow, it is not a good method of writing resource agents, switching user without setting the environment of the switched user. So, this is no fault of Pacemaker, more of loose programmed resource agents.</div>
<div>When the resource agent or any of its childs produces a core dump, it goes either to the current directory or to the directory specified with kernel core pattern.</div>
<div>If the core will go into the current directory and it is written by a switched user, who is not member of pcmk_gid, the core get lost.</div>
<div> </div>
<div>As i am not sure every resource agent is written with proper switch user environment and not rewriting my core pattern, enable world write on CRM_CCORE_DIR was the easy work around for it.</div>
<div> </div>
<div>Rainer</div>
<div style="margin: 10.0px 5.0px 5.0px 10.0px;padding: 10.0px 0 10.0px 10.0px;border-left: 2.0px solid rgb(195,217,229);">
<div style="margin: 0 0 10.0px 0;"><b>Gesendet:</b> Freitag, 29. März 2013 um 09:51 Uhr<br/>
<b>Von:</b> "Jacek Konieczny" <jajcus@jajcus.net><br/>
<b>An:</b> pacemaker@oss.clusterlabs.org<br/>
<b>Betreff:</b> Re: [Pacemaker] issues when installing on pxe booted environment</div>
<div>On Fri, 29 Mar 2013 11:37:37 +1100<br/>
Andrew Beekhof <andrew@beekhof.net> wrote:<br/>
<br/>
> On Thu, Mar 28, 2013 at 10:43 PM, Rainer Brestan<br/>
> <rainer.brestan@gmx.net> wrote:<br/>
> > Hi John,<br/>
> > to get Corosync/Pacemaker running during anaconda installation, i<br/>
> > have created a configuration RPM package which does a few actions<br/>
> > before starting Corosync and Pacemaker.<br/>
> ><br/>
> > An excerpt of the post install of this RPM.<br/>
> > # mount /dev/shm if not already existing, otherwise openais cannot<br/>
> > work if [ ! -d /dev/shm ]; then<br/>
> > mkdir /dev/shm<br/>
> > mount /dev/shm<br/>
> > fi<br/>
><br/>
> Perhaps mention this to the corosync guys, it should probably go into<br/>
> their init script.<br/>
<br/>
I don't think so. It is just a part of modern Linux system environment.<br/>
corosync is not supposed to mount the root filesystem or /proc –<br/>
mounting /dev/shm is not its responsibility either.<br/>
<br/>
BTW The excerpt above assumes there is a /dev/shm entry in /etc/fstab.<br/>
Should this be added there by the corosync init script too?<br/>
<br/>
Greets,<br/>
Jacek<br/>
<br/>
_______________________________________________<br/>
Pacemaker mailing list: Pacemaker@oss.clusterlabs.org<br/>
<a href="http://oss.clusterlabs.org/mailman/listinfo/pacemaker" target="_blank">http://oss.clusterlabs.org/mailman/listinfo/pacemaker</a><br/>
<br/>
Project Home: <a href="http://www.clusterlabs.org" target="_blank">http://www.clusterlabs.org</a><br/>
Getting started: <a href="http://www.clusterlabs.org/doc/Cluster_from_Scratch.pdf" target="_blank">http://www.clusterlabs.org/doc/Cluster_from_Scratch.pdf</a><br/>
Bugs: <a href="http://bugs.clusterlabs.org" target="_blank">http://bugs.clusterlabs.org</a></div>
</div>
</div>
</div></div></body></html>