[Bug 13] fcron-1.1.1

jbauman at adsl-63-193-249-142.dsl.snfc21.pacbell.net jbauman at adsl-63-193-249-142.dsl.snfc21.pacbell.net
Thu Aug 30 23:22:04 PDT 2001

On Wed, Aug 29, 2001 at 02:55:51AM +0100, Mark Hymers wrote:
> > Mark, if you could tell us the reasons for considering the switch, people 
> > may be able to provide information that would address those concerns.
> OK.. I'll own up ;-)
> The reasons I was considering making the switch were personal:
> 1) I can't get my head around fcrons syntax (though I'll investigate
> the compat mode)
> 2) I use dcron on my home system and it seems reliable
> Not good reasons in the slightest...  If fcron really is better we'll go
> with it and I'll shut up.  As I say, I'll investigate fcron again and
> look at the syntax when I'm more awake than I am now.
You may have missed the compatibility mode syntax because (I belive) it's new.
The changelog for the 1.1.1 version mentions it, and that was released July

I actually find fcron's native syntax to be clearer in many cases: 
@ 1h echo "executing every hour of uptime"
20 * * * * echo "did I get enough *'s in there?"

They're not precisely the same, but probably close enough for 99% of cases.
The second example will work with fcron, too.

I would suggest starting with the examples section in fcrontab(5) man page, 
and looking up specifics from there. 
Jeff Bauman
jbauman at adsl-63-193-249-142.dsl.snfc21.pacbell.net

"...the standard Windows remote administration tool -- your car."
	-- Hatch, Lee & Kurtz from "Hacking Linux Exposed"

More information about the blfs-book mailing list