# How to configure which port workers listen

**URL:** <https://discourse.julialang.org/t/how-to-configure-which-port-workers-listen/46759>\
**Category:** Julia at Scale\
**Created:** [September 17, 2020, 8:16am UTC](https://discourse.julialang.org/t/how-to-configure-which-port-workers-listen/46759 "2020-09-17T08:16:10Z")\
**Posts on this page:** 1\
**Showing post:** 8

<div class="post-metadata">

**Author:** ![DrChainsaw](https://sea2.discourse-cdn.com/julialang/user_avatar/discourse.julialang.org/drchainsaw/32/8497_2.png) [@DrChainsaw](https://discourse.julialang.org/u/DrChainsaw)\
**Post date:** [September 24, 2020, 12:16pm UTC](https://discourse.julialang.org/t/how-to-configure-which-port-workers-listen/46759/8 "2020-09-24T12:16:31Z")

</div>

I guess I could, but the startup time would be unnecessary to just print a number.

It would be interesting to have a richer worker startup script but I just could not find the effort to dig out what that --worker flag does. Do you think it would allow for not running that annoying `@everywhere` expression after workers are added? That could possibly alleviate [that other issue](https://discourse.julialang.org/t/adding-remote-workers-to-ongoing-dagger-job/47196/2) I’m investigating.

Adding a script when the worker flag is present seems to prevent the script from executing. If all --worker does is printing out the ip and port then it is ofc not much to duplicate. At one point I was contemplating to just feed a malformed IP address and follow the stacktrace to reverse engineer what happens but once I got a working solution there were other problems to focus on.

---

_[View the full topic](https://discourse.julialang.org/t/how-to-configure-which-port-workers-listen/46759)._