units: don't set LISTEN_FDNAMES for varlink services explicitly

Now that FileDescriptorName= is properly honored by Accept=yes sockets,
this explicit override is pointless.
This commit is contained in:
Lennart Poettering 2024-08-22 11:49:25 +02:00 committed by Mike Yuan
parent daa78907af
commit e7c8d78e7f
No known key found for this signature in database
GPG Key ID: 417471C0A40F58B3
5 changed files with 0 additions and 5 deletions

View File

@ -16,5 +16,4 @@ After=local-fs.target
Before=shutdown.target
[Service]
Environment=LISTEN_FDNAMES=varlink
ExecStart=bootctl

View File

@ -15,5 +15,4 @@ Conflicts=shutdown.target initrd-switch-root.target
Before=shutdown.target initrd-switch-root.target
[Service]
Environment=LISTEN_FDNAMES=varlink
ExecStart=-systemd-creds

View File

@ -16,5 +16,4 @@ Conflicts=shutdown.target initrd-switch-root.target
Before=shutdown.target initrd-switch-root.target
[Service]
Environment=LISTEN_FDNAMES=varlink
ExecStart=-{{LIBEXECDIR}}/systemd-pcrextend

View File

@ -17,5 +17,4 @@ Before=sysinit.target shutdown.target
After=systemd-remount-fs.service var.mount
[Service]
Environment=LISTEN_FDNAMES=varlink
ExecStart={{LIBEXECDIR}}/systemd-pcrlock --location=770

View File

@ -16,5 +16,4 @@ Conflicts=shutdown.target initrd-switch-root.target
Before=shutdown.target initrd-switch-root.target
[Service]
Environment=LISTEN_FDNAMES=varlink
ExecStart=-systemd-sysext