On 14/03/2021 03:02, Patrick O'Callaghan wrote:
I assume there must be a basic error here, but I'm at a loss.
I like to crawl before I walk and walk before I run.
Even then, I see a pitfall in your plan. So, I created a test
/etc/systemd/system/dock.service.
[root@f33k system]# cat dock.service
[Unit]
Description=Power the dock up or down
After=local-fs.target
DefaultDependencies=no
[Service]
Type=oneshot
ExecStartPre=/usr/bin/mkdir -p /var/tmp/auto
ExecStart=/usr/bin/touch /var/tmp/auto/start
ExecStop=/usr/bin/touch /var/tmp/auto/stop
And notice the following......
[root@f33k ~]# ll /var/tmp/auto
ls: cannot access '/var/tmp/auto': No such file or directory
[root@f33k ~]# systemctl status dock.service
● dock.service - Power the dock up or down
Loaded: loaded (/etc/systemd/system/dock.service; static)
Active: inactive (dead)
[root@f33k ~]# systemctl start dock.service
[root@f33k ~]# ll /var/tmp/auto
total 0
-rw-r--r--. 1 root root 0 Mar 14 06:35 start
-rw-r--r--. 1 root root 0 Mar 14 06:35 stop
See the issue?
Your dock.service, if run, would power-up and then immediately power-down the dock.
--
People who believe they don't make mistakes have already made one.