3.1.1 - Set Daemon Control

      Action Option -SD (-SetDaemon) :

      creates and modifies daemon control information into RDADB for given specialist login names, commands, and hostnames of computers on which the check commands are processed. One or multiple records can be set each time.

      dscheck-(SD|SetDaemon) [Mode Option]
        [-(DI|DaemonIndex) controlIndices]
        [-(CM|Command) UtilityProgramNames]
        [-(SN|Specialist) DSSSpecialists]
        [-(HN|HostName) HostMachineNames]
        [-(MH|MatchHost) FlagToMatchHostname]
        [-(PL|ProcessLimit) MaxNumberOfProcesses],
        [-(PO|Priority) HostListOrder]

      Mode option that can be specified for this action include:

      If information of a daemon control exists already in RDADB for a given specialist, a command and a hostname, the daemon control record is modified; otherwise, a new daemon control record is added if daemon index is 0 and Mode option -ND (-NewDaemon) is present. Combination of specialist login name, command name and hostname of computer must be unique for for each daemon control record.

      Specify host name 'SLURM' for putting the command in the SLURM batch control system. If a specified command name is not found in the daemon control, the general 'dscheck' configuration for command name 'ALL' is used.


      EXAMPLE 1.

      Set Daemon Control Information For Schuster, All Commands On Slurm Hosts, for maximum 4 checks can be processed at the same time with priority 1, the smaller the number the higher the priority is, via input file daemon.ctl

      dsrqst SD -ND -IF daemon.ctl

      Content of input file daemon.ctl:

      DaemonIndex<:>Command<:>Specialist<:>Hostname<:>ProcessLimit<:>Priority<:>
      0<:>schuster<:>ALL<:>SLURM<:>4<:>1<:>



      Back to Top
      -(ND|NewDaemon)sets a new daemon control record into RDADB