Next: Invoking deco, Up: deco and dmd [Contents][Index]
The dmd
program has the following synopsis:
dmd [option…]
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
from the (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
register-services
, the <service>
class, and related tools
(see Services).
Do not check if the directory where the socket—our communication
rendez-vous with deco
—is located has permissions 700
.
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
otherwise.
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.
If -
is specified as file name, commands will be read from
standard input, one per line, as would be passed on a deco
command line (see Invoking deco).
Synonym for --silent
.