{"comment":{"created_at":"2011-11-27T21:41:41Z","commit_id":"0530b687b690652c880668e04938d107362a0177","position":4,"updated_at":"2011-11-27T21:41:41Z","user":{"gravatar_id":"6094658f2aaf855ab9f330a08e12cf93","id":20242,"url":"https://api.github.com/users/masterzen","login":"masterzen","avatar_url":"https://secure.gravatar.com/avatar/6094658f2aaf855ab9f330a08e12cf93?d=https://a248.e.akamai.net/assets.github.com%2Fimages%2Fgravatars%2Fgravatar-140.png"},"body":"Yes it's not a config option, but it has been proposed to be an option in the ticket :)\nBasically if we run in a daemon we sub-fork, otherwise we do it the old way.\n\nApparently the only thing we're ever doing with the report in the --onetime case is: exit(report.exit_status) if --detailed-exit-codes is on. Otherwise we're only exit 1/0 depending on if something bad happened.\n\nUnfortunately the Puppet::Agent code is much more open than what the client use. So we can either close it and only report a status code (which can be returned from the forked process) or stay like this and don't care :) ","id":749197,"path":"lib/puppet/agent.rb","line":12,"html_url":"https://github.com/masterzen/puppet/commit/0530b687b6#commitcomment-749197","url":"https://api.github.com/repos/masterzen/puppet/comments/749197"}}