| Moab Workload Manager® |
3.1 Layout of Scheduler Components
Moab is initially unpacked into a simple one-deep directory structure. What follows demonstrates the default layout of scheduler components; some of the files (such as log and statistics files) are created while Moab runs.
- $(MOABHOMEDIR)
- moab.cfg - general configuration file
- moab-private.cfg - secure configuration file containing private information
- moab.dat - configuration file generated by Moab Cluster Manager
- moab.lic - license file
- .moab.ck - checkpoint file
- .moab.pid - lock file
- bin - directory for executable files
- spool - directory for temporary files
- log - directory for log files
- moab.log - log file
- moab.log.1 - previous log file
- stats - directory for statistics files
- events.<date> - event files
- {DAY|WEEK|MONTH|YEAR}.<date> - usage profiling data
- FS.<PARTITION>.<epochtime> - fairshare usage data
- docs - directory for documentation
- samples - directory for sample configuration files, simulation trace files, and so forth
- contrib - directory containing contributed code and plug-ins
- $(MOABINSTDIR)
- /etc/moab.cfg - optional file used to override default $(MOABHOMEDIR) settings that should contain the string MOABHOMEDIR $(DIRECTORY) to override the built-in $(MOABHOMEDIR) setting.
When Moab is configured via the configure script, the user is queried for the location of the Moab home directory and the $(MOABHOMEDIR) directory is compiled in as the default MOABHOMEDIR directory when Moab is built. Unless specified otherwise, Moab looks to this directory for configuration files. If you want to run Moab from a different directory, you can override the default home directory setting by editing the /etc/moab.cfg file. Look for the string containing MOABHOMEDIR <DIRECTORY> and set the environment variable MOABHOMEDIR, or specify that the configuration file explicitly use the -C command line option on Moab and the Moab client commands.
When Moab runs, it creates a log file, moab.log, in the log directory and creates a statistics file in the stats directory with the naming convention events.WWW_MMM_DD_YYYY. (Example: events.Sat_Feb_16_2008). Additionally, a checkpoint file, .moab.ck, and lock file, .moab.pid, are maintained in the Moab home directory.
3.1.1 Layout of Scheduler Components with Integrated Database Enabled
If USEDATABASE INTERNAL is configured, the layout of scheduler components varies slightly. The .moab.ck file and usage profiling data (stat/{DAY|WEEK|MONTH|YEAR}.<date>) are stored in the moab.db database. In addition, the event information is stored in both event files: (stat/events.<date>) and moab.db.