dmd program has the following synopsis:
It accepts the following options:
Read and evaluate file as the configuration script on startup.
file is evaluated in the context of a fresh module where bindings
(dmd service) module and Guile’s
(oop goops) are
available, in addition to the default set of Guile bindings. In
particular, this means that code in file may use
<service> class, and related tools
Do not check if the directory where the socket—our communication
deco—is located has permissions
If this option is not specified,
dmd will abort if the
permissions are not as expected.
Log output into file, or if file is not given,
/var/log/dmd.log when running as superuser, ~/.dmd.log
When dmd is ready to accept connections, write its PID to file or to the standard output if file is omitted.
Receive further commands on the socket special file file. If this option is not specified, localstatedir/run/dmd/socket is taken.
- is specified as file name, commands will be read from
standard input, one per line, as would be passed on a
command line (see Invoking deco).