Hello! With 4.0.18 you included the ability to omit an entry for the server name variable in httpd_config.xml. LSWS uses the environment $HOSTNAME variable to set it when this happens. With this change I moved the location of the central httpd_config.xml file from /usr/lsws/conf to /home/lsws (NFS mount) using a symbolic link. Every Litespeed server was configured in this method and everything has worked great. There is, however, one exception. While Litespeed operates fine with this file as a symbolic link, updating the config file from the Litespeed interface causes a problem. Litespeed appears to copy the contents of httpd_config.xml, deletes the symbolic link, and then recreates the httpd_config.xml as a static file. Before Updating in LSWS GUI: [root@www2 lsws]# stat /usr/lsws/conf/httpd_config.xml File: `/usr/lsws/conf/httpd_config.xml' -> `/home/lsws/httpd_config.xml' Size: 27 Blocks: 0 IO Block: 4096 symbolic link Device: 802h/2050d Inode: 197593802 Links: 1 Access: (0777/lrwxrwxrwx) Uid: ( 151/ lsadm) Gid: ( 503/ lsadm) Access: 2011-01-31 10:30:33.000000000 -0800 Modify: 2011-01-28 12:07:36.000000000 -0800 Change: 2011-01-31 10:30:30.000000000 -0800 After Updating in LSWS GUI: [root@www2 lsws]# stat /usr/lsws/conf/httpd_config.xml File: `/usr/lsws/conf/httpd_config.xml' Size: 100735 Blocks: 208 IO Block: 4096 regular file Device: 802h/2050d Inode: 197593797 Links: 1 Access: (0644/-rw-r--r--) Uid: ( 151/ lsadm) Gid: ( 503/ lsadm) Access: 2011-01-31 10:32:02.000000000 -0800 Modify: 2011-01-31 10:32:02.000000000 -0800 Change: 2011-01-31 10:32:02.000000000 -0800 This is happening on a cluster of servers running CentOS 5.5 x86_64 w/ the latest Litespeed release installed. This issue does not affect Litespeed in any negative way other than being a minor inconvenience to have to recreate the link repeatedly.