mochad systemd does not start

[woody]

I'm running mochad 0.1.15-2 on a Pogoplug V2. Everything is working ok except:

1. mochad does not start on reboot (but it does start if I unplug the USB and plug it back in again).

2. I tried to enable the systemd service for mochad, using the mochad.service file provided by WarheadsSE. I get errors when I try to start or enable systemd using that file.

So, I'm looking for a way to make sure that mochad will restart on reboot. Does anybody know what I need to do?

[WarheadsSE]

Looking at the file as I see it on my system now, it admittedly does not have all the bits that appear necessary for running at start.

[woody]

$this->bbcode_second_pass_quote('WarheadsSE', 'L')ooking at the file as I see it on my system now, it admittedly does not have all the bits that appear necessary for running at start.

[sdjf]

Writing systemd service files can be a challenge, and the documentation not easy to follow unless you are an expert.

I think your best bet is to copy a service file that you know works, and modify the contents to fit your application.

In some cases, systemd service won't work because some device has to be seen before they will. It may be possible to get them to wait for that, but I found in that instance, that a udev rule works better. System watches for a device to be recognized, and then runs whatever you want to have run.

[WarheadsSE]

Also, check if it has a udev rule to start it @ detection/insertion

[woody]

I do have a udev rule for it and it does start when I plug it in. Unfortunately, it does not start up on a reboot which is a problem when the power fails. I will see if I can figure out how to get systemd to work.

[WarheadsSE]

Ah, I see. Admittedly I haven't messed with mine much in the last while.

[woody]

I have been experimenting with a systemd file for mochad and this one seems to work most of the time:

$this->bbcode_second_pass_code('', '[[Unit]
Description=Mochad X10 Daemon
Requires=systemd-udevd.service
After=systemd-udevd.service

[Service]
Type=forking
GuessMainPID=yes
ExecStart=/usr/bin/mochad
Restart=on-abort

[Install]
WantedBy=multi-user.target')

I had one reboot where mochad crashed. I don't know exactly why that one crashed, but, as a precaution, I removed the udev auto-start rule in case that was causing a conflict.

Notice that this service file uses 'GuessMainPID='. I had to do this because it would not start properly when using the more typical option of specifying Pidfile=. It appears that the way the application is written that it doesn't allow systemd to specify the pid.

This is really an experimental hack on my part, so if anybody knows a way to improve this service file, please post it.