Comment 4 for bug 1304286

There is some additional changes must be done for astute part:
1) -o and -e options won't redirect any puppet output to specified files, if logdest was used. To check this run
daemonize -v -a -o out.txt -e err.txt /usr/bin/puppet apply -e "nootify {"foo":}" --logdest syslog
and compare results with
daemonize -v -a -o out.txt -e err.txt /usr/bin/puppet apply -e "nootify {"foo":}"
For the 1st case none logs would go to er.txt but to the syslog instead
And for the second case - errors would go to err.txt - but we don't need it anymore, if logdest was specified...

2) We don't need to specify --logdest in @puppetd - as you can see from mcagents/puppetd.rb puppet will be called with logdest syslog anyway, so we just make this option doubled. See grep logdest in diagnostic snapshots:
/usr/bin/puppet apply /etc/puppet/manifests/site.pp --logdest syslog --logdest syslog --trace --debug

3) We could as well use --evaltrace for debug case to see timings...

And besides that, there are still some issues exist with missed puppet logs in CI gates, see https://bugs.launchpad.net/bugs/1308684 ...