HP File System Extender (FSE) manual Options, Start

2.1 NAME 5

•post_start.sh (on Linux systems) or post_start.cmd (on Windows systems)

... this is the post–start helper script. It is executed after all FSE processes have been started up and all existing FSE file systems with an entry in the /etc/fstab file (on Linux systems) or all existing FSE file systems with a defined mount point (on Windows systems) have been mounted, i.e. right after the FSE system is put into its fully operational state;

•pre_stop.sh (on Linux systems) or pre_stop.cmd (on Windows systems) .....

this is the pre–stop helper script. It is executed before all mounted HSM file systems are unmounted and all running FSE processes are shut down, i.e. right before the FSE system is pulled out of its fully operational state.

If any of these scripts does not exist, it is simply ignored.

IMPORTANT: The commands that you specify in the post–start and pre–stop scripts should not block the execution of the fse command. Thus, they have to conform to the following rules:

•They must not require interactive input.

•They must finish in a reasonable time and afterwards return the control to the script afterwards.

2.1.3OPTIONS

•– –start

This option has different effects depending on whether the fse command is executed on a stand–alone FSE system or in a distributed FSE system on FSE server or FSE client.

If used on a stand–alone FSE system, the start option:

1.initiates omniNames – the omniORB naming service daemon, if it is not running yet,

2.initiates the FSE system operation starting up all FSE processes (see FSE PROCESSES for details on FSE processes),

3.mounts all existing HSM file systems with an entry in the /etc/fstab file (on Linux systems),

File System Extender 3.2 Command Line Reference