When hcron executes an event, it does so with a minimal environment. This means each event must set up the environment as appropriate for itself. The brute force way is to run a shell as a login shell, which will provide an environment almost equivalent to an interactive session (as shown below).

Tip: If using a shell from the Bourne shell family (e.g., bash, sh, ksh), using bash to set up a login type environment is probably the best option.

The command field of an hcron event definition should be set as follows for the respective shells:


command=bash -l -c "<commands here>"

ksh (e.g., on Linux with pdksh):

command=ksh -l -c "<commands here>"


command=csh -l -c "<commands here>"

For enterprises in which a large number of events may be launched at once, even across multiple hosts, loading a full login environment for each event is highly discouraged as it can put a significant and unnecessary load on the home file servers. Ideally, augment the environment only as needed for the event command to run.