I'm working on a script to take a snapshot of Lustre tunable values
in /proc.
I'd rather not hard code a list of files that will have to be updated
every time a tunable is added or removed.
One strategy that has been suggested to me is to look for files that
contain "min" or "max" as part of the name. I think there some that
this strategy will miss, though, like "lru_size" in the namespaces area.
The approach I have tentatively settled on is to look for files with
at least one write bit turned on.
Is this a reasonable approach? Will it find all the tunable files?
Does it select files that are not tunable? Can anyone suggest a
better way of doing this?
Thanks,
--
Tom Barron
[EMAIL PROTECTED]
865.576.1620
Oak Ridge National Laboratory
_______________________________________________
Lustre-devel mailing list
[email protected]
https://mail.clusterfs.com/mailman/listinfo/lustre-devel
