From owner-freebsd-questions@FreeBSD.ORG Tue Apr 8 10:50:59 2003 Return-Path: Delivered-To: freebsd-questions@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id CAA6C37B404 for ; Tue, 8 Apr 2003 10:50:59 -0700 (PDT) Received: from portal.aphroland.org (portal.aphroland.org [216.39.174.24]) by mx1.FreeBSD.org (Postfix) with ESMTP id AD0C943FCB for ; Tue, 8 Apr 2003 10:50:58 -0700 (PDT) (envelope-from freebsd@aphroland.org) Received: by portal.aphroland.org (Postfix, from userid 1010) id 5D2A8278019; Tue, 8 Apr 2003 10:50:58 -0700 (PDT) Received: from portal.aphroland.org (debian [127.0.0.1]) by portal.aphroland.org (Postfix) with SMTP id 0E24D278017 for ; Tue, 8 Apr 2003 10:50:54 -0700 (PDT) Received: from redhat.aphroland.org ([10.10.10.7]) (SquirrelMail authenticated user aphro) by webmail.linuxpowered.net with HTTP; Tue, 8 Apr 2003 10:50:55 -0700 (PDT) Message-ID: <50273.10.10.10.7.1049824255.squirrel@webmail.linuxpowered.net> Date: Tue, 8 Apr 2003 10:50:55 -0700 (PDT) From: "nate" To: X-XheaderVersion: 1.1 X-UserAgent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.3a) Gecko/20021207 Phoenix/0.5 X-Priority: 3 Importance: Normal X-Mailer: SquirrelMail (version 1.2.9) MIME-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1 Content-Transfer-Encoding: 8bit X-Spam-Status: No, hits=1.4 required=5.0 tests=MSG_ID_ADDED_BY_MTA_3,SPAM_PHRASE_01_02 version=2.42 X-Spam-Level: * X-Sanitizer: This message has been sanitized! X-Sanitizer-URL: http://mailtools.anomy.net/ X-Sanitizer-Rev: $Id: Sanitizer.pm,v 1.54 2002/02/15 16:59:07 bre Exp $ Subject: syslog-ng weirdness upgrading from 4.7 to 4.8 X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 08 Apr 2003 17:51:00 -0000 I upgraded to freebsd 4.8 from 4.7 last week and portupgrade reported it upgraded syslog-ng from syslog-ng-1.4.17 to syslog-ng-1.6.0.r1 and libol-0.2.23 to libol-0.3.9 (libol is required by syslog-ng) and while syslog-ng is working I cannot get it to store files that are group readable. In the past this has been no problem, but now syslog-ng seems to insist upon permissions of 600. I even went sofar as to set a umask of 137, in the syslog-ng init script, which sets permissions on newly created files to 640, but that seems to have no effect, syslog-ng randomly(?) changes permissions back to 600 even after I set them to 640 myself. I have logrotate run weekly and create files that are 640: /var/log-ng/* { create 0640 root wheel notifempty errors my@email.address rotate 26 weekly compress delaycompress olddir /var/log-ng/archive missingok } but syslog-ng again changes it back to 600. driving me crazy :) I don't see anything in the syslog-ng manpage that can set file permissions..so I'm at a loss! I have been running syslog-ng on freebsd 4.7 with no problems since about september 2002. anyone else experience this? thanks nate