# Is there something unusual about how the TMPDIR is being set in 2023.2?

**URL:** https://forum.qiime2.org/t/is-there-something-unusual-about-how-the-tmpdir-is-being-set-in-2023-2/26402
**Category:** Technical Support
**Tags:** diversity
**Created:** [May 10, 2023, 4:00pm UTC](https://forum.qiime2.org/t/is-there-something-unusual-about-how-the-tmpdir-is-being-set-in-2023-2/26402 "2023-05-10T16:00:08Z")
**Posts on this page:** 1
**Showing post:** 8

<div class="post-metadata">

### Author: ![Mechah](https://forum.qiime2.org/user_avatar/forum.qiime2.org/mechah/32/7261_2.png) [@Mechah](https://forum.qiime2.org/u/Mechah)
#### Post date: [May 16, 2023, 5:02pm UTC](https://forum.qiime2.org/t/is-there-something-unusual-about-how-the-tmpdir-is-being-set-in-2023-2/26402/8 "2023-05-16T17:02:12Z")

</div>

Hi Justin and Evan,  
we also had trouble executing our standard SLURM qiime2-2023.2 scripts on our HPC system. Our solution was to empty the TMPDIR prior to any executions by including something like this in the bash script (before activating, running and deactivating the conda qiime2-2023.2 environment):

#!/bin/bash

#SBATCH --job-name=qiime2  
#SBATCH --cpus-per-task=2  
#SBATCH --output=log/qiime2-%j.out  
#SBATCH --error=log/qiime2-%j.err

**hostname**  
**rm -r $TEMP/qiime2**

Maybe it is of any applicability to you or other QIIME2 users...

---

_[View the full topic](https://forum.qiime2.org/t/is-there-something-unusual-about-how-the-tmpdir-is-being-set-in-2023-2/26402)._