| View previous topic :: View next topic |
| Author |
Message |
gregcoit
Tux's lil' helper
Joined: 12 Jun 2002
Posts: 101
|
 Posted: Mon May 31, 2004 12:48 am Post subject: cron questions |
 |
|
To start off with, this is not a "vcron/vixie-cron" question like the ones that invaded the forums during the name change (at least, I don't think so).
When I had vcron, it worked great. No problems. Then they changed the name and I went through the same thing everyone else did to get rid of the "dependancy already satisfied by vcron" error.
No problem.
Except....
Cron no longer runs anything. It itself is running (a ps -ef shows this) and it's printing out stuff to the log files like normal:
| Quote: | May 30 17:00:00 [CRON] (root) CMD (rm -f /var/spool/cron/lastrun/cron.hourly)_
May 30 17:01:00 [CRON] (root) CMD (test -x /usr/sbin/run-crons && /usr/sbin/run-crons )_ |
But it's not actually doing anything.
Then I noticed in this thread (https://forums.gentoo.org/viewtopic.php?t=171499) the following lines of instructions:
| Quote: | > nano -w /etc/cron.hourly/virus-update.cron
#!/bin/bash
/opt/f-prot/check-updates.pl -cron -quiet
> chmod 755 /etc/cron.hourly/virus-update.cron
> crontab -e
# min hour day month weekday command
0 * * * * /etc/cron.hourly/virus-update.cron |
Waitaminute. One needs to place the script in *both* the cron.* dir and in one own's crontab?
I always thought the cron.* dir's were for system cron jobs, but one could always have their own crontab too (but that they would be seperate).
Have I been living a lie all this time? 
FWIW: I re-emerged vixie-cron and made sure all signs of vcron are gone. I'm open to any/all suggestions (unless it involves using windows).
_________________
"Life would be so much easier if we could see the source code" |
|
| Back to top |
|
 |
ecatmur
Advocate
Joined: 20 Oct 2003
Posts: 3595
Location: Edinburgh
|
| Posted: Mon May 31, 2004 2:20 am Post subject: |
|
|
This should be in your system crontab (/etc/crontab):
| Code: | # for vixie cron
# remember to give cron a sighup when updating this file
#
# $Header: /home/cvsroot/gentoo-x86/sys-apps/vixie-cron/files/crontab-3.0.1-r4,v 1.3 2003/12/14 17:19:25 azarah Exp $
#
#
# Global variables
SHELL=/bin/bash
PATH=/sbin:/bin:/usr/sbin:/usr/bin
MAILTO=root
HOME=/
# check scripts in cron.hourly, cron.daily, cron.weekly and cron.monthly
0 * * * * root rm -f /var/spool/cron/lastrun/cron.hourly
1 3 * * * root rm -f /var/spool/cron/lastrun/cron.daily
15 4 * * 6 root rm -f /var/spool/cron/lastrun/cron.weekly
30 5 1 * * root rm -f /var/spool/cron/lastrun/cron.monthly
* * * * * root test -x /usr/sbin/run-crons && /usr/sbin/run-crons
|
_________________
No more cruft
dep: Revdeps that work
Using command-line ACCEPT_KEYWORDS? |
|
| Back to top |
|
|
gregcoit
Tux's lil' helper
Joined: 12 Jun 2002
Posts: 101
|
| Posted: Mon May 31, 2004 2:31 am Post subject: yep.... |
|
|
Sorry, should have mentioned that I do have that....
Any other ideas?
Greg
_________________
"Life would be so much easier if we could see the source code" |
|
| Back to top |
|
|
ecatmur
Advocate
Joined: 20 Oct 2003
Posts: 3595
Location: Edinburgh
|
|
| Back to top |
|
|
gregcoit
Tux's lil' helper
Joined: 12 Jun 2002
Posts: 101
|
| Posted: Mon May 31, 2004 2:36 am Post subject: nope... |
|
|
it does not - nor does it generate any errors.... 
_________________
"Life would be so much easier if we could see the source code" |
|
| Back to top |
|
|
ecatmur
Advocate
Joined: 20 Oct 2003
Posts: 3595
Location: Edinburgh
|
|
| Back to top |
|
|
gregcoit
Tux's lil' helper
Joined: 12 Jun 2002
Posts: 101
|
| Posted: Mon May 31, 2004 5:09 am Post subject: |
|
|
afraid I did that too.
What surprised me is that this seems to be unique to me - but it's happening on both my boxes that I use cron.
very strange.
maybe I will unmerge and then re-emerge both cronbase and vixie-cron.
_________________
"Life would be so much easier if we could see the source code" |
|
| Back to top |
|
|
|
Other Things Gentoo
