The skarnet.org supervision suite http://git.skarnet.org/cgit/s6/atom/examples/ROOT/img/services-local/syslogd-linux/log/env?h=main 2015-10-06T16:23:19Z 2015-10-06T16:23:19Z Laurent Bercot ska-skaware@skarnet.org 2015-10-06T16:23:19Z urn:sha1:4da6b9c320e6b49d38af5cb6b5861480141f24cd - change examples to support -s - change examples to invoke s6-rc, remove servicedirs 2015-03-03T23:29:22Z Laurent Bercot ska-skaware@skarnet.org 2015-03-03T23:29:22Z urn:sha1:bcb2bb4b6ee85f19c80472df9b44eff0c4016e7b - fix comments in a few examples/.../README - add a /var symlink in examples/ROOT 2015-03-01T07:28:43Z Laurent Bercot ska-skaware@skarnet.org 2015-03-01T07:28:43Z urn:sha1:0e23f8f864a795214506918de4f7f5897f5e0730 2015-02-28T23:40:18Z Colin Booth colin@heliocat.net 2015-02-28T21:41:29Z urn:sha1:1473905fd7b31abafb54929fbd3c84e53cdc7841 Change -t to t for s6-log scripts: With the release of s6 v2.1.1.0 the -t flag to s6-log was depricated and replaced with a per-match control directive. This updates the example scripts to follow the current supported logging syntax. Update syslogd-linux example logger: It's helpful if you're doing syslog-style logging to split your log streams into different files in addition to a consolidated log. This change also splits the logging script out to be easier to manage. This also serves a second purpose of highlighting the fact that s6-log supports multiple log targets. Remove (most) absolute paths for non-init replacement s6-svscan: With non-slashpackage installs becoming the default, odds are that the execline and s6 binaries will be installed somewhere in the path. While all the example scripts still make calls to /command/execlineb, it makes sense to reduce the amount of editing needed to make these scripts work. Updating gitignore to skip trying to add vim turds