On Thu, Mar 25, 2010 at 01:13:28AM -0300, Tiago Bortoletto Vaz wrote:
> Hi Holger, thanks for reporting. I would like to have your help before 
> changing
> the cronjob code which causes this issue.
> 
> Please see the policy "9.5 Cron jobs":
> 
> "The scripts or crontab entries in these directories should check if all
> necessary programs are installed before they try to execute them. Otherwise,
> problems will arise when a package was removed but not purged since
> configuration files are kept on the system in this situation."
> 
> My cronjob file just checks if /sbin/apticron exists before running it:
> 
> ti...@thinkpad:~/Hacking/apticron$ cat debian/cron.daily
> #!/bin/sh
> 
> test -x /usr/sbin/apticron && /usr/sbin/apticron --cron
> 
> I know I could do it using other methods, but once the current one does what
> the policy requires and does not send any annoying output, then I need to
> imagine a situation where this behavior could affect the system. And I can't
> think in anything for now. So, could you give me an example?

Also note that crontab calls run-parts without "--exit-on-error" parameter.

Regards,

-- 
--------------------------------------------------------------------------------
  .''`.  Tiago Bortoletto Vaz                         GPG  :      1024D/A504FECA
 : :' :  http://tiagovaz.org                          XMPP : tiago at jabber.org
 `. `'   tiago at {tiagovaz,debian}.org               IRC  :       tiago at OFTC
   `-    Debian GNU/Linux - The Universal OS               http://www.debian.org
--------------------------------------------------------------------------------

Attachment: signature.asc
Description: Digital signature

Reply via email to