[Pacemaker] /.crm_help_index file (in system root aka /)

[Maros Timko]

> Date: Tue, 13 Jul 2010 13:42:00 +0200
> From: Lars Ellenberg <lars.ellenberg at linbit.com>
> To: pacemaker at oss.clusterlabs.org
> Subject: Re: [Pacemaker] /.crm_help_index file (in system root aka /)
> Message-ID: <20100713114200.GC4254 at barkeeper1-xen.linbit>
> Content-Type: text/plain; charset=iso-8859-1
>
> On Tue, Jul 13, 2010 at 12:12:12PM +0200, Raoul Bhatia [IPAX] wrote:
>> hi,
>>
>> On 07/12/2010 05:36 PM, Lars Ellenberg wrote:
>> > put some "( date ; env) >> /tmp/tmp.debug.log" into your script,
>> > then we can determine if the crm shell assumes too much.
>>
>> i did some digging around and found that cron seems to set
>> the correct environment. so i used "inotifywait -m /"
>> to watch for changes to /:
>>
>> # tail -f /var/log/syslog &
>> # inotifywait -m / | grep --color crm_ &
>
> are you aware of the grep option --line-buffered ?
>
>> please find a c/p from three of such events attached.
>>
>> it now seems to me that the drbd monitor action creates these files.
>
> Highly unlikely. No DRBD provided script calls the crm shell.
>

The python crm scripts use os.getenv("HOME") to decide where to look
for or store the history file. Some of the environments (cronjob or
sudo) do have HOME set to "/".
Try to prepend crm call with:
export HOME=/root

Tino

> how about "bsd process accounting"?
> -> atop
>
>
> --
> : Lars Ellenberg
> : LINBIT | Your Way to High Availability
> : DRBD/HA support and consulting http://www.linbit.com
>
> DRBD? and LINBIT? are registered trademarks of LINBIT, Austria.