README.md in remote_syslog-1.6.1 vs README.md in remote_syslog-1.6.2
- old
+ new
@@ -69,13 +69,15 @@
exists, write PID to `/tmp/remote_syslog.pid`, and send with facility local0
to `a.server.com:514`:
$ remote_syslog -D -d a.server.com -f local0 -P /tmp /var/log/mysqld.log
-remote_syslog will daemonize by default. A sample init file is in the gem as
-[remote_syslog.init.d]. You may be able to:
+## Auto-starting at boot
+The gem includes sample [init files] such as [remote_syslog.init.d]. remote_syslog will
+daemonize by default. You may be able to:
+
$ cp examples/remote_syslog.init.d /etc/init.d/remote_syslog
## Sending messages securely ##
If the receiving system supports sending syslog over TCP with TLS, you can
@@ -232,9 +234,10 @@
4. Push to your branch - `git push origin my_branch`
5. Create a Pull Request or an [Issue][is] with a link to your branch
6. That's it!
[sample config]: https://github.com/papertrail/remote_syslog/blob/master/examples/log_files.yml.example
+[init files]: https://github.com/papertrail/remote_syslog/blob/master/examples/
[remote_syslog.init.d]: https://github.com/papertrail/remote_syslog/blob/master/examples/remote_syslog.init.d
[advanced config]: https://github.com/papertrail/remote_syslog/blob/master/examples/log_files.yml.example.advanced
[fk]: http://help.github.com/forking/
[is]: https://github.com/papertrail/remote_syslog/issues/
[Papertrail]: http://papertrailapp.com/