Patch derives from diff -c \
        /pri/freebsd/releases/6.1-RELEASE/src/etc/newsyslog.conf \
        /site/etc/newsyslog.conf.README
I also have a link from newsyslog.conf.REL=5.5-RELEASE.diff 
but its totaly untried.

*** 6.4-RELEASE/src/etc/newsyslog.conf	Thu Oct  2 04:57:24 2008
--- new-jhs/src/etc/newsyslog.conf	Sun Dec 21 23:29:56 2008
***************
*** 15,39 ****
  # entries to 640 or 600.  For example, some sites will consider the
  # contents of maillog, messages, and lpd-errs to be confidential.  In the
  # future, these defaults may change to more conservative ones.
! #
  # logfilename          [owner:group]    mode count size when  flags [/pid_file] [sig_num]
! /var/log/all.log			600  7	   *	@T00  J
  /var/log/amd.log			644  7	   100	*     J
  /var/log/auth.log			600  7     100  *     JC
  /var/log/console.log			600  5	   100	*     J
  /var/log/cron				600  3	   100	*     JC
! /var/log/daily.log			640  7	   *	@T00  JN
  /var/log/debug.log			600  7     100  *     JC
  /var/log/kerberos.log			600  7	   100	*     J
  /var/log/lpd-errs			644  7	   100	*     JC
! /var/log/maillog			640  7	   *	@T00  JC
  /var/log/messages			644  5	   100	*     JC
! /var/log/monthly.log			640  12	   *	$M1D0 JN
  /var/log/pflog				600  3	   100	*     JB    /var/run/pflogd.pid
  /var/log/ppp.log	root:network	640  3	   100	*     JC
! /var/log/security			600  10	   100	*     JC
! /var/log/sendmail.st			640  10	   *	168   B
  /var/log/slip.log	root:network	640  3	   100	*     JC
  /var/log/weekly.log			640  5	   1	$W6D0 JN
  /var/log/wtmp				644  3	   *	@01T05 B
  /var/log/xferlog			600  7	   100	*     JC
--- 15,55 ----
  # entries to 640 or 600.  For example, some sites will consider the
  # contents of maillog, messages, and lpd-errs to be confidential.  In the
  # future, these defaults may change to more conservative ones.
! 
! # /site/etc/newsyslog.conf.README by jhs@
! # A file to copy over, but Caution:
! # hosts range from 4 to 6, & flag Z uses gzip & J bzip2
! 
  # logfilename          [owner:group]    mode count size when  flags [/pid_file] [sig_num]
! /var/log/all.log			600 31	   *	@T00  J
  /var/log/amd.log			644  7	   100	*     J
  /var/log/auth.log			600  7     100  *     JC
  /var/log/console.log			600  5	   100	*     J
  /var/log/cron				600  3	   100	*     JC
! /var/log/daily.log			640 31	   *	@T00  JN
  /var/log/debug.log			600  7     100  *     JC
+ /var/log/ftpd				640 20	 10000	*     JC
+ /var/log/httpd-access.log		600 20	 10000	*     JC
+ /var/log/httpd-error.log		600 20	 10000	*     JC
  /var/log/kerberos.log			600  7	   100	*     J
  /var/log/lpd-errs			644  7	   100	*     JC
! /var/log/maillog			640 20    10000    *     J
  /var/log/messages			644  5	   100	*     JC
! /var/log/monthly.log			640 12	   *	$M1D0 JN
! /var/log/named		bind:wheel	660 20   10000  *     CJ  # /var/run/named.pid
  /var/log/pflog				600  3	   100	*     JB    /var/run/pflogd.pid
  /var/log/ppp.log	root:network	640  3	   100	*     JC
! /var/log/security			600 10	   100	*     JC
! /var/log/sendmail.st			640 10	   *	168   B
  /var/log/slip.log	root:network	640  3	   100	*     JC
  /var/log/weekly.log			640  5	   1	$W6D0 JN
  /var/log/wtmp				644  3	   *	@01T05 B
  /var/log/xferlog			600  7	   100	*     JC
+ /var/named/var/log/named bind:wheel	660 20   10000  *     CJ  # /var/run/named.pid
+ 
+ # Is named part of syslog structure ? should I expose the PID for restart ?
+ 
+ # FreeBSD 4 just uses the short direct path /var/log/named,
+ # FreeBSD 5 & 6 use symbolic links to /var/named/var/log/named
+ # I need to run newsyslog -n to see what it would do: a cp of a symbolic link
+ # would be OK, a mv would not be OK.