From: Dave Nebinger <dnebinger@joat.com>
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] Problem with vixie-cron
Date: Tue, 07 Mar 2006 12:04:31 -0500 [thread overview]
Message-ID: <440DBD1F.8030804@joat.com> (raw)
In-Reply-To: <fcbf7e4c0603070856m32135147l356d4814dfda0f06@mail.gmail.com>
Thiago Lüttig wrote:
> Hi, i´m trying to automate a proccess with vixie-cron, so I edit the
> /etc/crontab file, and after run crontab /etc/crontab, i look into the
> log (/var/log/crond/current) and the following message apears: [cron]
> (*system*) BAD FILE MODE (/etc/crontab)
> and my task was not executed. What´s wrong ?
First you do not want to put it into /etc/crontab. Edit a file in your
local directory.
Often it is better to "crontab -l > local.crontab" or some such so the
file is populated with your current crontab entries, then edit it to add
your new entry.
Finish that off by "crontab local.crontab" to get the addition loaded.
--
gentoo-user@gentoo.org mailing list
next prev parent reply other threads:[~2006-03-07 17:19 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-03-07 16:56 [gentoo-user] Problem with vixie-cron Thiago Lüttig
2006-03-07 17:00 ` Michael Smith
2006-03-07 17:03 ` Dave Moore
2006-03-07 17:04 ` Dave Nebinger [this message]
2006-03-07 17:10 ` Michael Smith
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=440DBD1F.8030804@joat.com \
--to=dnebinger@joat.com \
--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