From f1dd0c3f9b4a257e81ff9c6a08070c702a0db45a Mon Sep 17 00:00:00 2001 From: Lennart Poettering Date: Fri, 18 Mar 2011 04:31:22 +0100 Subject: syslog: rework syslog detection so that we need no compile-time option what the name of the syslog implementation is --- man/systemd.special.xml.in | 31 ------------------------------- 1 file changed, 31 deletions(-) (limited to 'man') diff --git a/man/systemd.special.xml.in b/man/systemd.special.xml.in index 1506f34948..df62e9c4cd 100644 --- a/man/systemd.special.xml.in +++ b/man/systemd.special.xml.in @@ -78,7 +78,6 @@ sockets.target, swap.target, sysinit.target, - @SPECIAL_SYSLOG_SERVICE@, syslog.target, systemd-initctl.service, systemd-initctl.socket, @@ -542,27 +541,6 @@ or b. - - @SPECIAL_SYSLOG_SERVICE@ - - A special unit for the - syslog daemon. As soon as - this service is fully started - up systemd will connect to it - and use it for logging if it - has been configured for - that. - - Units should generally - avoid depending on this unit - directly and instead refer to - the - syslog.target - unit instead, which pulls this - one in directly or indirectly - via socket-based activation. - - syslog.target @@ -574,15 +552,6 @@ referring to the $syslog facility. - - Administrators should - ensure that this target pulls - in a service unit with the - name or alias of - @SPECIAL_SYSLOG_SERVICE@ - (or a socket unit that - activates this - service). -- cgit v1.2.3-54-g00ecf