4 All @ref{Configuration, configuration} is assumed to be placed in
5 @file{rc/cfg}. Probably you want to deal with multiple server
6 configurations simultaneously. You place them in corresponding
7 @file{rc/NAME.cfg} directories and use @url{http://cr.yp.to/redo.html,
8 redo} default target to create necessary symbolic link of
9 @file{rc/NAME.cfg} to @file{rc/cfg} and build executable itself.
13 # will produce example executable with rc/example.cfg configuration
16 # will produce fcgi.example executable with rc/fcgi.example.cfg configuration
19 But because you will mostly like to create binary patches to quickly
20 update already existing binaries, then you can use @file{make-update.sh}
21 script, that will store newly created binaries in @file{updates/}
22 directory and make shell-script with the built-in binary patch and
23 SHA512 checksum checker:
27 $ ./make-update example
28 $ scp updates/example.old web-server:/path/to/www-server
30 $ ./make-update example
31 $ scp updates/example-update.sh web-server:/tmp
32 web-server $ /tmp/example-update.sh /path/to/www-server
33 web-server $ svc -t /var/service/www-server
36 @file{contrib/service} contains @command{daemontools} example run scripts.
38 Send @code{SIGINFO} (@code{SIGUSR1} on Linux) signal to get current
39 daemon's configuration.