From owner-freebsd-current@FreeBSD.ORG  Fri Feb 25 00:13:07 2005
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Delivered-To: freebsd-current@freebsd.org
Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125])
	by hub.freebsd.org (Postfix) with ESMTP id 0A8CD16A4CE
	for <current@FreeBSD.org>; Fri, 25 Feb 2005 00:13:07 +0000 (GMT)
Received: from zinc.pathwaynet.com (zinc.pathwaynet.com [216.46.200.95])
	by mx1.FreeBSD.org (Postfix) with ESMTP id D982843D3F
	for <current@FreeBSD.org>; Fri, 25 Feb 2005 00:13:06 +0000 (GMT)
	(envelope-from sturdee@pathwaynet.com)
Received: from sun.mikesweb.com ([216.46.200.114])
        by zinc.pathwaynet.com with esmtp (Exim 4.43)
        id 1D4T6Q-000DSY-Bp
 for current@FreeBSD.org; Thu, 24 Feb 2005 19:13:06 -0500
Date: Thu, 24 Feb 2005 19:13:06 -0500 (EST)
From: Mike Sturdee <sturdee@pathwaynet.com>
X-X-Sender: sturdee@sun.mikesweb.com
To: current@FreeBSD.org
Message-ID: <20050224190926.Y41330@sun.mikesweb.com>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed
Subject: syslog msg size
X-BeenThere: freebsd-current@freebsd.org
X-Mailman-Version: 2.1.1
Precedence: list
List-Id: Discussions about the use of FreeBSD-current
	<freebsd-current.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-current>,
	<mailto:freebsd-current-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-current>
List-Post: <mailto:freebsd-current@freebsd.org>
List-Help: <mailto:freebsd-current-request@freebsd.org?subject=help>
List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-current>,
	<mailto:freebsd-current-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Fri, 25 Feb 2005 00:13:07 -0000

In trying to receive syslog(3) messages longer than 1024 bytes with 
syslog-ng, I'm noticing FreeBSD's library function syslog(3) is the only 
syslog implementation besides Solaris limited to 1024.. Has removing this 
limitation ever been considered?

-Mike