On Wednesday 01 Oct 2003 3:04 pm, Derek Jennings wrote:
On Wednesday 01 Oct 2003 1:13 am, L.V.Gandhi wrote:
I get following error.
Sep 30 05:29:02 lvghomepc anacron[1507]: Job `cron.daily' started
Sep 30 05:29:02 lvghomepc anacron[1770]: Updated timestamp for job
`cron.daily' to
I don't know about the cron error, but regarding the mail output, man
cron says:
When executing commands, any output is mailed to the owner of the
crontab (or to the user named in the MAILTO environment variable in the
crontab, if such exists).
Naturally, there must be a mailer deamon running
On Wednesday 01 Oct 2003 1:13 am, L.V.Gandhi wrote:
I get following error.
Sep 30 05:29:02 lvghomepc anacron[1507]: Job `cron.daily' started
Sep 30 05:29:02 lvghomepc anacron[1770]: Updated timestamp for job
`cron.daily' to 2003-09-30
Sep 30 05:29:51 lvghomepc anacron[1507]: Job `cron.daily'
thankyou very much,
bascule
On Friday 01 December 2000 4:38 pm, you wrote:
On Fri, 1 Dec 2000, bascule wrote:
I figured that one out.
In /etc/cron.daily there's a file called htdig-dbgen.
Just chmod -x that and it's over with the messages.
Paul
hi,
i am getting the message below
On Fri, 1 Dec 2000, bascule wrote:
I figured that one out.
In /etc/cron.daily there's a file called htdig-dbgen.
Just chmod -x that and it's over with the messages.
Paul
hi,
i am getting the message below regularly, i would be grateful if someone
could tell me if it is serious and how i might
If you look at slocate.cron in a text editor you will notice that the
last '}' is on a line by itself. Go to the last '}' and do a backspace
to bring it back up to its proper line.
If that doesn't work you'll have to open slocate.cron with the hex
editor. If you are using the hex editor,
On Sun, 5 Sep 1999, Ken Wilson wrote:
If you look at slocate.cron in a text editor you will notice that the
last '}' is on a line by itself. Go to the last '}' and do a backspace
to bring it back up to its proper line.
If that doesn't work you'll have to open slocate.cron with the hex
