# Using a machine file on a cluster but also propagating environment to the remote workers

**URL:** <https://discourse.julialang.org/t/using-a-machine-file-on-a-cluster-but-also-propagating-environment-to-the-remote-workers/38948>\
**Category:** Julia at Scale\
**Tags:** question\
**Created:** [May 7, 2020, 11:38am UTC](https://discourse.julialang.org/t/using-a-machine-file-on-a-cluster-but-also-propagating-environment-to-the-remote-workers/38948 "2020-05-07T11:38:17Z")\
**Posts on this page:** 1\
**Showing post:** 6

<div class="post-metadata">

**Author:** ![orialb](https://avatars.discourse-cdn.com/v4/letter/o/65b543/32.png) [@orialb](https://discourse.julialang.org/u/orialb)\
**Post date:** [May 7, 2020, 1:57pm UTC](https://discourse.julialang.org/t/using-a-machine-file-on-a-cluster-but-also-propagating-environment-to-the-remote-workers/38948/6 "2020-05-07T13:57:55Z")

</div>

I’m doing it as part of the sbatch script, it should be set on the compute node. But I’m not using machine files so maybe it’s different?  
I just start the processes from within the Julia script with

```julia
using ClusterManagers
addprocs(SlurmManager(nworkers))

```

The is also the `--project=path/to/environment` flag that you can try using instead, I don’t remember if I tried that on my cluster (there are some older discussions here about workers and environment activation)

---

_[View the full topic](https://discourse.julialang.org/t/using-a-machine-file-on-a-cluster-but-also-propagating-environment-to-the-remote-workers/38948)._