Re: cron.daily logrotate beating up my server

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

Re: cron.daily logrotate beating up my server

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 ;) > > Th

Re: cron.daily logrotate beating up my server

2014-02-26 12:43 GMT+01:00 Tony Baldwin : > 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

Re: cron.daily logrotate beating up my server

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 nee

Re: cron.daily logrotate beating up my server

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

Re: cron.daily logrotate beating up my server

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: http://lists.alio

Re: cron.daily logrotate beating up my server

On Tue, Feb 25, 2014 at 02:31:43PM +0100, Raffaele Morelli wrote: > 2014-02-25 13:53 GMT+01:00 Tazman Deville >: > > 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 �comma

Re: cron.daily logrotate beating up my server

2014-02-25 13:53 GMT+01:00 Tazman Deville : > > > 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* * * root

Re: cron.daily logrotate beating up my server

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

Re: cron.daily logrotate beating up my server

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

Re: cron.daily logrotate beating up my server

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.d

Re: cron.daily logrotate beating up my server

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 10

Re: cron.daily logrotate beating up my server

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,

Re: cron.daily logrotate beating up my server

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

Re: cron.daily logrotate beating up my server

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 * * *

Re: cron.daily error

On Wed, 25 Jul 2012 15:06:11 -0600, Bob Proulx wrote: >Jeff Grossman wrote: >> I just did a "grep source *" from the /etc/cron.daily directory to >> figure out what file is causing me the problems. But, it came back >> empty. How would I figure out where that source file is to fix it? >> The e-m

Re: cron.daily error

