Documentation System Daemons Beat

From FedoraProject

(Difference between revisions)
Jump to: navigation, search
(Replaced content with "{{header|docs}}{{Docs_beat_open}} Category:Docs Project Category:Draft documentation Category:Documentation beats")
Line 1: Line 1:
{{header|docs}}{{Docs_beat_open}}
+
== Remote journal logging ==
 +
 
 +
Journal messages can be forwarded to remote storage, without using a syslog daemon. The ''systemd-journal-remote'' and ''systemd-journal-upload'' packages provide receiver and sender daemons. Communication is done over HTTPS.
 +
 
 +
== systemd PrivateDevices ==
 +
 
 +
The PrivateDevices setting, when set to "yes", provides a private, minimimal /dev that does not include physical devices. This allows long-running services to have limited access, increasing security.
 +
 
 +
== systemd PrivateNetwork ==
 +
 
 +
The PrivateNetwork setting, when set to "yes", provides a private network with only a loopback interface. This allows long-running services that do not require network access to be cut off from the network.
 +
 
 
[[Category:Docs Project]]
 
[[Category:Docs Project]]
 
[[Category:Draft documentation]]
 
[[Category:Draft documentation]]
 
[[Category:Documentation beats]]
 
[[Category:Documentation beats]]

Revision as of 02:01, 2 August 2014

Remote journal logging

Journal messages can be forwarded to remote storage, without using a syslog daemon. The systemd-journal-remote and systemd-journal-upload packages provide receiver and sender daemons. Communication is done over HTTPS.

systemd PrivateDevices

The PrivateDevices setting, when set to "yes", provides a private, minimimal /dev that does not include physical devices. This allows long-running services to have limited access, increasing security.

systemd PrivateNetwork

The PrivateNetwork setting, when set to "yes", provides a private network with only a loopback interface. This allows long-running services that do not require network access to be cut off from the network.