From: rich@example.invalid   
      
   Marco Moock  wrote:   
   > Hello!   
   >   
   > I want to run a cronjob.   
   >   
   > It currently (for testing purposes) looks like that:   
   >   
   > m@tr:~$ sudo cat /etc/cron.d/big-8   
   > SHELL=/bin/sh   
   > PATH=/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin   
   > *  *    *       *       *   root   echo "hallo"   
   > m@tr:~$   
   >   
   > m@tr:~$ sudo run-parts /etc/cron.d   
   > /etc/cron.d/big-8: line 3: check_big8.sh: command not found   
   > /etc/cron.d/big-8 failed.   
   > m@tr:~$   
   >   
   > It included a call for this script in the past, but I removed that. It   
   > still tries to run it. What causes that?   
      
   In addition to what Henrik said, the most common reason for "old   
   crontab entry continues to be run" is that you directly edited the   
   crontab file instead of using 'crontab' to launch the edit.   
      
   In addition to 'locking' the file against plural edits, the 'crontab'   
   command also signals the running cron daemon to reload the edited file   
   when you save the changes and exit the editor.   
      
   If you just directly edit the file on disk, you have changed the file   
   on disk, but the running deamon will still have in memory a copy of the   
   old file before you edited it.   
      
   --- SoupGate-DOS v1.05   
    * Origin: you cannot sedate... all the things you hate (1:229/2)