mirror of
https://github.com/systemd/systemd.git
synced 2024-12-22 17:35:35 +03:00
74c4bd6b1a
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.
30 lines
934 B
SYSTEMD
30 lines
934 B
SYSTEMD
# SPDX-License-Identifier: LGPL-2.1-or-later
|
|
#
|
|
# 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
|
|
Documentation=man:systemd-journald.service(8) man:journald.conf(5)
|
|
DefaultDependencies=no
|
|
Before=sockets.target
|
|
|
|
# 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.
|
|
IgnoreOnIsolate=yes
|
|
|
|
[Socket]
|
|
ListenDatagram=/run/systemd/journal/socket
|
|
ListenStream=/run/systemd/journal/stdout
|
|
PassCredentials=yes
|
|
PassSecurity=yes
|
|
ReceiveBuffer=8M
|
|
Service=systemd-journald.service
|
|
SocketMode=0666
|
|
Timestamping=us
|