Suppressing ray_client_server_[port].out/err on new ray.init connections to ray head

Anyone know if there’s a way to prevent ray.init connections to a remote cluster from creating ray_client_server_[port].out/err files? Is there some flag we can set to suppress this?

I’m very close to writing a cron job that deletes those log files since they’re clogging things up for us :joy:

How severe does this issue affect your experience of using Ray?

  • Medium: It contributes to significant difficulty to complete my task, but I can work around it.

See following discussion in ray slack: Slack