Debian Automated Code Analysis

checkbashisms analysis of fetch-crl_3.0.5-1.dsc

possible bashism in ./fetch-crl-boot.init line 27 ($"foo" should be eval_gettext "foo"):
	action $"Running fetch-crl on boot: " /usr/sbin/fetch-crl -q
possible bashism in ./fetch-crl-boot.init line 58 ($"foo" should be eval_gettext "foo"):
           echo -n $"fetch-crl-boot lockfile present" && success
possible bashism in ./fetch-crl-boot.init line 61 ($"foo" should be eval_gettext "foo"):
           echo -n $"fetch-crl-boot lockfile missing" && failure
possible bashism in ./fetch-crl-boot.init line 67 ($"foo" should be eval_gettext "foo"):
	echo $"Usage: $0 {start|stop|status|restart|reload|force-reload|condrestart}"
possible bashism in ./fetch-crl-cron.init line 20 ($"foo" should be eval_gettext "foo"):
	action $"Enabling periodic fetch-crl: " touch "$lockfile" 
possible bashism in ./fetch-crl-cron.init line 25 ($"foo" should be eval_gettext "foo"):
	action $"Disabling periodic fetch-crl: " rm -f "$lockfile" 
possible bashism in ./fetch-crl-cron.init line 50 ($"foo" should be eval_gettext "foo"):
		echo $"Periodic fetch-crl is enabled."
possible bashism in ./fetch-crl-cron.init line 53 ($"foo" should be eval_gettext "foo"):
		echo $"Periodic fetch-crl is disabled."
possible bashism in ./fetch-crl-cron.init line 58 ($"foo" should be eval_gettext "foo"):
	echo $"Usage: $0 {start|stop|status|restart|reload|force-reload|condrestart}"

This report was generated on Wed, 16 Feb 2011 06:38:03 +0000, based on results by checkbashisms 2.10.65git5