mxi1 021457531b from now on, the entries in "litetree" table are no longer restricted to use different mnt point name; for example, ... The "litetree" table has the following entries: "1","ALL","192.168.11.107:/test/$node",, "2","ALL","192.168.11.108:/test/$node",, before the code is checked in, if you run "litetree <nodename>", you should get one message like this: <nodename>: 192.168.11.107:/test/<nodename> # 192.168.11.107 and 192.168.11.108 both mount /test. This not supported. After the code is checked in, there will be no any error/warning message about the entries in litetree table. Accordingly, the naming of mount points on the compute nodes are updated to "/.statelite/mnt/<nfs server ip>/<nfs directory>/" from "/.statelite/mnt/<nfs directory>/". git-svn-id: https://svn.code.sf.net/p/xcat/code/xcat-core/trunk@7105 8638fb3e-16cb-4fca-ae20-7b5d299a9bcd		2010-08-17 02:57:52 +00:00
..
autogpfs	Fixed issue where node was detected as new when gethostbyname failed.	2009-06-16 21:17:57 +00:00
stateless
statelite	from now on, the entries in "litetree" table are no longer restricted to use different mnt point name; for example,	2010-08-17 02:57:52 +00:00
torque	PBS_HOME wrong, should be /var/spool/torque (not /var/spool/pbs).	2010-05-13 15:53:08 +00:00