diet-bmd can manage a batch system on a machine. This command takes in argument the name of the machine where the batch system will be manage, the type of batch system, a user-table and a grp-table declaring the mapping rules for the users and the groups, but also a configuration file.
diet-bmd [--config diet_config_file] [--host machine] [--user-table user_table_file] [--grp-table grp_table_file] [--batch batch_name]
diet-bmd uses the configuration file diet_config_file defined with the --config option to be able for a client program to interact with the local batch system. If the --config option is not set, diet-bmd will use the configuration file defined by dietconfig in /etc/DIET/diet-bmd.cfg (which is the default location of the file). If this file does not exist, the diet_config_file could also be defined with the DBMS_DIET_CONFIG environment variable.
The host is by default the system hostname. This can be override by the --host option on the command line. If the --host option is not set, diet-bmd will use the host name defined by hostname option in /etc/DIET/diet-bmd.cfg (which is the default location of the file). If this file does not exist, the host name could also be defined with the DBMS_HOST_NAME environment variable.
diet-bmd uses the user_table_file to map the input users to the local users. If the --user-table option is not set, diet-bmd will use the user-table value defined by the usertable option in /etc/DIET/diet-bmd.cfg (which is the default location of the file). If this file does not exist, the user-table could also be defined with the DBMS_USER_TABLE environment variable.
diet-bmd uses the grp_table_file to map the input groups to the local groups. If the --grp-table option is not set, diet-bmd will use the grp-table value defined by the grouptable option in /etc/DIET/diet-bmd.cfg (which is the default location of the file). If this file does not exist, the grp-table could also be defined with the DBMS_GRP_TABLE environment variable.
diet-bmd uses the batch_name to know how to interact with the underlying batch system. If the --batch option is not set, diet-bmd will use the batch value defined by the batch option in /etc/DIET/diet-bmd.cfg (which is the default location of the file). If this file does not exist, the batch_name could also be defined with the DBMS_BATCH_NAME environment variable.
The diet-bmd.cfg file can store all the options of diet-bmd with the following options:
It could look like this:
dietconfig = /etc/DIET/SeD.cfg usertable = /etc/DIET/user-table.txt grouptable = /etc/DIET/group-table.txt hostname = foo batch = torque
How to launch the diet-bmd daemon with all the options on the command line? Let's see with the torque batch system on the foo machine:
diet-bmd --config path_to_the_configuration_file --user-table /etc/DIET/user-table.txt --grp-table /etc/DIET/grp-table.txt --host foo --batch torque
Now, suppose that we have the a well-defined diet-bmd.cfg file defined in the /etc/DIET directory (or elsewhere from the moment that the compilation has been do we the right path) that looks like to the one described above. We could then directly call the diet-bmd program like this:
diet-bmd
diet-bmd(1), diet-list(1), diet-cancel(1),diet-submit(1), diet-agent, omniNames.
Version: 1.1 of 2010/02/02.
This program is free software: you can redistribute it and/or modify it under the terms of the GNU General Public License as published by the Free Software Foundation, either version 3 of the License, or (at your option) any later version.
This program is distributed in the hope that it will be useful, but WITHOUT ANY WARRANTY; without even the implied warranty of MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the GNU General Public License for more details.
You should have received a copy of the GNU General Public License along with this program. If not, see http://www.gnu.org/licenses/.
GRAAL, INRIA Rhône-Alpes
46 allée d'Italie
69364 Lyon cedex 07, FRANCE
Email: tech@sysfera.com
WWW: http://www.sysfera.com.