I've got this service called odrived.service that I've written to be automatically started by systemd, which will in turn execte a binary file called odriveagent. It works, or I think it works, since systemctl status odrived.service
does show that odriveagent is started up. However, when I try executing scripts that depend on odriveagent, the scripts print errors stating that odriveagent is not started up.
However, if I followed the tutorial of the odrive website and manually entered nohup "home/user/.odrive-agent/bin/odriveagent" > /dev/null 2>&1 &
into a terminal, my scripts are able to find the started odriveagent and execute.
Is there something special about the processes started up by systemd that causes this error?
Below is my odrived.service code
[Unit]
Description=ODrive Sync Agent Daemon
[Service]
ExecStart=/home/user/.odrive-agent/bin/odriveagent
[Install]
WantedBy=multi-user.target
ExecStart
and it immediately exits? Doessystemctl status odrived.service
show an exit code? – yesno Oct 1 '19 at 9:59