Currently with the replacement variables/templates this is trickier, but we can do this on installed base.
When the replacement stuff is gone, we should run 'perl -c -w' on all perl scripts to verify them for errors/issues.
in the source dir identify perl scripts:
$ echo ls *pl | sed 's/.pl//g'
$ LIST=${paste}
$ for i in ${LIST}; do perl -c -w $i; done
approve syntax OK
chpw syntax OK
dbck-password syntax OK
findmember syntax OK
fsck-mlkeys syntax OK
fsck-pgpkeys syntax OK
gpgtest syntax OK
mail-handler syntax OK
new-member syntax OK
notify-idle syntax OK
notify-stuck syntax OK
notify-unvetted syntax OK
report-unvetted syntax OK
state-mon syntax OK
Currently with the replacement variables/templates this is trickier, but we can do this on installed base.
When the replacement stuff is gone, we should run 'perl -c -w' on all perl scripts to verify them for errors/issues.
in the source dir identify perl scripts: $ echo
ls *pl | sed 's/.pl//g'$ LIST=${paste} $ for i in ${LIST}; do perl -c -w $i; done approve syntax OK chpw syntax OK dbck-password syntax OK findmember syntax OK fsck-mlkeys syntax OK fsck-pgpkeys syntax OK gpgtest syntax OK mail-handler syntax OK new-member syntax OK notify-idle syntax OK notify-stuck syntax OK notify-unvetted syntax OK report-unvetted syntax OK state-mon syntax OK