xcat-core/xCAT-server
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
..
bin
etc -Rework init script to take advantage of 'nonstop' xcat 2010-07-09 15:17:47 +00:00
lib 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
sbin 1.fixed bug3041906 2. add enableASMI=no to site table 2010-08-12 03:30:31 +00:00
share/xcat 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
esx.esx4.tmpl
LICENSE.html
xCAT-server.spec roll back the last change, make the files in the fedora/dracut to be symbol link instead of using the spec 2010-07-26 10:15:17 +00:00
xcatd.rc