# Mechanics of sudo

**URL:** <https://forum.ansible.com/t/mechanics-of-sudo/14666>\
**Category:** Ansible Project\
**Created:** [February 27, 2014, 6:45pm UTC](https://forum.ansible.com/t/mechanics-of-sudo/14666 "2014-02-27T18:45:20Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![Deyna\_Cegielski](https://avatars.discourse-cdn.com/v4/letter/d/45deac/32.png) [@Deyna\_Cegielski](https://forum.ansible.com/u/Deyna_Cegielski)\
**Post date:** [February 27, 2014, 6:45pm UTC](https://forum.ansible.com/t/mechanics-of-sudo/14666/1 "2014-02-27T18:45:20Z")

</div>

I’ve run into a bit of a brick wall with Ansible.

As part of my playbook I’ve created an “application daemon” user. This user is responsible for running any software deployed to the provisioned machine. Its not a sudoer.

I’m trying to execute some post deployment tasks and one of them is to run a program I’ve installed as the application user. Everything else in the playbook is executed as root (using sudo from vagrant user) e.g.

---

<div class="post-metadata">

**Author:** ![Brian\_Coca1](https://avatars.discourse-cdn.com/v4/letter/b/278dde/32.png) [@Brian\_Coca1](https://forum.ansible.com/u/Brian_Coca1)\
**Post date:** [February 28, 2014, 1:53pm UTC](https://forum.ansible.com/t/mechanics-of-sudo/14666/2 "2014-02-28T13:53:05Z")

</div>

using -vvvv should show you what ansible runs