Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Conflict in temporary files in multi-user system #2

Open
arpaiva opened this issue Jul 19, 2023 · 3 comments
Open

Conflict in temporary files in multi-user system #2

arpaiva opened this issue Jul 19, 2023 · 3 comments

Comments

@arpaiva
Copy link

arpaiva commented Jul 19, 2023

I'm using mlxu (0.1.10) and noticed that it creates temporary files under /tmp/mlxu. The problem with the current framework is that, if multiple people are using the system and running experiments using mlxu, the mlxu folder in temp in /tmp/ is created with write permissions only for whoever first created the folder. Is there a way to get around this? Perhaps by setting an environment variable that puts those folders elsewhere?

I would suggest in the future making the temp folder /tmp/mlxu_<uid>/ for example to avoid this problem.

@young-geng
Copy link
Owner

The /tmp/mlxu is created by the logger. In order to change it, you can use command line flags to specify the logging directory:

python experiment.py --logger.output_dir=/path/to/logger/output

@arpaiva
Copy link
Author

arpaiva commented Sep 5, 2023

That is good to know. Thank you.

I still think that it would be good to set the default directory to something a bit more general and robust (#3). Also, it shouldn't break any properly written code because one would either be relying on whatever the default directory is or setting it explicitly. Can you think of a reason not to implement that change?

@arpaiva
Copy link
Author

arpaiva commented May 4, 2024

This issue has been open for a while. If you disagree or don't want to apply this change for whatever reason, I understand. Even in that case, please close this issue and the associated PR to mark it one way or the other.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants