From owner-freebsd-commit  Tue Nov 14 15:40:41 1995
Return-Path: owner-commit
Received: (from root@localhost)
          by freefall.freebsd.org (8.6.12/8.6.6) id PAA28347
          for freebsd-commit-outgoing; Tue, 14 Nov 1995 15:40:41 -0800
Received: (from root@localhost)
          by freefall.freebsd.org (8.6.12/8.6.6) id PAA28312
          for cvs-all-outgoing; Tue, 14 Nov 1995 15:40:30 -0800
Received: (from root@localhost)
          by freefall.freebsd.org (8.6.12/8.6.6) id PAA28276
          for cvs-usrsbin-outgoing; Tue, 14 Nov 1995 15:40:17 -0800
Received: (from peter@localhost)
          by freefall.freebsd.org (8.6.12/8.6.6) id PAA28227
          ; Tue, 14 Nov 1995 15:39:44 -0800
Date: Tue, 14 Nov 1995 15:39:44 -0800
From: Peter Wemm <peter>
Message-Id: <199511142339.PAA28227@freefall.freebsd.org>
To: CVS-commiters, cvs-usrsbin
Subject: cvs commit: src/usr.sbin/syslogd syslogd.c
Sender: owner-commit@FreeBSD.ORG
Precedence: bulk

peter       95/11/14 15:39:43

  Modified:    usr.sbin/syslogd  syslogd.c
  Log:
  With the recent 'make install' change in the kernel build makefiles, an
  `interesting' feature of syslogd turned up.  It calls getbootfile() for each
  log entry.  Since the kernel makefile now changes kern.bootfile when doing
  a 'make install', it's quite startling to see the syslog lines change.
  
  This change makes it call getbootfile() once at startup and cache it,
  saving a syscall per loop, and keeping something a little more asthetically
  pleasing in /var/log/messages...