|
|
Posted by shimmyshack on 06/06/07 00:14
On Jun 5, 9:34 pm, "Jon Slaughter" <Jon_Slaugh...@Hotmail.com> wrote:
> "Toby A Inkster" <usenet200...@tobyinkster.co.uk> wrote in messagenews:unjgj4-h76.ln1@ophelia.g5n.co.uk...
>
>
>
> > Jon Slaughter wrote:
>
> >> I assume this is bash stuff? (I haven't done any unix scripting in a very
> >> long time and very little but I assume the other posts give the script
> >> that
> >> will work here). I just remember there being several types
>
> > Cron doesn't specifically require bash scripting.
>
> > Cron can be used to launch any executable file at a frequency of up to
> > once per minute. (Or as infrequent as once every 28 years[1] if need be,
> > but that seems a bit excessive -- if something needs scheduling that
> > infrequently, you're better off running it manually.)
>
> > These executables could be bash scripts, tcsh scripts, Perl scripts,
> > compiled C code, or raw machine code written in a hex editor if you
> > like -- anything that you could run from the command line can run from
> > cron.
>
> > That said, most people do seem to use either Perl or some form of shell
> > scripting for cron jobs.
>
> Thanks... I'll try to do some more research on it and see what I come up
> with... on what to do. I like the idea of using php but I think it won't be
> fast enough so I'll look into doing it in C++ and then figure out how to run
> it(since I'm on a windows machine I'll have to compile it for linux somehow)
>
> Jon
php offloads some of its work onto c libraries anyway, so unless you
have a specific task in mind that php does not offload, you might not
find too much diff in perf, my $0.02
Navigation:
[Reply to this message]
|