On Tue, 12 Jun 2012 12:21:31 -0500, Dan Lists wrote:
The syntax of his crontab file is correct. Vixie cron does care about
leading spaces, tabs, extra spaces, or leading zeros. Earlier versions
of cron are much pickier about the crontab file. The cron logs show
that it is starting his
On 6/13/2012 6:23 PM, Walter Hurry wrote:
On Tue, 12 Jun 2012 12:21:31 -0500, Dan Lists wrote:
The syntax of his crontab file is correct. Vixie cron does care about
leading spaces, tabs, extra spaces, or leading zeros. Earlier versions
of cron are much pickier about the crontab file. The
On 11/06/2012 23:10, Michael Sierchio wrote:
On Mon, Jun 11, 2012 at 7:04 PM, Walter Hurry walterhu...@gmail.com wrote:
As the subject says, this is probably a newbie question (I am new to
FreeBSD but quite experienced at Linux).
FreeBSD9 on x86_64.
Cron is running:
$ ps -ax|grep cron
On Tue, 12 Jun 2012 00:06:21 -0500, Robert Bonomi
bon...@mail.r-bonomi.com wrote:
Comment: using a leading zero on the numeric fields is a BAD IDEA(tm) --
you
are *strongly* encocuraged to remove them. Yes, that means numbers will
not
be column aligned, but it is a small price to pay to
Mark Felder f...@feld.me writes:
On Tue, 12 Jun 2012 00:06:21 -0500, Robert Bonomi
bon...@mail.r-bonomi.com wrote:
Comment: using a leading zero on the numeric fields is a BAD IDEA(tm) --
you
are *strongly* encocuraged to remove them. Yes, that means numbers
will not
be column aligned,
On Tue, 12 Jun 2012 09:36:37 -0500, Lowell Gilbert
freebsd-questions-lo...@be-well.ilk.org wrote:
I don't have ready access to source at the moment, but I would expect
(like the normal C I/O functions) it will be interpreted as octal.
Suppose we could always ask Paul Vixie :-)
On Tue, 12 Jun 2012 08:29:02 -0500, Mark Felder wrote:
On Tue, 12 Jun 2012 00:06:21 -0500, Robert Bonomi
bon...@mail.r-bonomi.com wrote:
Comment: using a leading zero on the numeric fields is a BAD IDEA(tm) --
you
are *strongly* encocuraged to remove them. Yes, that means numbers
On Tue, Jun 12, 2012 at 12:06 PM, Polytropon free...@edvax.de wrote:
On Tue, 12 Jun 2012 08:29:02 -0500, Mark Felder wrote:
On Tue, 12 Jun 2012 00:06:21 -0500, Robert Bonomi
bon...@mail.r-bonomi.com wrote:
Comment: using a leading zero on the numeric fields is a BAD IDEA(tm) --
you
are
As the subject says, this is probably a newbie question (I am new to
FreeBSD but quite experienced at Linux).
FreeBSD9 on x86_64.
Cron is running:
$ ps -ax|grep cron
1513 ?? Is 0:00.01 /usr/sbin/cron -s
2283 0 S+ 0:00.00 grep cron
$
I have a syntactically valid crontab
On Mon, Jun 11, 2012 at 7:04 PM, Walter Hurry walterhu...@gmail.com wrote:
As the subject says, this is probably a newbie question (I am new to
FreeBSD but quite experienced at Linux).
FreeBSD9 on x86_64.
Cron is running:
$ ps -ax|grep cron
1513 ?? Is 0:00.01 /usr/sbin/cron -s
On Mon, 11 Jun 2012 19:10:21 -0700, Michael Sierchio wrote:
Have you installed bash? It's not in the system base.
What's in your shell scripts?
Thanks for the quick response.
$ pkg_info|grep bash
bash-4.2.28 The GNU Project's Bourne Again SHell
$ which bash
/bin/bash
$
$ less
On Mon, Jun 11, 2012 at 7:25 PM, Walter Hurry walterhu...@gmail.com wrote:
cat /etc/shells
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to
On Mon, 11 Jun 2012 21:21:12 -0500, Adam Vande More wrote:
You really have bash in /bin ? Are your scripts executable? What does
/var/log/cron say?
$ file /bin/bash
/bin/bash: symbolic link to `/usr/local/bin/bash'
$ sudo tail -50 /var/log/cron (result snipped at 02:22:00 for brevity)
Jun
On Mon, 11 Jun 2012 19:36:28 -0700, Michael Sierchio wrote:
cat /etc/shells
$ cat /etc/shells
# $FreeBSD: release/9.0.0/etc/shells 59717 2000-04-27 21:58:46Z ache $
#
# List of acceptable shells for chpass(1).
# Ftpd will not allow users to connect who are not using
# one of these shells.
On 6/11/2012 9:25 PM, Walter Hurry wrote:
On Mon, 11 Jun 2012 19:10:21 -0700, Michael Sierchio wrote:
Have you installed bash? It's not in the system base.
What's in your shell scripts?
Thanks for the quick response.
$ pkg_info|grep bash
bash-4.2.28 The GNU Project's Bourne
Walter Hurry walterhu...@gmail.com wrote:
As the subject says, this is probably a newbie question (I am new to
FreeBSD but quite experienced at Linux).
FreeBSD9 on x86_64.
Cron is running:
$ ps -ax|grep cron
1513 ?? Is 0:00.01 /usr/sbin/cron -s
2283 0 S+ 0:00.00 grep
out if cron is running:
ps aux | grep cron
It should show you /usr/sbin/cron
cron is started with defaults in /etc/defaults/rc.conf as modified by
/etc/rc.conf.
Annelise
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org
It has been a long time since I've had to post for help, so forgive me if
this question is misplaced or stupid.
I have a freebsd server running at home now for years with no problems.
Over the years it has been rebooted a few times either on purpose or do to
things like power failures. It
Check the clock. Often older systems have dead batteries so the clock is
so far out of whack cron jobs don't run.
-Derek
At 08:18 AM 12/28/2006, steve wrote:
It has been a long time since I've had to post for help, so forgive me if
this question is misplaced or stupid.
I have a
Hello,
Make sure to use full path in the cron command file, like so:
/usr/sbin/ntpdate time.server.anywhere
Derek Ragona skrev:
Check the clock. Often older systems have dead batteries so the clock
is so far out of whack cron jobs don't run.
-Derek
At 08:18 AM 12/28/2006, steve
]
On Dec 28, 2006, at 3:33 PM, [EMAIL PROTECTED]
wrote:
Date: Thu, 28 Dec 2006 09:07:23 -0600
From: Derek Ragona [EMAIL PROTECTED]
Subject: Re: cron not running
To: steve [EMAIL PROTECTED],
freebsd-questions@freebsd.org freebsd-questions@freebsd.org
Message-ID:
[EMAIL PROTECTED
I'm having problems getting my freshly update FreeBSD 5.3 system to run
my cron jobs. Logged in as root, I enter the job in root's crontab with
the following command
crontab -e
I enter the job in the following format:
05 10 * * * /root/cronjobs/cvs-sup.sh
Andy Clements wrote:
Hello All,
I'm having problems getting my freshly update FreeBSD 5.3 system to
run my cron jobs. Logged in as root, I enter the job in root's
crontab with the following command
crontab -e
I enter the job in the following format:
05 10 * * *
On Tuesday 14 December 2004 12:20, Andy Clements wrote:
Did I forget some small tid-bit that needs to change for this to work?
Cron requires a newline at the end of the file. I'll bet that your crontab
ends with cvs-sup.sh and not cvs-sup.shNEWLINE.
--
Kirk Strauser
pgpBCUQtL0uV4.pgp
Hello All,
I'm having problems getting my freshly update FreeBSD 5.3 system to run
my cron jobs. Logged in as root, I enter the job in root's crontab with
the following command
crontab -e
I enter the job in the following format:
05 10 * * * /root/cronjobs/cvs-sup.sh
Hey there-
I am running FreeBSD 5.2.1 and I have a cron job running
webalizer. The cron job seems to be running based on the log, but the data
is not being updated in the directory. I do believe that I can say that
the webalizer is configured correctly because if I run the command
Bob Ababurko [EMAIL PROTECTED] wrote:
Hey there-
I am running FreeBSD 5.2.1 and I have a cron job running
webalizer. The cron job seems to be running based on the log, but the data
is not being updated in the directory. I do believe that I can say that
the webalizer is configured
'My' webalizer is in /usr/local/bin/ but then I use FBSD 5.1.
Try with specifying where you have the configuration file
( -c path-to-config-file-and-filename).
Eg. /usr/local/bin/webalizer -c /usr/local/www/conf/webalizer.conf
I use it in a shell script and it works fine.
28 matches
Mail list logo
