# Sudo clarification, and what it means for DEBUG and -D

**URL:** <https://forum.ansible.com/t/sudo-clarification-and-what-it-means-for-debug-and-d/11465>\
**Category:** Ansible Project\
**Created:** [April 28, 2012, 1:26pm UTC](https://forum.ansible.com/t/sudo-clarification-and-what-it-means-for-debug-and-d/11465 "2012-04-28T13:26:14Z")\
**Posts on this page:** 1\
**Page:** 1

<div class="post-metadata">

**Author:** ![Michael\_DeHaan](https://avatars.discourse-cdn.com/v4/letter/m/c4cdca/32.png) [@Michael\_DeHaan](https://forum.ansible.com/u/Michael_DeHaan)\
**Post date:** [April 28, 2012, 1:26pm UTC](https://forum.ansible.com/t/sudo-clarification-and-what-it-means-for-debug-and-d/11465/1 "2012-04-28T13:26:14Z")

</div>

Per paramiko docs: Only channels using exec\_command or invoke\_shell WITHOUT a pty will ever have data on the stderr stream.

This means modules can’t output things to stderr, more or less. If a module does return something unparseable, we can still have Ansible  
return information about what went wrong, but debug should probably just go to /var/log/messages via /usr/bin/logger or BETTER, python standard  
logging classes.

I will be changing modules to remove debug so they can continue working with sudo, and then reinstating upgraded sudo.

–Michael