[Pkg-lirc-maint] Bug#580666: Bug#580666: lircd doesnt log in /var/log/lircd.log

[Stefan Lippers-Hollmann]

Hi

On Monday 10 May 2010, Andreas Marschke wrote:
> Am Freitag 07 Mai 2010, 19:25:17 schrieben Sie:
> > severity 580666 minor
> > thanks
> > 
> > On Friday 07 May 2010, Andreas Marschke wrote:
> > > Package: lirc
> > > Version: 0.8.3-5
> > > Severity: normal
> > > 
> > > As described in the applications documentation it is supposed to log
> > > problems in /var/log but I can't find a log file in /var/log for lirc.
> > > This is independent from  success of starting lirc via /etc/init.d/lirc
> > [...]
> > lirc is using syslog facilities for logging several years by now (iirc
> > pre-etch). While I'll try to check the Debian specific lirc documentation
> > soon, it will unfortunately be low priority for me due to more pressing
> > needs with the current lirc packages. Any specific pointers or patches
> > would be welcome though.
[...]
> Quote [:$ man lircd] 
> ,------------------------------------------------------------------------------
> Files:
> 	The config file for lircd is located in /etc/lircd.conf. lircd has its
> 	own log file in /var/log/lircd  (beginning with  LIRC  version 0.6.1 you
> 	can configure lircd to use syslogd for log messages; then it depends on
> 	your system configuration where log messages will show up).  You can make
> 	lircd reread its config file  and  reopen  its  logfile by sending the HUP
> 	signal to the program. That way you can rotate old log files.
> `------------------------------------------------------------------------------

I don't see a bug here, it's just that the Debian package makes use of this
documented alternative of employing the system's syslog, instead of logging
to a dedicated file.

> Might be better written like:
> ,------------------------------------------------------------------------------
> Files:
> 	The config file for lircd is located in /etc/lirc/lircd.conf. lircd uses 
> 	syslog to log messages. In /etc/lirc/hardware.conf you can configure which
> 	remotecontrole confuguration to use, and wether Modules should be loaded 
> 	at start of the deamon.
> 	You can make lircd reread its config file  and reopen  its  logfile by
> 	sending the HUP	signal to the program. That way you can rotate old log
> 	files.
> `------------------------------------------------------------------------------

The problem with this proposed patch to lircd's manpage is, that it isn't 
upstream'able, given /etc/lirc/hardware.conf being Debian specific and 
applying to the upstream lirc package in any way. As such I'm a little
reluctant to change the correct and even complete, but (in regards to the 
Debian package) maybe slightly too generic manpage. Would adding something
based on your proposal to /usr/share/doc/lirc/README.Debian meet your
expectations as well?

> Would you like a quilt patch for that?
[...]

Usually a unified patch (as used by quilt) is preferred, however this case 
is easy enough either way.

Regards
	Stefan Lippers-Hollmann
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 198 bytes
Desc: This is a digitally signed message part.
URL: <http://lists.alioth.debian.org/pipermail/pkg-lirc-maint/attachments/20100510/47978ed9/attachment.pgp>