From owner-freebsd-questions Sat Jan 25 9:23:51 2003 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 A927237B401 for ; Sat, 25 Jan 2003 09:23:50 -0800 (PST) Received: from sage-american.com (adsl-65-71-135-139.dsl.crchtx.swbell.net [65.71.135.139]) by mx1.FreeBSD.org (Postfix) with ESMTP id A103A43F13 for ; Sat, 25 Jan 2003 09:23:49 -0800 (PST) (envelope-from jackstone@sage-one.net) Received: from sagea (sagea.sage-american [192.168.0.3]) by sage-american.com (8.12.6/8.12.6) with SMTP id h0PHNhJ7088022 for ; Sat, 25 Jan 2003 11:23:44 -0600 (CST) (envelope-from jackstone@sage-one.net) Message-Id: <3.0.5.32.20030125112344.02d37ea0@mail.sage-one.net> X-Sender: jackstone@mail.sage-one.net X-Mailer: QUALCOMM Windows Eudora Pro Version 3.0.5 (32) Date: Sat, 25 Jan 2003 11:23:44 -0600 To: freebsd-questions@freebsd.org From: "Jack L. Stone" Subject: Newsyslog Log File Naming Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" X-Spam-Status: No, hits=0.5 required=4.5 tests=SPAM_PHRASE_01_02 version=2.43-jlsrules1 Sender: owner-freebsd-questions@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG Am running FBSD-4.5 and 4.7. Has anyone else experienced a problem with newsyslog trimming the logs and saving the first log as "logname.log.1" instead of "logname.log.0".... While it "jumps over the "log.0" log and saves the log content in "log.1", there is usually a "log.0", but it is empty. This only becomes a problem if another program (like a stats program) is looking for the first log filename to be "log.0". At first, they were named "log.0", but abruptly changed to the two files - the "log.0" as empty and "log.1" with contents. When the stats program is still looking for "log.0", of course no contents. Can change the stats program to look for the "log.1" but don't know if it will decide to change the naming again. Chmod'd files t0 644 and to "B" so the "logfile turned over" line does't confuse anything, but no dice on correcting the naming. See it happening on most logs, not just Apache logs. Can newsyslog be tweaked to make this go back and stay there? I see this on most if not all machines.... been wondering and googled without success. Best regards, Jack L. Stone, Administrator SageOne Net http://www.sage-one.net jackstone@sage-one.net To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-questions" in the body of the message