From: Bryce Porter <bporter@advancenet.net>
To: gentoo-dev@gentoo.org
Subject: [gentoo-dev] cron
Date: Tue May 15 03:33:01 2001 [thread overview]
Message-ID: <Pine.LNX.4.21.0105150423550.8845-100000@x86.dyn.cheapnet.net> (raw)
Hi everyone...
I've been having serious problems with cron. It seems that the default
/etc/crontab is not getting used by crontab. After an initial install, I
ran crontab -e and it was blank, but /etc/crontab had many things in it.
After putting things into the crontab with crontab -e it works, but I have
it setup to run something once every 15 minutes and it runs things once
every 5 minutes instead (according to the docs and #linpeople on
openprojects.net, the contents are correct).
Also, the standard ways of changing the editor invoked with crontab -e do
not work. I tried "export EDITOR=joe" and "export VISUAL=joe" but crontab
-e still failed to run joe instead of vi. I then resorted to moving
/usr/bin/vi to /usr/bin/vi-old and ln -s /usr/bin/joe /usr/bin/vi and then
it STILL tries to invoke vi, but it fails saying "Couldn't open
'/usr/lib/virc'".
Alot of people suggested I switch to vixiecron instead of dcron, because
of thier previous experiences with dcron. I was told vixie
wouldn't have these problems.
I was wondering if there was a way we could switch the default
implementation of cron to vixie so that these problems could be fixed?
Has anyone else experienced the same problems?
Thanks for your time.
Bryce Porter
BP Web Design
bporter@advancenet.net
x86@gentoo.org
next reply other threads:[~2001-05-15 9:32 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-05-15 3:33 Bryce Porter [this message]
2001-05-15 4:02 ` [gentoo-dev] cron Achim Gottinger
-- strict thread matches above, loose matches on Subject: below --
2002-03-13 20:14 [gentoo-dev] Cron Thilo Bangert
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=Pine.LNX.4.21.0105150423550.8845-100000@x86.dyn.cheapnet.net \
--to=bporter@advancenet.net \
--cc=gentoo-dev@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