All of lore.kernel.org
 help / color / mirror / Atom feed
* Error logging
@ 2009-06-22 16:35 David Liontooth
  0 siblings, 0 replies; only message in thread
From: David Liontooth @ 2009-06-22 16:35 UTC (permalink / raw)
  To: video4linux-list

v4l device errors, such as VBI read errors, are no longer showing up 
anywhere in my logs -- not in dmesg, not in syslog, not in 
/var/log/debug. I'm running Debian sid.

I see them in the terminal window where I run the recording process. 
They used to show up in dmesg and syslog.

Does anybody know what I can do to direct these errors to syslog? Is 
this change due to my local configuration or upstream changes in logging?

Here's my syslog.conf:

#  /etc/syslog.conf     Configuration file for syslogd.
#
#                       For more information see syslog.conf(5)
#                       manpage.

#
# First some standard logfiles.  Log by facility.
#

auth,authpriv.*                 /var/log/auth.log
*.*;auth,authpriv.none          -/var/log/syslog
cron.*                          /var/log/cron.log
daemon.*                        -/var/log/daemon.log
kern.*                          -/var/log/kern.log
lpr.*                           -/var/log/lpr.log
mail.*                          -/var/log/mail.log
user.*                          -/var/log/user.log
uucp.*                          /var/log/uucp.log

Appreciate any insights into this.

Cheers,
David


--
video4linux-list mailing list
Unsubscribe mailto:video4linux-list-request@redhat.com?subject=unsubscribe
https://www.redhat.com/mailman/listinfo/video4linux-list

^ permalink raw reply	[flat|nested] only message in thread

only message in thread, other threads:[~2009-06-22 16:35 UTC | newest]

Thread overview: (only message) (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2009-06-22 16:35 Error logging David Liontooth

This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.