HP ProLiant DL380G5-WSS 3.7.0 HP StorageWorks HP Scalable NAS File Serving Sof - Page 158

ls -l /oracle/*bin lrwxrwxrwx 1 root root 10 Jun 16 16:40 /oracle/bin -> {MACH}/bin lrwxrwxrwx 1 root root 11 Jun 16 16:40 /oracle/sbin -> {MACH}/sbin When you log in on serv1, the /oracle/bin and /oracle/sbin symbolic links resolve to /oracle//bin and /oracle// sbin. On serv2, the links resolve to /oracle//bin and / oracle//sbin. Locate a target that is not on a PSFS filesystem In the earlier examples, both the symbolic links and the targets were on PSFS filesystems. However, only the symbolic link must be on a PSFS filesystem. The target can be located on a non-PSFS filesystem. This example uses a CDSL to link the /oracle/etc directory on the PSFS filesystem to a non-PSFS directory on serv1 or serv2. 1. On each server, create a target directory in /etc that has the same name as the server's hostname: mkdir /etc/serv1.xvz.com mkdir /etc/serv2.xvz.com 2. Populate the new directories with the appropriate files. 3. Create the CDSL: ln -s /etc/{HOSTNAME} /oracle/etc When you are logged in on serv1, the /oracle/etc symbolic link will point to / etc/serv1.xvz.com. On serv2, it will point to /etc/serv2.xvz.com. Cluster-wide file locking HP Scalable NAS supports cluster-wide locks on files located on PSFS filesystems. The locks are implemented with the standard Linux flock() system call, which is also known as the BSD flock interface. The psfssema command-line semaphore utility provides a simple synchronization mechanism for managing cluster-wide file locks. The utility can be used in shell scripts on different nodes of a cluster and takes advantage of the PSFS filesystem and its internode communication abilities. For example, you might want to use cluster-wide file locking in a Start or Stop script for a service or device monitor. 158 Configure PSFS filesystems