Difference between revisions of "Bright: Freeze Torque config files"
(Created page with "'''Question''' We recently installed a small Bright cluster for a customer in Scotland and they are using Torque with the default scheduler. They noticed that cmd auto-changed...") |
(No difference)
|
Revision as of 17:09, 10 February 2017
Question We recently installed a small Bright cluster for a customer in Scotland and they are using Torque with the default scheduler. They noticed that cmd auto-changed the /cm/shared/apps/torque/var/spool/server_priv/nodes file, which apparently broke their configuration. Can this be stopped and if yes can you please let me know where should the changes be made?
Answer You can either freeze the file in CMDaemon or freeze the torque configurations at all.
You can freeze the file in CMDaemon by adding it to the list of FrozenFiles in /cm/local/apps/cmd/etc/cmd.conf file and restart CMDaemon:
FrozenFile = { "/cm/local/apps/cmd/etc/cmd.conf" , "/etc/dhcpd.conf" }
You can have only one FrozenFile directive. Inside the curly brackets, you can have more than one file.
If you want to freeze the torque configurations, then you can "FreezeChangesToTorqueConfig = true" in cmd.conf and restart CMDaemon.
Question Also, out of curiosity, that's a different behaviour compared to SLURM right?
Answer The nodes file is completely generated by Bright.