From: AGottinger@t-online.de (Achim Gottinger)
To: gentoo-dev@gentoo.org
Subject: Re: [gentoo-dev] cron
Date: Tue May 15 04:02:02 2001 [thread overview]
Message-ID: <3B00F796.EC264B7C@gentoo.org> (raw)
In-Reply-To: Pine.LNX.4.21.0105150423550.8845-100000@x86.dyn.cheapnet.net
Bryce Porter wrote:
>
> 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.
>
Yeah, dcron ignores /etc/crontab, you must run crontab /etc/crontab to
get it working.
> 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'".
dcron ignores those variables.
>
> 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.
Hrm, you can try the vcron package if you prefere vixicron. But there is
no init.d script for that cron at the moment.
You can copy dcron to cron and replace /usr/sbin/crond with
/usr/bin/cron and things should work. Make sure you run rc-update del
svc-dcron
before you activate the new cron init script.
>
> 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?
I plan to make all three cron packages usable (fcron,drcon and vcron).
Daniel preferes dcron because it is the simplest one so
it will still be the default.
bye achim~
>
> Has anyone else experienced the same problems?
>
> Thanks for your time.
>
> Bryce Porter
> BP Web Design
> bporter@advancenet.net
> x86@gentoo.org
>
> _______________________________________________
> gentoo-dev mailing list
> gentoo-dev@gentoo.org
> http://www.gentoo.org/mailman/listinfo/gentoo-dev
next prev parent reply other threads:[~2001-05-15 10:01 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-05-15 3:33 [gentoo-dev] cron Bryce Porter
2001-05-15 4:02 ` Achim Gottinger [this message]
-- 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=3B00F796.EC264B7C@gentoo.org \
--to=agottinger@t-online.de \
--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