# remote\_tmp

**URL:** <https://forum.ansible.com/t/remote-tmp/25526>\
**Category:** Ansible Project\
**Created:** [September 19, 2017, 1:48pm UTC](https://forum.ansible.com/t/remote-tmp/25526 "2017-09-19T13:48:40Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![Siva](https://avatars.discourse-cdn.com/v4/letter/s/7c8e57/32.png) [@Siva](https://forum.ansible.com/u/Siva)\
**Post date:** [September 19, 2017, 1:48pm UTC](https://forum.ansible.com/t/remote-tmp/25526/1 "2017-09-19T13:48:40Z")

</div>

Hi,

We have overridden the remote\_tmp as “$HOME/.ansible/tmp” in the ansible\_cfg but still ansible uses the ‘/tmp’ and the entire execution fails because we dont have ‘/tmp’ allocated with enough space to perform our execution.

Can anyone help us where we might go wrong?

Regards,  
Siva

---

<div class="post-metadata">

**Author:** ![system](https://us1.discourse-cdn.com/ansible/original/1X/1882d9a01da5d8996a862359b0913cc568a39b84.svg) [@system](https://forum.ansible.com/u/system)\
**Post date:** [September 19, 2017, 2:57pm UTC](https://forum.ansible.com/t/remote-tmp/25526/2 "2017-09-19T14:57:31Z")

</div>

In some cases, mostly when you 'become' an unprivileged user, Ansible  
needs to use a 'system temp' which will be /tmp by default, /var/tmp  
if that is the configured remote\_tmp.

This is inconvenient because currently it is a global setting, we do  
plan to making it a connection variable to allow a lot more flexible  
configuration in the future.