systemd/units/remote-cryptsetup.target

#  SPDX-License-Identifier: LGPL-2.1+
#
#  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=Remote Encrypted Volumes
Documentation=man:systemd.special(7)
After=remote-fs-pre.target cryptsetup-pre.target
DefaultDependencies=no
Conflicts=shutdown.target

[Install]
WantedBy=multi-user.target
Add SPDX license headers to unit files 2017-11-18 17:35:03 +01:00			`# SPDX-License-Identifier: LGPL-2.1+`
			`#`
units: add remote-cryptsetup.target and remote-cryptsetup-pre.target The pair is similar to remote-fs.target and remote-fs-pre.target. Any cryptsetup devices which require network shall be ordered after remote-cryptsetup-pre.target and before remote-cryptsetup.target. 2017-09-05 10:15:13 +02: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=Remote Encrypted Volumes`
			`Documentation=man:systemd.special(7)`
units: make remote-cryptsetup.target also after cryptsetup-pre.target This way people can order units before cryptsetup-pre.target and have them run before any cryptsetup-related stuff. 2017-10-18 15:14:46 +02:00			`After=remote-fs-pre.target cryptsetup-pre.target`
units: add [Install] section to remote-cryptsetup.target This makes this target the same as remote-fs.target in this regard. In practice it probably doesn't make that much difference, because all encrypted devices that are part of remote-fs.target (marked with _netdev) will be used for mount points, so they will be pulled in anyway individually, but with this change any such device will be configured, even if it is not pulled by any other unit. 2017-10-12 22:13:03 +02:00			`DefaultDependencies=no`
			`Conflicts=shutdown.target`

			`[Install]`
			`WantedBy=multi-user.target`