Mailinglist Archive: opensuse (3419 mails)

[Magnus Boman <captain.magnus@xxxxxxxxx>]

On Tue, 2007-04-10 at 09:54 +0100, G.T.Smith wrote:
> John Andersen wrote:
> > On Monday 09 April 2007, riccardo35@xxxxxxxxx wrote:
> >   
> >> On Tue 10 Apr 2007 06:15, Magnus Boman wrote:
> >>     
> >>> There are plenty of ways to do this...
> >>>       
> >>  you can make it as an executable file, called "rootcron" in directory:
> >>
> >>        /var/spool/cron/tabs
> >>
> >>
> >> then, execute :
> >>
> >>        /var/spool/cron/tabs/crontab rootcron
> >>
> >>
> >>  . . . and your executable file rootcron will be installed as your new
> >> crontab named "root" in the file :
> >>
> >>     /var/spool/cron/tabs/root
> >>
> >>
> >>  [ I believe  :)             ]
> >>     
> >
> > There is no reason to make it executable. 
> > Any text file will do.  It can be located anywhere.
> >   
> 
> Surely some mistake here, the root cron file in the example would have
> to executed to so needs execute rights :-) ...  To be honest reply is a
> bit ambiguous..., but the original suggestion is wildly off the mark ...

Ehh..? What are you considering "original suggestion" here?

> 
> You do have a choice.... the //etc/cron.hourly, /etc/cron.daily and
> /etc/cron.monthly directory contain system wide root jobs that are
> executed at the indicated times. You can ensure a script is run a given
> interval merely by placing the executable script in the relevant 
> directory.... The more complex option is to create a crontab table file
> for a user account and activating it with the crontab command....
> > I suggest you read 
> >     man crontab
> >
> >
> >   
> agreed..
> 
> 

Cheers,
Magnus

-- 
To unsubscribe, e-mail: opensuse+unsubscribe@xxxxxxxxxxxx
For additional commands, e-mail: opensuse+help@xxxxxxxxxxxx