runit-void - runit init scripts for Void Linux

	Commit message (Collapse)	Author	Age	Files	Lines
*	vlogger.8: fix typo	jacereda	2020-01-23	1	-1/+1
\|
*	vlogger: force to use syslog if message arguments are given	Duncan Overbruck	2019-08-25	1	-11/+29
\|
*	vlogger.8: fix -f description	Duncan Overbruck	2019-08-25	1	-1/+3
\|
*	vlogger: use the same defaults as logger(1)	Duncan Overbruck	2019-08-25	1	-1/+4
\|
*	vlogger: add message argument for POSIX logger compatibility	Duncaen	2018-06-23	1	-1/+6
\|
*	vlogger: use static buffer and add -f flag	Duncaen	2018-06-22	1	-14/+19
\|
*	vlogger: pass level and facility to /etc/vlogger	Duncaen	2018-06-22	1	-2/+6
\|
*	vlogger: add logger(1) compatible -s and -i flag, and -S to force syslog	Duncaen	2018-06-22	1	-3/+27
\|
*	vlogger.8: reference runit(8) 20180620	Duncaen	2018-06-20	1	-1/+3
\|
*	vlogger.8: fix mdoc warnings	Duncaen	2018-06-20	1	-3/+3
\|
*	Add vlogger(8)	Duncaen	2018-06-20	1	-0/+138
	vlogger(8) is a alternative to logger(1), by default it sends messages from stdin to syslog. The main reason to replace logger(1) is, that logger only connects once to the syslog socket in default mode and puts all messages into the void if syslog is not running at the time. logger(1) has a new `--socket-errors=on` mode which would work, but some void uses don't use syslog at all and in this case the log service would constantly restart. As a bonus vlogger(8) looks for /etc/vlogger and if its executable it just executes it and is replaced by it. This can be used to avoid syslog and just write all logs to files with svlogd(8) as example, without having to edit all log services.