Cron auto-generate bug

[Krnák János]

hi

do you add this extra line through an init script?
i had a bug with the method i mentioned, but while looking up other init 
scripts i found a soltion:

(crontab -l 2>&- | grep -v myscriptname.sh
  echo "10 * * * * /path/to/myscript/myscriptname.sh 2&>1 > /dev/null"
) | crontab - 2>&-

this will check your crontab, and only add the line if it not exists, i 
mean, if no other lines matches the myscriptname.sh

bye

Graham Beneke escribió:
> Hi
>
> I have been having problems with various CoovaAP devices locking up 
> and failing to boot after a few months of deployment.
>
> When viewing the syslog i found the following:
>
> user.info : /etc/init.d/S90chilli: 1: cannot create 
> /etc/chilli/main.conf: No space left on device
> user.info : touch: /etc/chilli/local.conf: No space left on device
> kern.crit kernel: mini_fo: create_sto_file: ERROR creating sto file.
> user.info : touch: /etc/chilli/hs.conf: No space left on device
> kern.crit kernel: mini_fo: create_sto_file: ERROR creating sto file.
> user.info : coova-chilli: Error opening configuration file 
> '/etc/chilli/hs.conf'
>
> Further investigation revealed that an extra line that I had added to 
> /etc/crontabs/root had got mangled and duplicated thousands of times 
> but one of the start-up scripts.
>
> This resulted in the flash filling up and the device being unable to 
> start.
>
> How should I be adding cron items to avoid them being mangled?
>
> regards

-- 
This message has been scanned for viruses and
dangerous content by MailScanner, and is
believed to be clean.

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.coova.org/pipermail/chilli/attachments/20080818/9f07ec4b/attachment.htm>