From owner-freebsd-stable Mon Oct 12 07:23:11 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id HAA29502 for freebsd-stable-outgoing; Mon, 12 Oct 1998 07:23:11 -0700 (PDT) (envelope-from owner-freebsd-stable@FreeBSD.ORG) Received: from passer.osg.gov.bc.ca (passer.osg.gov.bc.ca [142.32.110.29]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id HAA29479 for ; Mon, 12 Oct 1998 07:23:04 -0700 (PDT) (envelope-from cy@cschuber.net.gov.bc.ca) Received: (from uucp@localhost) by passer.osg.gov.bc.ca (8.8.8/8.6.10) id HAA00685; Mon, 12 Oct 1998 07:22:41 -0700 (PDT) Received: from cschuber.net.gov.bc.ca(142.31.240.113), claiming to be "cwsys.cwsent.com" via SMTP by passer.osg.gov.bc.ca, id smtpdtVT682; Mon Oct 12 07:22:01 1998 Received: (from uucp@localhost) by cwsys.cwsent.com (8.8.8/8.6.10) id HAA22643; Mon, 12 Oct 1998 07:21:58 -0700 (PDT) Message-Id: <199810121421.HAA22643@cwsys.cwsent.com> Received: from localhost.cwsent.com(127.0.0.1), claiming to be "cwsys" via SMTP by localhost.cwsent.com, id smtpdI22639; Mon Oct 12 07:21:50 1998 X-Mailer: exmh version 2.0.2 2/24/98 Reply-to: Cy Schubert - ITSD Open Systems Group From: Cy Schubert - ITSD Open Systems Group X-Sender: cy To: Igor Roshchin cc: stable@FreeBSD.ORG Subject: Re: syslogd and syslog.conf In-reply-to: Your message of "Sun, 11 Oct 1998 16:03:30 CDT." <199810112103.QAA14342@alecto.physics.uiuc.edu> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Mon, 12 Oct 1998 07:21:49 -0700 Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > Hello! > > Those who are reading freebsd-security, already saw this. > For others, briefly: > There was a question and few followups about the syslogd > which doesn't allow to have spaces between the first and the second > field in /etc/syslog.conf . > (this is a feature of syslogd in some (or all ?) other Unices). > Only s are allowed. Having had a chance to think about this, I think that a modification of this nature, which would make syslogd somewhat incompatible, e.g. not the same as, syslogd's on other UNIX systems, a name change should also be considered. In keeping with tradition, this new syslogd should be called nsyslogd. Taking a compromise position, I think that there are a couple of options: 1. Define the characters that syslogd should recognize and have the syslogd Makefile build syslogd and nsyslogd, or 2. Make the new behavior an option, "-n" for new behavior, or have syslogd see whether it was invoked via the syslogd command or nsyslogd command and invoke the new behavior based on that, or 3. Make the proposed changes a port based on FreeBSD code, similar to what has been done with colorls. Those who wish to use the proposed changes can install the port. (The port could even support non-standard syslog features like the use of TCP in addition to UDP or even encryption). I tend to favour options 2 and 3 over option 1. Regards, Phone: (250)387-8437 Cy Schubert Fax: (250)387-5766 Open Systems Group Internet: cschuber@uumail.gov.bc.ca ITSD Cy.Schubert@gems8.gov.bc.ca Government of BC To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message