Re: [cobalt-users] Planned execution of a script on a RAQ - AT not there ?

[Larry Smith <lesmith@xxxxxxxxx>]

On Monday 10 May 2004 07:27, Francisco Javier Fabra Caro wrote:
> > I guess I am missing something here.  Cron still works on Cobalts just
> > like any other "nix box - you can set jobs to run at any time you desire.
> >  Note the last line of /etc/crontab - which runs swatch every 15 minutes.
> >  Simply build a crontab (or modify it) to do the job (run your perl
> > script) at the time you desire.
> >
> > As for syncing the time, start ntp (/etc/rc.d/init.d/xntpd) which will
> > sync the time with a network time server (there are loads out there) and
> > make sure your box is accurate with the rest of the net.  I run it on all
> > my servers so that I know a report/email dated a certain time is the same
> > "time" for all servers.
>
> But the problem it's that crond doesn't guarantee you to execute the
> process in the exact time. Depending of your needings, you should start
> before the time a process with high-priority to ensure the correct
> execution on all possible cases (load, time..). But depends on the
> neccessity that you have for a real close-time-execution, I think.. The
> cron solution it's the most suitable for most of situations.
>

While I agree - in principle - but if one needs more than (more accurate than) 
per minute accounting then you do _not_ need to be running on a multi-tasking 
machine and definitely not on a Cobalt.  Get something that supports 
"real-time".  I have seen few (very) processes that require greater than per 
minute accuracy.

-- 
Larry Smith
SysAd ECSIS.NET
sysad@xxxxxxxxx