proxmox-backup/etc/pbsbanner.service

[Unit]
Description=Proxmox Backup Server Login Banner
ConditionPathExists=/usr/sbin/pbsbanner
ConditionPathExists=!/usr/bin/pvebanner
DefaultDependencies=no
After=local-fs.target
Before=console-getty.service

[Service]
ExecStart=/usr/sbin/pbsbanner
Type=oneshot
RemainAfterExit=yes

[Install]
WantedBy=getty.target
add login banner service Modeled after the one from PVE, but using rust instead of perl for resolving the nodename and writing to /etc/issue Behavior differs a bit. We write all non-loopback addresses to this file, as the gui accepts connections from them all, so limiting it to the first one is not really sensible. Further an error to resolve, or only getting loopback addresses won't write out an empty /etc/issue file, but a note about the error at the place where the address would be displayed. Named it "pbsbanner", not "proxmox-backup-banner" as it's rather an internal tool anyway and mirrors pvebanner, pmgbanner Signed-off-by: Thomas Lamprecht <t.lamprecht@proxmox.com> 2020-02-06 21:08:07 +00:00			`[Unit]`
			`Description=Proxmox Backup Server Login Banner`
			`ConditionPathExists=/usr/sbin/pbsbanner`
			`ConditionPathExists=!/usr/bin/pvebanner`
			`DefaultDependencies=no`
			`After=local-fs.target`
			`Before=console-getty.service`

			`[Service]`
			`ExecStart=/usr/sbin/pbsbanner`
			`Type=oneshot`
			`RemainAfterExit=yes`

			`[Install]`
			`WantedBy=getty.target`