On Wed, 25 Jul 2012 13:50:32 -0700, Jeff Grossman wrote: > On Wed, 25 Jul 2012 14:25:40 +0100, Darac Marjal wrote: (...) >>I imagine that your system shell has been changed to dash (run "ls -l >>/bin/sh" to check). Dash is somewhat stricter in its implementation of >>POSIX than bash (it's main f

Re: cron.daily error

Jeff Grossman wrote: > I just did a "grep source *" from the /etc/cron.daily directory to > figure out what file is causing me the problems. But, it came back > empty. How would I figure out where that source file is to fix it? > The e-mail is my daily cron.daily cron job e-mail that is giving me

Re: cron.daily error

On Wed, 25 Jul 2012 14:25:40 +0100, Darac Marjal wrote: >On Wed, Jul 25, 2012 at 06:13:31AM -0700, Jeff Grossman wrote: >> Since I have upgraded to Squeeze, I get and e-mail with the following >> line in it every morning. Would somebody be able to point me in the >> right direction to figure out

Re: cron.daily error

On Wed, Jul 25, 2012 at 06:13:31AM -0700, Jeff Grossman wrote: > Since I have upgraded to Squeeze, I get and e-mail with the following > line in it every morning. Would somebody be able to point me in the > right direction to figure out what file in cron.daily is giving me > this error? > > > -s

Re: cron.daily error for apt

On Mon, 5 Dec 2011, John Hasler wrote: From debian-policy: hi John, Thank you for this very useful reply. I think that it is a good practice, when giving an information, to give also the way to get it, (it is sometimes enough to give the link to the doc, when available) I install

Re: cron.daily error for apt

>From debian-policy: E.1 Automatic handling of configuration files by dpkg A package may contain a control information file called conffiles. This file should be a list of filenames of c

Re: cron.daily error for apt

On Lu, 05 dec 11, 21:59:50, Pierre Frenkiel wrote: > On Mon, 5 Dec 2011, Andrei Popescu wrote: > > >You must be confusing this with the regular behavior. > >I can't confuse, as I am unable to guess, from the man, what is >the "regular behaviour", i.e. the default one. >Details are giv

Re: cron.daily error for apt

On Mon, 5 Dec 2011, Andrei Popescu wrote: You must be confusing this with the regular behavior. I can't confuse, as I am unable to guess, from the man, what is the "regular behaviour", i.e. the default one. Details are given for all --force-things, but I found nothing on what happe

Re: cron.daily error for apt

On Lu, 05 dec 11, 12:14:06, Pierre Frenkiel wrote: > To replace also the modified files, I added in apt.conf > "--force-confask"; > I think there was a time where this was the default with apt-get You must be confusing this with the regular behavior. From 'man dpkg' (emphasis

Re: cron.daily error for apt

Pierre Frenkiel wrote: > I understand this behaviour for a removed conffile. but not for a > modified one: I imagine that aptitude doesn't know whether this > conffile comes from a previous version or not. The package management system knows what version was installed previously and the checksums

Re: cron.daily error for apt

On Mon, 5 Dec 2011, Bob Proulx wrote: You said you removed the file. You didn't say you modified it. Sorry, I forgot to say it. I did both tests. Actually, I removed the file after seeing that it was not replaced. Of course asking is still the default for apt-get! But you said you we

Re: cron.daily error for apt

Pierre Frenkiel wrote: > Bob Proulx wrote: >Actually, the increase is impressive >I changed to one of the listed mirrors. Oh good. > >Right. You removed it. It is a conffile. Therefore the system > >respects your changes to that file. Including removing it. The > >system views removi

Re: cron.daily error for apt

On Sun, 4 Dec 2011, Bob Proulx wrote: Better to use a mirror. Take a look at the amount of bandwidth used by the main site. Wow! http://www.debian-multimedia.org/statistics.php hi Bob, Actually, the increase is impressive I changed to one of the listed mirrors. Right. You remov

Re: cron.daily error for apt

Pierre Frenkiel wrote: > Bob Proulx wrote: > >I do not see such a line in Squeeze or Sid. What version of apt do > >you have installed? > > it's difficult for me to understand this mess; > I am on Squeeze. apt version is > 0.8.10.3+squeeze1 That looks normal. >deb http://ftp.fr.deb

Re: cron.daily error for apt

On Sat, 3 Dec 2011, Bob Proulx wrote: I do not see such a line in Squeeze or Sid. What version of apt do you have installed? hi Bob, it's difficult for me to understand this mess; I am on Squeeze. apt version is 0.8.10.3+squeeze1 here is my source.list ===

Re: cron.daily error for apt

Pierre Frenkiel wrote: > Looking in the log for cron.daily, I discovered the following problem: > > /etc/cron.daily/apt contains a line: > apt-key net-update I do not see such a line in Squeeze or Sid. What version of apt do you have installed? $ dpkg --status apt | awk '/Version:/{pr

Re: cron.daily/man-db problems

On Tue, May 16, 2006 at 12:00:15 +0300, David Baron wrote: > On Tuesday 16 May 2006 11:48, Florian Kulzer wrote: > > On Tue, May 16, 2006 at 10:22:39 +0300, David Baron wrote: > > > Get a whole series of messages like: > > > mandb: warning: /usr/share/man/man1/xtrapinfo.1x.gz: bad symlink or ROFF >

Re: cron.daily/man-db problems

On Tuesday 16 May 2006 11:48, Florian Kulzer wrote: > On Tue, May 16, 2006 at 10:22:39 +0300, David Baron wrote: > > Get a whole series of messages like: > > mandb: warning: /usr/share/man/man1/xtrapinfo.1x.gz: bad symlink or ROFF > > `.so' request > > mandb: can't open /usr/share/man/man1x/xtrap.1

Re: cron.daily/man-db problems

On Tue, May 16, 2006 at 10:22:39 +0300, David Baron wrote: > Get a whole series of messages like: > mandb: warning: /usr/share/man/man1/xtrapinfo.1x.gz: bad symlink or ROFF > `.so' > request > mandb: can't open /usr/share/man/man1x/xtrap.1x: No such file or directory > > I tried recreating the d

Re: cron.daily dwww error

On Tue, Oct 11, 2005 at 10:52:45AM +0800, Xiaoyang Gu wrote: > hi, Hi, > I am using debian sid. There is a problem about dwww. > After running /etc/cron.daily/dwww, i get a mail from Anacron as > followed: > > /etc/cron.daily/dwww: > configuration error - unknown item 'QUOTAS_ENAB' (notify adminis

Re: cron.daily, howto control mailed reports

On Fri, Dec 24, 2004 at 02:22:10AM +, Joao Clemente wrote: > Why do I receive daily reports (in my mail system) from this particular > script being runned, but not from other also existant in /etc/cron.daily? If any cron script outputs anything on stdout or stderr, the output is emailed to yo

Re: cron.daily, howto control mailed reports

Benjamin A'Lee wrote: On Fri, Dec 24, 2004 at 02:22:10AM + or thereabouts, Joao Clemente wrote: Why do I receive daily reports (in my mail system) from this particular script being runned, but not from other also existant in /etc/cron.daily? If you want it to run silently, you can put MAILTO=

Re: cron.daily, howto control mailed reports

Sorry, ignore mine. I completely misread the question :\ Robert Vangel wrote: set the MAILTO variable in the script eg #!/bin/bash MAILTO="[EMAIL PROTECTED]" /etc/init.d/ntpdate restart afaik, that would work. Joao Clemente wrote: Hi people. In a server I setup recently I tougth of keeping the cloc

Re: cron.daily, howto control mailed reports

On Fri, Dec 24, 2004 at 02:22:10AM + or thereabouts, Joao Clemente wrote: > Why do I receive daily reports (in my mail system) from this particular > script being runned, but not from other also existant in /etc/cron.daily? > If you want it to run silently, you can put MAILTO="" in /etc/cront

Re: cron.daily, howto control mailed reports

set the MAILTO variable in the script eg #!/bin/bash MAILTO="[EMAIL PROTECTED]" /etc/init.d/ntpdate restart afaik, that would work. Joao Clemente wrote: Hi people. In a server I setup recently I tougth of keeping the clock sinc'ed by running ntpdate daily. I wrote a script calling /etc/init.d/ntpd

Re: cron.daily: order of script execution

On Wed, 7 Apr 2004 05:39:29 +0200 Jochen Kaechelin <[EMAIL PROTECTED]> wrote: > is there a way to decide in which order the scripts in cron.daily > will run? > > i need to run a rsync script before awstats starts analysing > the rsynced files. Add numbers to the beginning, or just simply rename

Re: cron.daily and updatedb

On Thu, Dec 19, 2002 at 09:55:54PM +0100, Dominique Deleris wrote: > I have the following problem: > > I would like to have the locate db updated only once a week, and > not daily as per default settings. I have therefore done the > following: > > - dpkg-diverted /etc/cron.daily/find to /etc/cron

Re: cron.daily and updatedb

Oliver> Do you have an entry for updatedb in /etc/init.d? No. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

Re: cron.daily and updatedb

On Thu, 19 Dec 2002, Dominique Deleris wrote: > Hello, > > I have the following problem: > > I would like to have the locate db updated only once a week, and > not daily as per default settings. I have therefore done the > following: > > - dpkg-diverted /etc/cron.daily/find to /etc/cron.weekly/

Re: cron.daily problem

> > I observed on one of our Debian 2.2 machines that daily cron still > > didn't finish after 5+ hours: > > > > # ps aux > > nobody 29273 0.0 0.4 1104 532 ?D06:25 0:01 find / ( > > -fstype NFS -o -fstype nfs -o -fstype afs -o -fstype > > -fstype NFS --> network file system >

Re: cron.daily problem

On Thu, Oct 12, 2000 at 01:17:36PM +0200, Igor Mozetic wrote: > > I observed on one of our Debian 2.2 machines that daily cron still > didn't finish after 5+ hours: > > # ps aux > nobody 29273 0.0 0.4 1104 532 ?D06:25 0:01 find / ( > -fstype NFS -o -fstype nfs -o -fstype afs

Re: cron.daily and slrnpull

On Thu, Sep 14, 2000 at 07:43:15AM +0100, Anthony Campbell wrote: > I configured slrnpull to run only on demand, but cron.daily keeps trying > to run it every morning. As I am only connected to my ISP intermittently > this is wrong. > > How do I change this (apart from deleting the entry in cron.

Re: cron.daily

On Wed, Apr 26, 2000 at 09:30:10AM +1200, [EMAIL PROTECTED] wrote: > Hi > > if i put in my own script into the /etc/cron.daily directory does that > mean that the script will run on a daily basis? In theory, yes, if the script is readable and executable by root. You can test this by executin

Re: cron.daily isn't

Quoth Brad, > Have you made sure the name fits the requirements of run-parts? man > run-parts for the info. In particular, dots in the filename aren't > allowed. You can test if run-parts will run it with "run-parts --test > /etc/cron.daily" Many thanks to Brad, John, and Jonathon, who all sugges

Re: cron.daily isn't

On Thu, Mar 02, 2000 at 10:25:42PM +1100, Damon Muller wrote > Quoth kmself@ix.netcom.com, > > 'at' is a very useful one-time scheduler. I use it frequently as an > > alternative to backgrounding stuff, say: > > When my clock-radio broke recently, I started using at as an alarm > clock, setting

Re: cron.daily isn't

On Thu, Mar 02, 2000 at 10:25:42PM +1100, Damon Muller wrote: > > I also have a problem on a slink system with a (at least one) cron.daily > job not running. It's a logcheck script, and runs fine when strated from > a shell prompt. There is no evidence anywhere what is going on - nothing > in the

Re: cron.daily isn't

Quoth kmself@ix.netcom.com, > 'at' is a very useful one-time scheduler. I use it frequently as an > alternative to backgrounding stuff, say: When my clock-radio broke recently, I started using at as an alarm clock, setting it to play MP3s for me in the morning to wake me up (my schedule isn't re

Re: cron.daily isn't

On Tue, Feb 29, 2000 at 05:30:07PM -0500, Ben Collins wrote: > On Tue, Feb 29, 2000 at 02:32:41PM -0800, Ernest Johanson wrote: > > I had a similar experience recently on the alpha platform. If I added > > something to the crontab file, it didn't run. I had to stop and start the > > cron daemon to

Re: cron.daily isn't

Ben Collins wrote: > Correct. "at" is an addition to cron, that makes sure that cron jobs get > run regardless of whether the machine was off during the time it was > supposed to excute the given job. If your box is up 24/7, all you need is > cron. Er, I think you meant "anacron", not "at". At doe

Re: cron.daily isn't

On Tue, 29 Feb 2000, Ben Collins wrote: > Correct. "at" is an addition to cron, that makes sure that cron jobs > get run regardless of whether the machine was off during the time it > was supposed to excute the given job. If your box is up 24/7, all you > need is cron. You're overlooking at's abi

Re: cron.daily isn't

On Tue, Feb 29, 2000 at 03:53:14PM -0800, aphro wrote: > On 29 Feb 2000, Michael A. Miller wrote: > > mmille >> "Ben" == Ben Collins <[EMAIL PROTECTED]> writes: > mmille > > mmille >> If your system is up 24/7, I suggest removing at. It is > mmille >> only meant for machines that are u

Re: cron.daily isn't

On 29 Feb 2000, Michael A. Miller wrote: mmille >> "Ben" == Ben Collins <[EMAIL PROTECTED]> writes: mmille > mmille >> If your system is up 24/7, I suggest removing at. It is mmille >> only meant for machines that are up "sometimes, like dual mmille >> boot setups, desktops that ge

Re: cron.daily isn't

> "Ben" == Ben Collins <[EMAIL PROTECTED]> writes: > If your system is up 24/7, I suggest removing at. It is > only meant for machines that are up "sometimes, like dual > boot setups, desktops that get shutdown at night, etc... For machines that are not up 24/7, what replaces at?

Re: cron.daily isn't

On Tue, Feb 29, 2000 at 02:32:41PM -0800, Ernest Johanson wrote: > I had a similar experience recently on the alpha platform. If I added > something to the crontab file, it didn't run. I had to stop and start the > cron daemon to get the new entry to run. Reloading didn't do it. This is > on frozen

Re: cron.daily isn't

I had a similar experience recently on the alpha platform. If I added something to the crontab file, it didn't run. I had to stop and start the cron daemon to get the new entry to run. Reloading didn't do it. This is on frozen. Ernest Johanson Web Systems Administrator Fuller Theological Seminary

Answer: re: cron.daily looks for emacs and movemail:not registered

Someone asked about an entry which appears in his logs, informing him that emacs and movemail are not registered. I found the fix to this problem, and I don't know how I missed it before. Just remove the lines pertaining to movemail and emacs from your /etc/suid.conf -- Andrew -

Re: cron.daily : when does it run?

On Wed, 25 Jun 1997, Peter S Galbraith wrote: > And how can we control it? Looked at man pages, but coudn't find it. > (And I'm used to Slackware with only /var/spool/cron/crontabs/ stuff) /etc/crontab http://www.sound.net/~wpmills/ - : W. Paul Mills

Re: cron.daily : when does it run?

On Wed, 25 Jun 1997, Peter S Galbraith wrote: : And how can we control it? Looked at man pages, but coudn't find it. : (And I'm used to Slackware with only /var/spool/cron/crontabs/ stuff) Checkout /etc/crontab. -- // Remco van de Meent // email: [EMAIL PROTECTED] // www: http://oloo

Re: cron.daily et al.

On Mon, 20 Jan 1997, Seak, Teng-Fong wrote: > Paul Seelig wrote: > > On Fri, 17 Jan 1997, Jean Pierre LeJacq wrote: > > > > How about a (cron) job, that executed every time the > > > > machine gets booted and that checks when the cron jobs > > > > were executed for the last time. If these for were

Re: cron.daily et al.

> I heard of a program called anacron to solve just this problem, but I > don't think it's available as a Debian package, yet. Maybe someone here > knows where to get it? Otherwise, you could try comp.unix.admin or > gopher. > That package is in project/experimental/anacron_1.0.1-3_all.deb I

Re: cron.daily et al.

On Mon, 20 Jan 1997 09:31:09 +0100 "Seak, Teng-Fong" ([EMAIL PROTECTED]) wrote: > Paul Seelig wrote: > > > > On Fri, 17 Jan 1997, Jean Pierre LeJacq wrote: > > > > > > How about a (cron) job, that executed every time the > > > > machine gets booted and that checks when the cron jobs > > > > we

Re: cron.daily et al.

Paul Seelig wrote: > > On Fri, 17 Jan 1997, Jean Pierre LeJacq wrote: > > > > How about a (cron) job, that executed every time the > > > machine gets booted and that checks when the cron jobs > > > were executed for the last time. If these for were not > > > executed for say two days (weeks, mont

Re: cron.daily et al.

> > How about a (cron) job, that executed every time the > > machine gets booted and that checks when the cron jobs > > were executed for the last time. If these for were not > > executed for say two days (weeks, months) then they > > get executed regardless the actual hour, day, week of month. >

Re: cron.daily et al.

On Jan 17, Jan Camenisch wrote [cron suggestion for machines that don't run all day] > How about a (cron) job, that executed every time the > machine gets booted and that checks when the cron jobs > were executed for the last time. If these for were not > executed for say two days (weeks, months)

RE: cron.daily et al.

Jan Camenisch wrote: >There might be a problem with the execution >of the cron.daily, cron.weekly, and cron.monthly : >An machines that don't run all day, these cron jobs get >rarely executed. >For instance, I usually use my maschine only in the >evenings at home (i.e. later than 6 pm). But a

Re: cron.daily et al.

On Fri, 17 Jan 1997, Jan Camenisch wrote: > Hi, > > There might be a problem with the execution > of the cron.daily, cron.weekly, and cron.monthly : > An machines that don't run all day, these cron jobs get > rarely executed. > For instance, I usually use my maschine only in the > evenings a