Hello all, I am new to -hackers, and I have run into a very frustrating problem. I am using standard printf statements for status info while debugging the parallel port zip driver in PS2 mode. For a reason I have yet to discover, my messages are no longer appearing consistently in my dmesg output. As I move through the debug process, I will enable and disable blocks of debug output, but when I run dmesg, what I see is not the same as what I saw while the machine was rebooting. These same messages usually end up in /var/log/messages, but I can't figure out the pattern. I saw that messages.4 was not gzipped like the others. Could i have overflowed syslogd and messed things up? I would be happy to post info besides my syslog.conf, but I didn't want to clog the list. My work has come to a standstill, since I cannot access the debug output. Please help! Hopefully it is only a small issue that I can learn from and fix promptly. jm -- ------------------------------------------------------------------------ Jonathon McKitrick -- [EMAIL PROTECTED] They laugh because I'm different. I laugh because they're all the same. ------------------------------------------------------------------------
# $FreeBSD: src/etc/syslog.conf,v 1.9.2.1 1999/08/29 14:19:02 peter Exp $ # # Spaces are NOT valid field separators in this file. # Consult the syslog.conf(5) manpage. #*.err;kern.debug;auth.notice;mail.crit /dev/console *.notice;kern.debug;lpr.info;mail.crit;news.err /var/log/messages #security.* /var/log/security mail.info /var/log/maillog lpr.info /var/log/lpd-errs cron.* /var/log/cron *.err root #*.notice;news.err root *.alert /var/log/messages *.emerg * # uncomment these if you're running inn # news.crit /var/log/news/news.crit # news.err /var/log/news/news.err # news.notice /var/log/news/news.notice !startslip *.* /var/log/slip.log !ppp *.* /var/log/ppp.log !ipfw *.* /var/log/ipfw.log
