public inbox for gentoo-user@lists.gentoo.org
 help / color / mirror / Atom feed
From: Neil Bothwick <neil@digimed.co.uk>
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] strange cron messages...
Date: Tue, 17 Nov 2009 08:59:34 +0000	[thread overview]
Message-ID: <20091117085934.3f89e8a4@digimed.co.uk> (raw)
In-Reply-To: <4B017607.80102@caf.com.tr>

[-- Attachment #1: Type: text/plain, Size: 1368 bytes --]

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:
> > 
> >>     - 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?
> 
> 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.
> 
> 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.


-- 
Neil Bothwick

An example of hard water is ice.

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 198 bytes --]

  parent reply	other threads:[~2009-11-17  9:00 UTC|newest]

Thread overview: 24+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-11-14 14:01 [gentoo-user] strange cron messages Jarry
2009-11-14 16:53 ` Alex Schuster
2009-11-15 11:45   ` Mick
2009-11-16  7:05     ` Eray Aslan
2009-11-16  8:08       ` Graham Murray
2009-11-16 11:10         ` Eray Aslan
2009-11-16 12:46       ` Neil Bothwick
2009-11-16 15:55         ` Eray Aslan
2009-11-16 18:04           ` Alan McKinnon
2009-11-17  8:59           ` Neil Bothwick [this message]
2009-11-17 12:08             ` Eray Aslan
2009-11-17 12:43               ` Alan McKinnon
2009-11-17 15:08               ` Neil Bothwick
2009-11-17 15:25                 ` Eray Aslan
2009-11-17 16:08                   ` Neil Bothwick
2009-11-17 16:14                     ` Alan McKinnon
2009-11-16 17:38     ` Alex Schuster
2009-11-16 17:56   ` Jarry
2009-11-16 18:47     ` Alex Schuster
2009-11-16 20:09       ` Neil Walker
2009-11-16 22:14         ` Alan McKinnon
2009-11-17  2:35           ` Neil Walker
2009-11-17  8:32             ` Alan McKinnon
2009-11-16 22:31         ` Alex Schuster

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20091117085934.3f89e8a4@digimed.co.uk \
    --to=neil@digimed.co.uk \
    --cc=gentoo-user@lists.gentoo.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox