It looks like the stock logs rotate at 6:24 AM my time? This seems like a
strange "time" to do it to me, is this typical? Or is something not set
local correctly my system?

Is doing it at the stroke of midnight an unwise practice?


--
To UNSUBSCRIBE, email to debian-user-REQUEST@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmaster@lists.debian.org

On Mon, 09 Nov 2009 23:30:28 -0500
vr <debian-user@iotk.net> wrote:

> It looks like the stock logs rotate at 6:24 AM my time? This seems like a
> strange "time" to do it to me, is this typical? Or is something not set
> local correctly my system?

Typical; here's my (stock) '/etc/crontab':

...

# m h dom mon dow user command
17 * * * * root cd / && run-parts --report /etc/cron.hourly
25 6 * * * root test -x /usr/sbin/anacron || ( cd / && run-parts --report /etc/cron.daily )
47 6 * * 7 root test -x /usr/sbin/anacron || ( cd / && run-parts --report /etc/cron.weekly )
52 6 1 * * root test -x /usr/sbin/anacron || ( cd / && run-parts --report /etc/cron.monthly )
#

So the /etc/cron.daily stuff, which includes a logrotate invocation, is
run at 6:25.

> Is doing it at the stroke of midnight an unwise practice?

I don't see any reason why it should be.

Celejar
--
foffl.sourceforge.net - Feeds OFFLine, an offline RSS/Atom aggregator
mailmin.sourceforge.net - remote access via secure (OpenPGP) email
ssuds.sourceforge.net - A Simple Sudoku Solver and Generator


--
To UNSUBSCRIBE, email to debian-user-REQUEST@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmaster@lists.debian.org

Hello VR,

actually it is configured in `/etc/crontab' , see crontab(1) crontab(5) cron(8) with man for further details:
I guess it is a good idea to adapt the configuration with respect to the use of the computer.
If you box is a laptop, you may consider to install anachron.

For some people, like me, minnight is really not appropriate :-)

hth,
Jerome

vr wrote:

It looks like the stock logs rotate at 6:24 AM my time? This seems like a
strange "time" to do it to me, is this typical? Or is something not set
local correctly my system?

Is doing it at the stroke of midnight an unwise practice?




--
Jerome BENOIT
jgmbenoit_at_mailsnare_dot_net


--
To UNSUBSCRIBE, email to debian-user-REQUEST@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmaster@lists.debian.org

On Tue, 10 Nov 2009 12:48:21 +0800, Jerome BENOIT
<jgmbenoit@mailsnare.net>
wrote:
> Hello VR,
>
> actually it is configured in `/etc/crontab' , see crontab(1) crontab(5)
> cron(8) with man for further details:

Thanks for this. Based on an earlier list reply I was able to set it
before midnight my time last night so it is resolved.

> I guess it is a good idea to adapt the configuration with respect to the
> use of the computer.
> If you box is a laptop, you may consider to install anachron.
>

It is on my syslog receiver for a relatively low volume mail server.

> For some people, like me, minnight is really not appropriate :-)

I would be interested to hear "why" it would not be appropriate in your
case because perhaps you've got a scenario that might apply to me now or in
the future. I can see high volume being a factor if logs grow so large per
minute/hour/day they become unmanageable? But I am interested to know your
experiences.


--
To UNSUBSCRIBE, email to debian-user-REQUEST@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmaster@lists.debian.org

vr schreef:

On Tue, 10 Nov 2009 12:48:21 +0800, Jerome BENOIT

If you box is a laptop, you may consider to install anachron.

...

For some people, like me, minnight is really not appropriate :-)


I would be interested to hear "why" it would not be appropriate in your
case because perhaps you've got a scenario that might apply to me now or in
the future. I can see high volume being a factor if logs grow so large per
minute/hour/day they become unmanageable? But I am interested to know your
experiences.

Because he and his computer are sleeping then

The reason not to start at midnight is that this timing schedule is set
up to avoid cron hourly, daily, weekly, and monthly to run at the same
time. And it usually does not matter *when* it happens, as long *as* it
happens.


Sjoerd

On Mon, Nov 09, 2009 at 11:30:28PM -0500, vr wrote:

> Is doing it at the stroke of midnight an unwise practice?

Well, on a home system it doesn't matter much. For production use,
though, you generally want to avoid CPU or I/O spikes, and running a ton
of stuff at the same time would be a Bad Thing (tm). Since midnight
tends to be an obvious choice for many things, a lot of system scripts
are set to kick off elsewhen.

--
"Oh, look: rocks!"
-- Doctor Who, "Destiny of the Daleks"


--
To UNSUBSCRIBE, email to debian-user-REQUEST@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmaster@lists.debian.org