On Tue, Nov 29, 2011 at 12:40 AM, Dejan Muhamedagic <[email protected]> wrote: > On Mon, Nov 28, 2011 at 10:36:06AM +1100, Andrew Beekhof wrote: >> On Thu, Nov 24, 2011 at 8:52 PM, Dejan Muhamedagic <[email protected]> >> wrote: >> > Hi, >> > >> > On Wed, Nov 23, 2011 at 08:52:43AM +1100, Andrew Beekhof wrote: >> >> On Wed, Nov 23, 2011 at 4:05 AM, Dejan Muhamedagic <[email protected]> >> >> wrote: >> >> > It could be that the init script on your platform doesn't >> >> > support this parameter. You should talk to your vendor. >> >> >> >> Init script? Doesn't the lrmd just look for that variable in its >> >> environment? >> > >> > No, it doesn't. lrmadmin has to be used to set the parameter: >> > >> > lrmadmin -p max-children $LRMD_MAX_CHILDREN >> >> Interesting choice > > Since it doesn't have a configuration file, lrmd is managed > through lrmadmin. It's always been like that.
Alas its not compatible with systemd based installs. > IMO, for > daemon-like programs that's still a better interface than > changing behaviour via environment variables. _______________________________________________ Linux-HA mailing list [email protected] http://lists.linux-ha.org/mailman/listinfo/linux-ha See also: http://linux-ha.org/ReportingProblems
