On Wed, Feb 26, 2014 at 06:43:36AM -0500, Tony Baldwin wrote:
On Wed, Feb 26, 2014 at 06:41:22AM -0500, Tony Baldwin wrote:
On Wed, Feb 26, 2014 at 12:09:05PM +0200, Andrei POPESCU wrote:
On Ma, 25 feb 14, 13:53:39, Tazman Deville wrote:
I DO have anacron installed.
Well,
On Ma, 25 feb 14, 13:53:39, Tazman Deville wrote:
I DO have anacron installed.
Well, purge (not remove) it then, or adjust /etc/anacrontab as needed ;)
Kind regards,
Andrei
--
http://wiki.debian.org/FAQsFromDebianUser
Offtopic discussions among Debian users and developers:
On Wed, Feb 26, 2014 at 12:09:05PM +0200, Andrei POPESCU wrote:
On Ma, 25 feb 14, 13:53:39, Tazman Deville wrote:
I DO have anacron installed.
Well, purge (not remove) it then, or adjust /etc/anacrontab as needed ;)
Kind regards,
Andrei
Thanks, Andrei,
But could you explain why I
On Wed, Feb 26, 2014 at 06:41:22AM -0500, Tony Baldwin wrote:
On Wed, Feb 26, 2014 at 12:09:05PM +0200, Andrei POPESCU wrote:
On Ma, 25 feb 14, 13:53:39, Tazman Deville wrote:
I DO have anacron installed.
Well, purge (not remove) it then, or adjust /etc/anacrontab as needed ;)
2014-02-26 12:43 GMT+01:00 Tony Baldwin t...@tonybaldwin.info:
On Wed, Feb 26, 2014 at 06:41:22AM -0500, Tony Baldwin wrote:
On Wed, Feb 26, 2014 at 12:09:05PM +0200, Andrei POPESCU wrote:
On Ma, 25 feb 14, 13:53:39, Tazman Deville wrote:
I DO have anacron installed.
Well,
On Mi, 26 feb 14, 06:41:22, Tony Baldwin wrote:
On Wed, Feb 26, 2014 at 12:09:05PM +0200, Andrei POPESCU wrote:
On Ma, 25 feb 14, 13:53:39, Tazman Deville wrote:
I DO have anacron installed.
Well, purge (not remove) it then, or adjust /etc/anacrontab as needed ;)
Thanks, Andrei,
On Mon, Feb 24, 2014 at 11:15:19PM +0200, Andrei POPESCU wrote:
On Lu, 24 feb 14, 15:06:48, Tazman Deville wrote:
On Mon, Feb 24, 2014 at 01:57:02PM +0100, Tazman Deville wrote:
I have a little server running here in my office,
and logrotate kept running at c. 7am, and using up 100% CPU.
On Mon, Feb 24, 2014 at 07:38:24PM -0300, André Nunes Batista wrote:
On Mon, 2014-02-24 at 13:57 +0100, Tazman Deville wrote:
I have a little server running here in my office,
and logrotate kept running at c. 7am, and using up 100% CPU.
I changed the line in /etc/crontab to run cron.daily
On Mon, Feb 24, 2014 at 01:57:02PM +0100, Tazman Deville wrote:
I have a little server running here in my office,
and logrotate kept running at c. 7am, and using up 100% CPU.
Logrotate *itself* shouldn't use much CPU. But there are a couple of
things I can think that might make it do so:
* A
On Tue, Feb 25, 2014 at 01:10:38PM +, Darac Marjal wrote:
On Mon, Feb 24, 2014 at 01:57:02PM +0100, Tazman Deville wrote:
I have a little server running here in my office,
and logrotate kept running at c. 7am, and using up 100% CPU.
Logrotate *itself* shouldn't use much CPU. But there
2014-02-25 13:53 GMT+01:00 Tazman Deville tazmande...@gmx.com:
My /etc/crontab is as follows:
SHELL=/bin/sh
PATH=/usr/local/sbin:/usr/local/bin:/sbin:/bin:/usr/sbin:/usr/bin
# m h dom mon dow user command
17 ** * * rootcd / run-parts --report /etc/cron.hourly
15 4* * *
On Tue, Feb 25, 2014 at 02:31:43PM +0100, Raffaele Morelli wrote:
2014-02-25 13:53 GMT+01:00 Tazman Deville tazmande...@gmx.com
mailto:tazmande...@gmx.com:
My /etc/crontab is as follows:
SHELL=/bin/sh
PATH=/usr/local/sbin:/usr/local/bin:/sbin:/bin:/usr/sbin:/usr/bin
# m h dom mon dow
I have a little server running here in my office,
and logrotate kept running at c. 7am, and using up 100% CPU.
I changed the line in /etc/crontab to run cron.daily scripts
at 4:15am, instead of 7:whateveritwas am.
15 4 * * *
Also, in cron.daily/logrotate
I added
nice -n 15
I made these changes
On Mon, Feb 24, 2014 at 01:57:02PM +0100, Tazman Deville wrote:
I have a little server running here in my office,
and logrotate kept running at c. 7am, and using up 100% CPU.
I changed the line in /etc/crontab to run cron.daily scripts
at 4:15am, instead of 7:whateveritwas am.
15 4 * * *
On Lu, 24 feb 14, 15:06:48, Tazman Deville wrote:
On Mon, Feb 24, 2014 at 01:57:02PM +0100, Tazman Deville wrote:
I have a little server running here in my office,
and logrotate kept running at c. 7am, and using up 100% CPU.
I changed the line in /etc/crontab to run cron.daily scripts
at
On Mon, 2014-02-24 at 13:57 +0100, Tazman Deville wrote:
I have a little server running here in my office,
and logrotate kept running at c. 7am, and using up 100% CPU.
I changed the line in /etc/crontab to run cron.daily scripts
at 4:15am, instead of 7:whateveritwas am.
15 4 * * *
Also, in
16 matches
Mail list logo
