Starting and stopping the DaCS services
/sbin/service hdacsd stopand to restart the host daemon type:
/sbin/service hdacsd start
The accelerator daemon (adacsd) may be restarted in like manner. See the man page for service for more details on the service command.
DaCS daemon Configuration
The host daemon service is named hdacsd and the accelerator daemon service is named adacsd. Both daemons are configured using their respective /etc/dacsd.conf files.
Default versions of these files are automatically installed with each of the daemons. These default files contain comments on the parameters and values currently supported.
When one of these files is changed the changes will not take affect until the respective daemon is restarted as described above.
dacsd_receive_timeout=5
dacsd_kill_timeout=5
blade_monitor_interval=60
dacs_topology_config=/etc/dacs_topology.config
ae_cwd_prefix=/adacsd
ae_cwd_keep=falsewhich means the AE Current Working Directory and its contents are deleted when the AE process terminates. To prevent this use:
ae_cwd_keep=true
he_tar_command="/bin/tar cf -"An example of a debug setting is:
he_tar_command="/usr/bin/strace -o/tmp/he_tar_strace /bin/tar cvvf -"
ae_tar_command="/bin/tar xf -"and an example is:
ae_tar_command="/usr/bin/strace -o/tmp/ae_tar_strace /bin/tar xvvf -"
adacsd_use_numa=trueTo disable numa support use:
adacsd_use_numa=false
Startup options
ADACSD_ARGS="--log /var/log/adacsd.log --pidfile /var/run/adacsd.pid" HDACSD_ARGS="--log /var/log/hdacsd.log --pidfile /var/run/hdacsd.pid"
The --log option specifies the location for the daemon log file. This can be changed to a new file location. If no logging is desired set this to /dev/null.
The --pidfile option specifies the daemon pid file. The pid file contains the process id the daemon is running under. This information is useful when signals need to be sent to the daemon.
Topology Configuration
The HE daemon (hdacsd) also reads the DaCS topology configuration file. This file defines the configuration of the hardware, and how it can be used within DaCS. The file is normally set up as part of the DaCS for Hybrid installation, and is discussed in the SDK for Multicore Acceleration Version 3.0 Installation Guide.