Hi guys, Thanks both of you for your help. I finally found out what the root cause of problems was. I did this in this order: 1. Created the service directory 2. Symlink it to tell runit about the new service 3. Created the log directory At this point, no matter how many times I started/stopped the service, logging was not kicking in. I needed to remove the symlink created in (2), and recreate it. Then, hey presto, it was all working beautifully! FWIW--I didn't understand the key concept that runit was monitoring the service directory and looking for new symlinks to be created. Also, as a side note, in the FAQ for logging, it seems that the service that is being started is another logging tool (socklog-klog). This in itself was confusing for me, as it wasn't clear if this logging was part of the runit logging, or if it was just the service. So I guess what I'm saying here is maybe the documentation should be changed to log a different kind of process so it is clear what part of the script is required for logging and what is just other stuff. Cheers, Raymond On 30 April 2013 22:07, Jameson Graef Rollins wrote: > On Tue, Apr 30 2013, Raymond Barlow wrote: > > Logging: > > > > * Do you need to create 2 run scripts (/etc/sv/myservice/run, > > /etc/sv/myservice/log/run)? Or does the log/run supersede the > myservice/run > > script? > > The run and log/run scripts are completely distinct. The run script is > for exec'ing the actual supervised process, and the log/run script is > for exec'ing the corresponding svlogd process. > > > * The directory specified in the log run script to svlogd (eg > ./main)--does > > this live in the log directory? > > Yes: log/main/ > > > * Do I need to create the log directory or does the svlogd directory do > > that for me > > Usually the log/run script creates it if it doesn't exist. > > Pretty much all of my services use this same log/run script: > > #!/bin/sh > set -e > LOG=$(readlink -f ./main) > test -d "$LOG" || mkdir -p -m0750 "$LOG" > exec svlogd -tt "$LOG" > > jamie. >