Port-arm archive

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index][Old Index]

Re: Retransmission: Minor issue w/ syslog ....



On 05/29/15 18:20, Christos Zoulas wrote:
In article <5568CE47.1080208%hiwaay.net@localhost>,
William A. Mahaffey III <wam%hiwaay.net@localhost> wrote:
	

.... I have a RPiB+ serving as the time server on my LAN. I followed the
excellent instructions @
http://rich-tbp.blogspot.com/2013/03/netbsd-on-rpi-minimizing-disk-writes.html
(posted on this list a few weeks ago) to try to minimize unnecessary
disk I/O to prolong the life of the micro SD 'HDD' that the box uses. I
redirected syslog I/O to another box on the LAN, however I am still
getting some stuff on the RPi syslog file:


May 10 17:06:15 rpi syslogd[11087]: restart
May 11 09:07:17 rpi timed[6547]: measure: kabini1.local did not respond
May 11 09:07:17 rpi timed[6547]: measure: kabini1.local did not respond
May 11 09:31:25 rpi timed[6547]: no reply to time correction from
kabini1.local
May 11 09:47:19 rpi timed[6547]: measure: kabini1.local did not respond
May 11 09:47:19 rpi timed[6547]: measure: kabini1.local did not respond
May 11 09:51:19 rpi timed[6547]: measure: kabini1.local did not respond
May 11 09:51:19 rpi timed[6547]: measure: kabini1.local did not respond
May 11 15:07:05 rpi su: wam to root on /dev/pts/0
May 11 15:14:17 rpi sshd[24420]: error: PAM: authentication error for
root from q6600
May 11 10:20:42 rpi syslogd[11087]: last message repeated 2 times
May 11 15:17:41 rpi su: wam to root on /dev/pts/2
May 11 17:06:16 rpi syslogd[11087]: restart
May 12 17:06:15 rpi syslogd[11087]: restart
May 13 17:06:15 rpi syslogd[11087]: restart
May 14 11:06:16 rpi syslogd[11087]: restart
May 14 17:06:15 rpi syslogd[11087]: restart
May 15 17:06:16 rpi syslogd[11087]: restart
May 16 17:06:16 rpi syslogd[11087]: restart
May 16 23:40:44 rpi su: wam to root on /dev/pts/0
May 17 17:06:16 rpi syslogd[11087]: restart
May 18 16:09:50 rpi su: wam to root on /dev/pts/1
May 18 13:06:16 rpi syslogd[11087]: restart
May 18 17:06:16 rpi syslogd[11087]: restart
May 19 17:06:15 rpi syslogd[11087]: restart
May 20 17:06:15 rpi syslogd[11087]: restart
May 21 04:16:09 rpi su: wam to root on /dev/pts/0
May 21 04:18:27 rpi su: wam to root on /dev/pts/1
May 21 17:06:16 rpi syslogd[11087]: restart
May 22 16:06:15 rpi syslogd[11087]: restart
May 22 17:06:15 rpi syslogd[11087]: restart
May 23 17:06:15 rpi syslogd[11087]: restart
May 24 17:06:15 rpi syslogd[11087]: restart
May 25 17:06:15 rpi syslogd[11087]: restart
May 26 17:06:16 rpi syslogd[11087]: restart
May 26 18:06:15 rpi syslogd[11087]: restart
Wed May 27 15:43:10 MCDT 2015

In particular, the syslogd-restart messages don't show up on the other
box (the rest does). My syslog.conf follows:


rpi # cat syslog.conf
#       $NetBSD: syslog.conf,v 1.9 2004/07/23 03:45:42 mycroft Exp $

*.err;kern.*;auth.notice;authpriv.none;mail.crit        /dev/console

*.err;kern.*;auth.notice;authpriv.none;mail.crit /var/log/messages

*.err;kern.*;auth.notice;authpriv.none;mail.crit        @kabini1

*.info;auth,authpriv,cron,ftp,kern,lpr,mail.none /var/log/messages
kern.debug /var/log/messages

*.info;auth,authpriv,cron,ftp,kern,lpr,mail.none        @kabini1
kern.debug                                              @kabini1

# The authpriv log file should be restricted access; these
# messages shouldn't go to terminals or publically-readable
# files.
auth,authpriv.info /var/log/authlog

cron.info /var/log/cron
ftp.info /var/log/xferlog
lpr.info /var/log/lpd-errs
mail.info /var/log/maillog
#uucp.info /var/spool/uucp/ERRORS

*.emerg                                                 *

*.emerg                                                 @kabini1

#*.notice                                               root
rpi # uname -a
NetBSD rpi 7.0_BETA NetBSD 7.0_BETA (RPI.201503272230Z) evbarm
rpi #

Basically, I duplicated all lines that I found going to messages & sent
them to kabini1, the other box. However, the syslogd-restart messages
don't make it over there. Could be pilot error, but I would like to
eventually comment out *ALL* of the lines writing to my messages file,
w/o missing any messages, no matter how trivial (such as syslogd
restarting). Any clues appreciated. TIA & have a good one.


C'mon, throw me a bone ;-) ....
>From my reading of the code it is possible that none of the messages
created inside the init() function are propagated.

christos


Very well, does that rise to the level of 'bug' ? No sweat either way., bit if so, what do I need to do to propogate it ;-) ? TIA & have a good one ....

--

	William A. Mahaffey III

 ----------------------------------------------------------------------

	"The M1 Garand is without doubt the finest implement of war
	 ever devised by man."
                           -- Gen. George S. Patton Jr.



Home | Main Index | Thread Index | Old Index