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 1NA2Ai-0007W0-5n for garchives@archives.gentoo.org; Mon, 16 Nov 2009 14:03:12 +0000 Received: from pigeon.gentoo.org (localhost [127.0.0.1]) by pigeon.gentoo.org (Postfix) with SMTP id 4111DE09BC for ; Mon, 16 Nov 2009 14:03:10 +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 25216E0698 for ; Mon, 16 Nov 2009 12:46:18 +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 0EC224B84EF for ; Mon, 16 Nov 2009 12:46:16 +0000 (GMT) Date: Mon, 16 Nov 2009 12:46:06 +0000 From: Neil Bothwick To: gentoo-user@lists.gentoo.org Subject: Re: [gentoo-user] strange cron messages... Message-ID: <20091116124606.055ceff5@digimed.co.uk> In-Reply-To: <4B00F9AE.8010209@caf.com.tr> References: <4AFEB84B.2010107@gmail.com> <200911141753.24403.wonko@wonkology.org> <200911151145.28867.michaelkintzios@gmail.com> <4B00F9AE.8010209@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_/Nhez_R6CnKRrvbXGayGV2A+"; protocol="application/pgp-signature" X-Archives-Salt: 6f0b7f72-5fe3-4edd-98d6-ec81e14fc659 X-Archives-Hash: 852ccf7c4b3581fbc07c4786e038d702 --Sig_/Nhez_R6CnKRrvbXGayGV2A+ Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: quoted-printable On Mon, 16 Nov 2009 09:05:18 +0200, Eray Aslan wrote: > - No need to logrotate with time based filenames. Hence, no need to > "kill -HUP" the syslog daemon. No missed logs. Then how do you get the server to use the new logfile names each day/week? You only need to send a SIGHUP to the server using that log facility, so syslog would not be affected in your example. > - Easier to get the log files to a central server with time based > filenames. Logrotate can use datestamps in the rotated logfile names. You can use the postrotate facility to copy them automatically. --=20 Neil Bothwick Uhura: Captain, you're being flamed on channel one. --Sig_/Nhez_R6CnKRrvbXGayGV2A+ Content-Type: application/pgp-signature; name=signature.asc Content-Disposition: attachment; filename=signature.asc -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.13 (GNU/Linux) iEYEARECAAYFAksBSZYACgkQum4al0N1GQPO7QCgmZv1OCA3JdZuA6mQShS2HRQS 1K4An0VoM7KRnzUiFvPWZFcFYG73Z2Lb =JqWO -----END PGP SIGNATURE----- --Sig_/Nhez_R6CnKRrvbXGayGV2A+--