Arch Linux

Please read this before reporting a bug:
https://wiki.archlinux.org/title/Bug_reporting_guidelines

Do NOT report bugs when a package is just outdated, or it is in the AUR. Use the 'flag out of date' link on the package page, or the Mailing List.

REPEAT: Do NOT report bugs for outdated packages!
Tasklist

FS#42412 - [lirc-utils] lircd does not started correctly from systemd, if the drop-in feature used

Attached to Project: Arch Linux
Opened by Dikiy (dikiy) - Thursday, 16 October 2014, 18:37 GMT
Last edited by Doug Newgard (Scimmia) - Tuesday, 21 October 2014, 18:17 GMT
Task Type Bug Report
Category Packages: Extra
Status Closed
Assigned To Lukas Fleischer (lfleischer)
Architecture All
Severity Medium
Priority Normal
Reported Version
Due in Version Undecided
Due Date Undecided
Percent Complete 100%
Votes 0
Private No

Details

Description:
I want to pass correct parameters to lircd, and use drop in for it. lircd daemon seems to be started, but then dies immediatly.

Additional info:
* package version(s)
lirc 1:0.9.1.a-5
extra lirc-utils 1:0.9.1.a-5
libsystemd 216-3
systemd 216-3
systemd-sysvcompat 216-3

* config and/or log files etc.
/etc/systemd/system/lircd.service.d/lircd.conf:

[Service]
Type=simple
ExecStart=
ExecStart=/usr/bin/lircd --driver=atilibusb --device=/dev/lirc0

Steps to reproduce:
1. create a dir /etc/systemd/system/lircd.service.d/
2. create a lircd.conf within the text above.
3. systemctl enable lircd.service
4. systemctl start lircd.service

It can be, that you need to pass another parameter to lircd, and not the --driver=atilibusb

It seems to be a problem with systemd, because if I start lircd with these parameters directly it runs ok.
This task depends upon

Closed by  Doug Newgard (Scimmia)
Tuesday, 21 October 2014, 18:17 GMT
Reason for closing:  Not a bug
Comment by Doug Newgard (Scimmia) - Thursday, 16 October 2014, 18:51 GMT
Why is it dying? We need some log info.

And why do you have the "Type" in your conf file?
Comment by Dikiy (dikiy) - Thursday, 16 October 2014, 19:14 GMT
I dont know, why it dies. I have Type in conf file, because I have tried to get it work. But nothing changes.

some logs from console attached.
   log.txt (1.5 KiB)
Comment by Doug Newgard (Scimmia) - Thursday, 16 October 2014, 19:31 GMT
Why did you remove the --nodaemon option?
Comment by Dikiy (dikiy) - Thursday, 16 October 2014, 19:37 GMT
Ok. It works now, thanks!!

I removed this option, because I don't understand precisely how systemd works :) And with previous version (I didnt update my system ~5 months) of systemd the problem did not exist, even without this option.

I wondered first, why this option exists there.... Now I know it.

Do I understand right, that without nodaemon, lircd forks in the background and systemd lose the control about it? But why lircd dies?
Comment by Dikiy (dikiy) - Tuesday, 21 October 2014, 17:42 GMT
I think, the bug can be closed.

Loading...