shaba/systemd-stable
1
1
Fork 0
mirror of https://github.com/systemd/systemd-stable.git synced 2024-12-23 17:34:00 +03:00
Code
39f0d1d2e7
systemd-stable/units/systemd-journald-dev-log.socket

36 lines
1.2 KiB
SYSTEMD
Raw Normal View History

license: LGPL-2.1+ -> LGPL-2.1-or-later
2020-11-09 07:23:58 +03:00
# SPDX-License-Identifier: LGPL-2.1-or-later
Add SPDX license headers to unit files
2017-11-18 19:35:03 +03:00
#
journald: move /dev/log socket to /run This way we can make the socket also available for sandboxed apps that have their own private /dev. They can now simply symlink the socket from /dev.
2014-06-04 18:37:02 +04:00
# This file is part of systemd.
#
# systemd is free software; you can redistribute it and/or modify it
# under the terms of the GNU Lesser General Public License as published by
# the Free Software Foundation; either version 2.1 of the License, or
# (at your option) any later version.
[Unit]
Description=Journal Socket (/dev/log)
Documentation=man:systemd-journald.service(8) man:journald.conf(5)
DefaultDependencies=no
Before=sockets.target
units: add IgnoreOnIsolate=yes to systemd-journald too We already had it on the socket units, so it's possible that systemd-journald.service would be stopped and then restarted when trafic hits the sockets when something logs. Let's not try to stop it. It is supposed to run until the end and be eventually killed in the final killing spree. This might (or not) help with #23287.
2022-06-29 14:14:37 +03:00
# Mount and swap units need this. If this socket unit is removed by an isolate
# request the mount and swap units would be removed too, hence let's exclude
# systemd-journald and its sockets from isolate requests.
journald: move /dev/log socket to /run This way we can make the socket also available for sandboxed apps that have their own private /dev. They can now simply symlink the socket from /dev.
2014-06-04 18:37:02 +04:00
IgnoreOnIsolate=yes
[Socket]
ListenDatagram=/run/systemd/journal/dev-log
PassCredentials=yes
PassSecurity=yes
units: turn on timestamping for journald sockets To make things simple and robust when debugging journald, we'll leave the SO_TIMESTAMP invocations in the C code in place, even if they are now typically redundant, given that the sockets are already passed into the process with SO_TIMESTAMP turned on now.
2020-10-26 19:41:06 +03:00
Service=systemd-journald.service
SocketMode=0666
Symlinks=/dev/log
Timestamping=us
journald: also increase the SendBuffer of /dev/log to 8M http://lists.freedesktop.org/archives/systemd-devel/2014-August/021825.html
2014-08-13 20:53:05 +04:00
# Increase both the send and receive buffer, so that things don't
# block early. Note that journald internally uses the this socket both
# for receiving syslog messages, and for forwarding them to any other
# syslog, hence we bump both values.
journald: move /dev/log socket to /run This way we can make the socket also available for sandboxed apps that have their own private /dev. They can now simply symlink the socket from /dev.
2014-06-04 18:37:02 +04:00
ReceiveBuffer=8M
journald: also increase the SendBuffer of /dev/log to 8M http://lists.freedesktop.org/archives/systemd-devel/2014-August/021825.html
2014-08-13 20:53:05 +04:00
SendBuffer=8M
Copy Permalink