From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from pigeon.gentoo.org ([208.92.234.80] helo=lists.gentoo.org) by finch.gentoo.org with esmtp (Exim 4.60) (envelope-from ) id 1NAJv0-0007hP-Uu for garchives@archives.gentoo.org; Tue, 17 Nov 2009 09:00:11 +0000 Received: from pigeon.gentoo.org (localhost [127.0.0.1]) by pigeon.gentoo.org (Postfix) with SMTP id 8B472E0A7E; Tue, 17 Nov 2009 08:59:43 +0000 (UTC) Received: from mail.digimed.co.uk (82-69-83-178.dsl.in-addr.zen.co.uk [82.69.83.178]) by pigeon.gentoo.org (Postfix) with ESMTP id 3FD56E0A7E for ; Tue, 17 Nov 2009 08:59:43 +0000 (UTC) Received: from digimed.co.uk (majikthise.digimed.co.uk [192.168.1.2]) (using TLSv1 with cipher DHE-RSA-AES128-SHA (128/128 bits)) (No client certificate requested) by mail.digimed.co.uk (Postfix) with ESMTPSA id 54EEC5040F2 for ; Tue, 17 Nov 2009 08:59:42 +0000 (GMT) Date: Tue, 17 Nov 2009 08:59:34 +0000 From: Neil Bothwick To: gentoo-user@lists.gentoo.org Subject: Re: [gentoo-user] strange cron messages... Message-ID: <20091117085934.3f89e8a4@digimed.co.uk> In-Reply-To: <4B017607.80102@caf.com.tr> References: <4AFEB84B.2010107@gmail.com> <200911141753.24403.wonko@wonkology.org> <200911151145.28867.michaelkintzios@gmail.com> <4B00F9AE.8010209@caf.com.tr> <20091116124606.055ceff5@digimed.co.uk> <4B017607.80102@caf.com.tr> Organization: Digital Media Production X-Mailer: Claws Mail 3.7.3cvs13 (GTK+ 2.18.3; i686-pc-linux-gnu) X-GPG-Fingerprint: 7260 0F33 97EC 2F1E 7667 FE37 BA6E 1A97 4375 1903 Precedence: bulk List-Post: List-Help: List-Unsubscribe: List-Subscribe: List-Id: Gentoo Linux mail X-BeenThere: gentoo-user@lists.gentoo.org Reply-to: gentoo-user@lists.gentoo.org Mime-Version: 1.0 Content-Type: multipart/signed; micalg=PGP-SHA1; boundary="Sig_/2YFV7Pl6=D_M.rxM1kYqE1V"; protocol="application/pgp-signature" X-Archives-Salt: 8396f262-5a44-4d06-9017-67afb759bb53 X-Archives-Hash: 6fe3df190bf51d4af2900f56ab91e79e --Sig_/2YFV7Pl6=D_M.rxM1kYqE1V Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: quoted-printable On Mon, 16 Nov 2009 17:55:51 +0200, Eray Aslan wrote: > On 16.11.2009 14:46, Neil Bothwick wrote: > > On Mon, 16 Nov 2009 09:05:18 +0200, Eray Aslan wrote: > >=20 > >> - No need to logrotate with time based filenames. Hence, no > >> need to "kill -HUP" the syslog daemon. No missed logs. > >=20 > > Then how do you get the server to use the new logfile names each > > day/week? >=20 > It creates and uses a new file each hour/day/etc. Perhaps, you missed > the file(...) directive? I didn't miss it. My question was how to you get the process to USE the new file. Unless you SIGHUP the process, it will continue using the config in pace when it started. > > You only need to send a SIGHUP to the server using that log > > facility, so syslog would not be affected in your example. >=20 > I can't parse this. The point is avoiding SIGHUP so that we do not miss > any log messages. You wouldn't miss a log messsage by sending a SIGHUP to your mail server, the logger woulsd keep running. > OP asked how one manages log files without logrotate and the answer is > with time based file names. It has the additional benefit of avoiding > SIGHUP. I understood both the question and answer, but it seems like you are avoiding logrotate by re-implementing it in your scripts. --=20 Neil Bothwick An example of hard water is ice. --Sig_/2YFV7Pl6=D_M.rxM1kYqE1V Content-Type: application/pgp-signature; name=signature.asc Content-Disposition: attachment; filename=signature.asc -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.13 (GNU/Linux) iEYEARECAAYFAksCZfwACgkQum4al0N1GQPuMQCdEUgpmjZGlUbwbXiMRjxQct9R yKMAn0LUM+zLqhzzkqPuGYeR93F7TttZ =X3CY -----END PGP SIGNATURE----- --Sig_/2YFV7Pl6=D_M.rxM1kYqE1V--