From: Michael Orlitzky <michael@orlitzky.com>
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] crontab questions
Date: Sat, 15 Dec 2012 12:21:38 -0500 [thread overview]
Message-ID: <50CCB1A2.70709@orlitzky.com> (raw)
In-Reply-To: <CAN0CFw1rhyEK1nj_KzKj6_W+fn-RDTrG+k_K+SsT2AiShfXSfw@mail.gmail.com>
On 12/14/2012 09:36 PM, Grant wrote:
>
> I got it working in /etc/crontab. Should I file a bug for
> http://www.gentoo.org/doc/en/cron-guide.xml to mention that vixie-cron
> must be restarted when making changes to /etc/crontab? It says:
>
> "Note that only Vixie-cron schedules jobs in /etc/crontab automatically."
>
You shouldn't have to restart vixie-cron, I think it just scans
/etc/crontab every so often.
> Wouldn't you rather use a one-liner like this?
>
> iptables -L -n | mail -s "mx1 iptables state" -a "From:
> root@mx1.example.com <mailto:root@mx1.example.com>"
> postmaster@example.com <mailto:postmaster@example.com>
>
Even the simple stuff I like to keep in a separate shell script. They're
all under version control so that if one server blows up, all I have to
do is checkout the git repo and hit `make` on another box and everything
will more-or-less work once I emerge @world.
I could avoid using a temp file that way, but it ain't broke so I'm not
going to fix it.
prev parent reply other threads:[~2012-12-15 17:23 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-12-11 21:15 [gentoo-user] crontab questions Grant
2012-12-12 3:14 ` Michael Orlitzky
2012-12-12 22:09 ` Grant
2012-12-13 1:01 ` Michael Orlitzky
2012-12-15 2:36 ` Grant
2012-12-15 17:21 ` Michael Orlitzky [this message]
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=50CCB1A2.70709@orlitzky.com \
--to=michael@orlitzky.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