On Mon, Jun 29, 2009 at 12:05:50PM +0200, Florian Haas wrote:
> On 2009-06-29 11:57, Dejan Muhamedagic wrote:
> >>> Yes. BTW, it won't work if the configuration's changed back from
> >>> some to none, so perhaps you should remove those files in that
> >>> case.
> >> You lost me there. What files are you referring to? And what is it
> >> exactly that won't work?
> >
> > Sorry. The /etc/initiators.deny and such. If the user first
> > specifies some initiators and runs the resource, then later
> > changes it to empty, the files won't change, i.e. the "none" case
> > is not enforced.
>
> The resource agent does not implement reload, so on reconfiguration the
> resource will get stopped with the old config (which will remove entries
> in /etc/initiators,{allow,deny}) and then restarted with the new
> configuration (where, by default, no access restrictions are put in place).
>
> At least that's the way it works for me, with Pacemaker 1.0.4. Am I
> missing something? Or does this work only accidentally?
Didn't test it myself, it just looked so in the code and
according to the documentation. But I probably misunderstood.
Cheers,
Dejan
> Florian
>
> _______________________________________________________
> Linux-HA-Dev: [email protected]
> http://lists.linux-ha.org/mailman/listinfo/linux-ha-dev
> Home Page: http://linux-ha.org/
_______________________________________________________
Linux-HA-Dev: [email protected]
http://lists.linux-ha.org/mailman/listinfo/linux-ha-dev
Home Page: http://linux-ha.org/
