On Sunday 12 August 2007 19:47, Patrick Cernko wrote:
Hi list, hi Klaus,
Klaus Schmidinger wrote:
The changes since version 1.5.6:
- All logging now goes to LOG_ERR, because some systems split error, info and debug messages into separate files, which repeatedly caused extra efforts to find out when incomplete log excerpts were attached to problem reports in the past.
should this change be permanent, configurable or will it only apply for the developer releases?
I vote for a configurable solution. Softdevice has such a mode (not realized for all messages but ..) which allows some kind of messages to be turned off (info, debug and trace). Messages can be written to stdout/stderr or to a configureable file with optionally current PID appended.
In my opinion, it is a benefit to redirect different log levels to different files for normal operation. In case of a bug, a commandline/setup option could select this behaviour to produce full logs.
On 08/12/07 20:51, Stefan Lucke wrote:
On Sunday 12 August 2007 19:47, Patrick Cernko wrote:
Hi list, hi Klaus,
Klaus Schmidinger wrote:
The changes since version 1.5.6:
- All logging now goes to LOG_ERR, because some systems split error, info and debug messages into separate files, which repeatedly caused extra efforts to find out when incomplete log excerpts were attached to problem reports in the past.
should this change be permanent, configurable or will it only apply for the developer releases?
I vote for a configurable solution. Softdevice has such a mode (not realized for all messages but ..) which allows some kind of messages to be turned off (info, debug and trace). Messages can be written to stdout/stderr or to a configureable file with optionally current PID appended.
You can control how much VDR logs via the -l option.
In my opinion, it is a benefit to redirect different log levels to different files for normal operation. In case of a bug, a commandline/setup option could select this behaviour to produce full logs.
Believe me, after having gone through the "your log is incomplete, please send all the VDR log entries from all the files your logging setup might spread the into" often enough, you would also switch to a *single* log file.
Klaus
Personally, I like the idea of vdr having a dedicated logfile. And even more if the path/filename of this logfile can be defined by the user.
VDR User wrote:
Personally, I like the idea of vdr having a dedicated logfile. And even more if the path/filename of this logfile can be defined by the user.
It can, at least with syslog-ng. I added these statements to my syslog-ng.conf:
destination df_vdr { file("/var/log/vdr.log" owner("root") group("vdr") perm(0640)); };
filter f_vdr { program("vdr"); }; filter f_novdr { not program("vdr"); };
log { source(s_all); filter(f_vdr); destination(df_vdr); };
If you do not want, to have vdr log _also_ to the other log files, you can use the f_novdr filter in those log-statements, e.g. in Debian:
# *.*;auth,authpriv.none -/var/log/syslog log { source(s_all); filter(f_syslog); filter(f_novdr); destination(df_syslog); };
@Klaus: I see your problem. Let's leave it like this if it helps you.
@Stefan: Replacing syslog-logging with own file logging is not a solution for my concern. I always welcomed the vdr way of logging as it directly allowes to redirect the log to own destinations (even remotely) adntools like logrotate also take care of not filling up the disk. But I also see the need of a user/GUI program to have logging to something else than syslog (which mostly can't be checked by an unpriveleged user).
So long,
-
Klaus Schmidinger -
Patrick Cernko -
Stefan Lucke -
VDR User