[mythtv-users] starting with systemd was Who's running Myth on Arch, and what do you think? (Gary Buhrmaster)

[Greg Woods]

On Sat, 2013-11-23 at 22:51 -0600, Bill Meek wrote:
> On 11/23/2013 10:26 PM, James Linder wrote:

> > ----------------------------------------------------------------------
> > boot then check status
> > ----------------------------------------------------------------------
> > [sandypit] /home/jam [51]% sh mythstatus
> > mythbackend.service - MythTV backend service
> > 	  Loaded: loaded (/etc/systemd/system/mythbackend.service; enabled)
> > 	  Active: failed (Result: exit-code) since Sun, 2013-11-24 12:02:25 WST; 1min 15s ago
> > 	 Process: 1040 ExecStart=/usr/local/bin/mythbackend --logpath /store/mythlogs --loglevel crit (code=exited, status=130)
> > 	  CGroup: name=systemd:/system/mythbackend.service
> >

You can also try "journalctl -u mythbackend" to see any error messages
produced when trying to start mythbackend. 

One big difference between the systemd world and the sysvinit world is
that systemd runs everything it thinks it can in parallel. This does
greatly speed up the boot process, but it also complicates it in that
all of your services must list dependencies on any other services
explicitly. So I would hazard a guess that mythbackend needs something
(like network.target maybe) that your systemd service file is not
specifying, and it's getting started before something it needs is
available. That would explain why it fails at boot time and works fine
if manually started later.

Now that I have spent some time learning how systemd works, I rather
like it, but there's no denying that there is a learning curve involved.

--Greg