source: gpfs_3.1_ker2.6.20/lpp/mmfs/samples/gpfsready.sample @ 24

#!/bin/ksh
# @(#)49  1.11  src/avs/fs/mmfs/ts/config/gpfsready.sample, mmfs, avs_rgpfs24, rgpfs240610b 10/31/05 10:18:04 
##############################################################################
#
# When properly installed, this script is invoked by the GPFS daemon during
# initialization, before it runs recovery for any VFS mount points that were
# already mounted, perhaps because GPFS is recovering from crash.
#
# This script can be used to initialize DMAPI applications before any mount
# is started.  Upon return from this script, DMAPI applications should have
# a session and a disposition for the mount event.
#
# If SANergy is used to access files controlled by GPFS, sanergyd can be
# started from this script.
#
#
# IMPORTANT: The GPFS daemon will wait until this script returns.  Do not
#            invoke long-running commands synchronously, and do not mount
#            GPFS file systems from this script.  Use the mmfsup script
#            for this purpose.
#
#
# To activate the code:
#
#   a) edit this script and make the appropriate changes
#   b) copy this script to /var/mmfs/etc/gpfsready
#   c) ensure this script is executable (chmod +x /var/mmfs/etc/gpfsready)
#
##############################################################################


# Uncomment the following to start sanergyd on MDC after GPFS comes up.

# sanergyd_cmd=/usr/SANergy/sanergyd32
# if [ -x $sanergyd_cmd ]
# then
#   print "$(date) $0 $sanergyd_cmd started"
#   $sanergyd_cmd &
# else
#   print "$(date) $0 can't execute $sanergyd_cmd"
# fi

return 0