[patch] Use appropriate priority when logging through logger

use-appropriate-priority.patch (text/plain), 983 bytes, created by Thomas Deutschmann (RETIRED) on 2015-07-22 09:18:01 UTC

diff -rupN old/sys-process/cronbase/files/run-crons-0.3.5 new/sys-process/cronbase/files/run-crons-0.3.5
--- old/sys-process/cronbase/files/run-crons-0.3.5	2015-07-22 09:12:15.000000000 +0200
+++ new/sys-process/cronbase/files/run-crons-0.3.5	2015-07-22 11:02:03.156344540 +0200
@@ -33,9 +33,12 @@
 LOCKDIR=/var/spool/cron/lastrun
 LOCKFILE=${LOCKDIR}/lock
 
-# Usage: log <args to logger>
+# Usage: log <priority> <msg>
 log() {
-	logger -i -p cron.info -t run-crons "$@"
+	local priority=$1
+	shift
+
+	logger -i -p ${priority} -t run-crons "$@"
 }
 
 mkdir -p ${LOCKDIR}
@@ -108,11 +111,11 @@ for BASE in hourly daily weekly monthly
 				.*|*~) continue ;;
 				esac
 
-				log "($(whoami)) CMD (${SCRIPT})"
+				log "cron.info" "($(whoami)) CMD (${SCRIPT})"
 				$SCRIPT
 				ret=$?
 				if [ ${ret} -ne 0 ] ; then
-					log "CMD (${SCRIPT}) failed with exit status ${ret}"
+					log "cron.err" "CMD (${SCRIPT}) failed with exit status ${ret}"
 					EXIT_STATUS=1
 				fi
 			fi