diff options
Diffstat (limited to 'meta-phosphor/common/recipes-phosphor/chassis/obmc-op-control-power/op-powered-off@.service')
| -rw-r--r-- | meta-phosphor/common/recipes-phosphor/chassis/obmc-op-control-power/op-powered-off@.service | 20 |
1 files changed, 0 insertions, 20 deletions
diff --git a/meta-phosphor/common/recipes-phosphor/chassis/obmc-op-control-power/op-powered-off@.service b/meta-phosphor/common/recipes-phosphor/chassis/obmc-op-control-power/op-powered-off@.service deleted file mode 100644 index b76db7bf4..000000000 --- a/meta-phosphor/common/recipes-phosphor/chassis/obmc-op-control-power/op-powered-off@.service +++ /dev/null @@ -1,20 +0,0 @@ -[Unit] -Description=Power is off to chassis%i -After=op-wait-power-off@%i.service -Requires=op-wait-power-off@%i.service - -[Service] -RemainAfterExit=no -# systemd starts all wanted targets in parallel and a Conflict -# statement will resolve itself when the target starts, not when -# completes. Some services have a requirement to stop -# once power is off. The solution is to create a new target, -# obmc-chassis-powered-off@.target, that is started after it is -# verified that power has been removed from the chassis. Then -# services may conflict with this target to ensure they -# are stopped at the appropriate time. -ExecStart=/bin/systemctl start obmc-chassis-powered-off@%i.target - - -[Install] -WantedBy=obmc-chassis-poweroff@%i.target |
