From 2abe0f2d527c7b3f6b97bd6519bf0e35a266ea68 Mon Sep 17 00:00:00 2001 From: Luke Shumaker Date: Sun, 7 Aug 2016 21:03:44 -0400 Subject: stuff --- docs/sysvinit/.gitignore | 1 - docs/sysvinit/README.in | 27 --------------------------- docs/var-log/.gitignore | 1 - docs/var-log/README.in | 26 -------------------------- 4 files changed, 55 deletions(-) delete mode 100644 docs/sysvinit/.gitignore delete mode 100644 docs/sysvinit/README.in delete mode 100644 docs/var-log/.gitignore delete mode 100644 docs/var-log/README.in (limited to 'docs') diff --git a/docs/sysvinit/.gitignore b/docs/sysvinit/.gitignore deleted file mode 100644 index c3fea7424f..0000000000 --- a/docs/sysvinit/.gitignore +++ /dev/null @@ -1 +0,0 @@ -/README diff --git a/docs/sysvinit/README.in b/docs/sysvinit/README.in deleted file mode 100644 index 996402d06b..0000000000 --- a/docs/sysvinit/README.in +++ /dev/null @@ -1,27 +0,0 @@ -You are looking for the traditional init scripts in @SYSTEM_SYSVINIT_PATH@, -and they are gone? - -Here's an explanation on what's going on: - -You are running a systemd-based OS where traditional init scripts have -been replaced by native systemd services files. Service files provide -very similar functionality to init scripts. To make use of service -files simply invoke "systemctl", which will output a list of all -currently running services (and other units). Use "systemctl -list-unit-files" to get a listing of all known unit files, including -stopped, disabled and masked ones. Use "systemctl start -foobar.service" and "systemctl stop foobar.service" to start or stop a -service, respectively. For further details, please refer to -systemctl(1). - -Note that traditional init scripts continue to function on a systemd -system. An init script @SYSTEM_SYSVINIT_PATH@/foobar is implicitly mapped -into a service unit foobar.service during system initialization. - -Thank you! - -Further reading: - man:systemctl(1) - man:systemd(1) - http://0pointer.de/blog/projects/systemd-for-admins-3.html - http://www.freedesktop.org/wiki/Software/systemd/Incompatibilities diff --git a/docs/var-log/.gitignore b/docs/var-log/.gitignore deleted file mode 100644 index c3fea7424f..0000000000 --- a/docs/var-log/.gitignore +++ /dev/null @@ -1 +0,0 @@ -/README diff --git a/docs/var-log/README.in b/docs/var-log/README.in deleted file mode 100644 index 2e64fb196a..0000000000 --- a/docs/var-log/README.in +++ /dev/null @@ -1,26 +0,0 @@ -You are looking for the traditional text log files in @VARLOGDIR@, and -they are gone? - -Here's an explanation on what's going on: - -You are running a systemd-based OS where traditional syslog has been -replaced with the Journal. The journal stores the same (and more) -information as classic syslog. To make use of the journal and access -the collected log data simply invoke "journalctl", which will output -the logs in the identical text-based format the syslog files in -@VARLOGDIR@ used to be. For further details, please refer to -journalctl(1). - -Alternatively, consider installing one of the traditional syslog -implementations available for your distribution, which will generate -the classic log files for you. Syslog implementations such as -syslog-ng or rsyslog may be installed side-by-side with the journal -and will continue to function the way they always did. - -Thank you! - -Further reading: - man:journalctl(1) - man:systemd-journald.service(8) - man:journald.conf(5) - http://0pointer.de/blog/projects/the-journal.html -- cgit v1.2.3-54-g00ecf