Arch Linux

lomaker

Member

Registered: 2013-04-10

Posts: 8

Website

dahdi.service script error after reboot

Hi!
Setup DAHDI drivers. Created a service-file as follows:

[Unit]
Description = DAHDI configuration script.
After = network.target

[Service]
Type = forking
WorkingDirectory = / home
ExecStart = / usr / bin / dahdi_cfg-vvvv
ExecStop = / usr / bin / dahdi_cfg-s

RemainAfterExit = yes

[Install]
WantedBy = multi-user.target

After the computer restarts systemctl issues as the status of the process failed. The output of "journalctl -xn" also shows nothing. Included in the mode LogLevel debug. But the team "journalctl -u dahdi" issue just simply this:

- Reboot -
Jul 09 09:13:54 aesats1 systemd [1]: dahdi.service changed dead -> failed

But after I manually do "systemctl start dahdi" service normally starts and does not show any errors.
Tried to change the type simple and oneshot - no result.

jasonwryan

Anarchist

From: .nz

Registered: 2009-05-09

Posts: 30,426

Website

Re: dahdi.service script error after reboot

Not an Installation issue, moving to AUR issues...

---

Arch + dwm   •   Mercurial repos  •   Surfraw

Registered Linux User #482438

lomaker

Member

Registered: 2013-04-10

Posts: 8

Website

Re: dahdi.service script error after reboot

I agree, in aur any, but tarball do not have service-file. Thus it is no better than my Tarball. The problem is just in the start script. Without it, the driver is not initialized and meaning in this package, just do not! Interested in is the script systemd, as the basis. Everything else is just for compatibility.

Lone_Wolf

Administrator

From: Netherlands, Europe

Registered: 2005-10-04

Posts: 15,401

Re: dahdi.service script error after reboot

Have you tried asking the maintainer of dahdi , magicrhesus , about adding a systemd servicefile to the dahdi pacakge ?
He also maintains the asterisk package and recently added a systemd service file to that package.

As to your service file :

- doesn't work on boot
- DOES work after system has been fully initialised.

That suggests dahdi needs something else besides network.target to function properly.

---

Disliking systemd intensely, but not satisfied with alternatives so focusing on taming systemd.

clean chroot building not flexible enough ?
Try clean chroot manager by graysky

lomaker

Member

Registered: 2013-04-10

Posts: 8

Website

Re: dahdi.service script error after reboot

No, I'm don't wrote to DAHDI developer. As for the lack of goals network.target it so I understand. I thought that you just show me what it is not enough.