(solved) chronjob update flashplugin-nonfree format error

Started by michaa7, 2013/07/09, 12:44:42

Previous topic - Next topic

michaa7

I get warning emails about absolut's chronjob.

Quote/etc/cron.daily/flash:
run-parts: failed to exec /etc/cron.daily/flash: Exec format error
run-parts: /etc/cron.daily/flash exited with return code 1

???
Ok, you can't code, but you still might be able to write a bug report for Debian's sake

michaa7

Solution:

Add shebang, content must look like:

Quote#!/bin/sh

test -x /usr/sbin/update-flashplugin-nonfree && /usr/sbin/update-flashplugin-nonfree --install --quiet
and must be executable.
Ok, you can't code, but you still might be able to write a bug report for Debian's sake

absolut

oh, damn!

thanks for the update. I somehow completely missed this one...

michaa7

As a follow up:

Is this the expected result if your flashplugin-nonfree *is* up to date:

Anacron job 'cron.daily' on <mycomp>
Quote/etc/cron.daily/flash:
already exists: /usr/bin/flash-player-properties
already exists: /usr/share/applications/flash-player-properties.desktop
already exists: /usr/share/icons/hicolor/16x16/apps/flash-player-properties.png
already exists: /usr/share/icons/hicolor/22x22/apps/flash-player-properties.png
already exists: /usr/share/icons/hicolor/24x24/apps/flash-player-properties.png
already exists: /usr/share/icons/hicolor/32x32/apps/flash-player-properties.png
already exists: /usr/share/icons/hicolor/48x48/apps/flash-player-properties.png
already exists: /usr/share/pixmaps/flash-player-properties.png
Note: This is an email notifacation which you only recive if you configured local root mail to be delivered to a specific user. Otherwise only root sees this messages.

Do you have any clue how to enhance your script/cronjob to only sent messages in case of failure
Ok, you can't code, but you still might be able to write a bug report for Debian's sake

absolut

uhm. actually, from my point of view, this is a "bug" in /usr/sbin/update-flashplugin-nonfree, because it ignores the --quiet parameter in this particular case (see line 331)

if you change the line to [ "$verbose" != "yes" ] || echo "already exists: $targetfile", it will behave quietly, as it should

maybe this should be reported upstream...