PS. Some info here which tells how to make this _permanent_ and we were
surprised adding the setting to sysctl.conf wasn't the primary method
mentioned: http://www.redhatmagazine.com/2006/12/15/tips_tricks/
Yes, this is very unfortunate. Hacking the init scripts is not a very
elegant way to perform changes to the default behaviour, IMHO. The
reasons I can think of are
a) sysctl works with /proc/sys and has no clue about /proc/cluster
b) sysctl -p executes about 20% into /etc/rc.sysinit, WAY before the
cluster services would start up (and /proc/cluster created).
It would be great if we could have this setting changeable via a
standard mechanism (e.g. checking /etc/sysconfig/cluster, which
/etc/init.d/gfs does source, but
Question to the developers - what would be the best mechanism to have
the number of cached locks set in /etc/sysconfig/cluster for GFS in
RHEL4 and RHEL5? Bugzilla RFE? Global Support Service Request? I have
heard about featurezilla from a Red Hat employee before, but I could not
find it (so I assume it is not open to regular customers/partners)
tnx
Riaan
begin:vcard
fn:Riaan van Niekerk
n:van Niekerk;Riaan
org:Obsidian Systems;Obsidian Red Hat Consulting
email;internet:riaan@xxxxxxxxxxxxxx
title:Systems Architect
tel;work:+27 11 792 6500
tel;fax:+27 11 792 6522
tel;cell:+27 82 921 8768
x-mozilla-html:FALSE
url:http://www.obsidian.co.za
version:2.1
end:vcard
--
Linux-cluster mailing list
Linux-cluster@xxxxxxxxxx
https://www.redhat.com/mailman/listinfo/linux-cluster
