From owner-freebsd-current@FreeBSD.ORG Fri Feb 25 19:03:21 2005 Return-Path: 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 6939016A4CE for ; Fri, 25 Feb 2005 19:03:21 +0000 (GMT) Received: from zinc.pathwaynet.com (zinc.pathwaynet.com [216.46.200.95]) by mx1.FreeBSD.org (Postfix) with ESMTP id 29BB043D53 for ; Fri, 25 Feb 2005 19:03:21 +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 1D4kkB-000Ka9-KO; Fri, 25 Feb 2005 14:03:19 -0500 Date: Fri, 25 Feb 2005 14:03:19 -0500 (EST) From: Mike Sturdee X-X-Sender: sturdee@sun.mikesweb.com To: Lars Erik Gullerud In-Reply-To: <20050225185200.I13634@electra.nolink.net> Message-ID: <20050225140135.X691@sun.mikesweb.com> References: <20050224190926.Y41330@sun.mikesweb.com> <20050225185200.I13634@electra.nolink.net> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed cc: current@FreeBSD.org Subject: Re: 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 List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 25 Feb 2005 19:03:21 -0000 On Fri, 25 Feb 2005, Lars Erik Gullerud wrote: > On Thu, 24 Feb 2005, Mike Sturdee wrote: > >> 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? > > Well, 1024 bytes is the max length specified in RFC 3164: > > 4.1 syslog Message Parts > > The full format of a syslog message seen on the wire has three > discernable parts. The first part is called the PRI, the second part > is the HEADER, and the third part is the MSG. The total length of > the packet MUST be 1024 bytes or less. There is no minimum length of > the syslog message although sending a syslog packet with no contents > is worthless and SHOULD NOT be transmitted. > > Now, 3164 is of course only an Informational RFC, but breaking it can > obviously still have potential compatibility issues. > > /leg > > Thanks for the info. -Mike