blob: cd45cbdf65c9e8460fc7564e91fbc6a4976f6c36 [file] [log] [blame]
Andrew Geissler86a1ebf2022-11-10 15:58:30 -06001[Unit]
Andrew Geissler69a250d2022-11-10 16:23:04 -06002Description=Power is off to Chassis%i
Andrew Geissler86a1ebf2022-11-10 15:58:30 -06003After=phosphor-wait-power-off@%i.service
4Requires=phosphor-wait-power-off@%i.service
5
6[Service]
7RemainAfterExit=no
8# systemd starts all wanted targets in parallel and a Conflict
9# statement will resolve itself when the target starts, not when
10# completes. Some services have a requirement to stop
11# once power is off. The solution is to create a new target,
12# obmc-chassis-powered-off@.target, that is started after it is
13# verified that power has been removed from the chassis. Then
14# services may conflict with this target to ensure they
15# are stopped at the appropriate time.
16ExecStart=/bin/systemctl start obmc-chassis-powered-off@%i.target
Andrew Geissler69a250d2022-11-10 16:23:04 -060017SyslogIdentifier=phosphor-powered-off
Andrew Geissler86a1ebf2022-11-10 15:58:30 -060018
19
20[Install]
21WantedBy=obmc-chassis-poweroff@%i.target