How to use config.yml

[story-lo]

In the windows system, I deployed an hsds using the file storage method. How can I deploy multiple hsds servers with different ports.I use the following command for deployment. And config.yml is located under the config folder
hsds --root_dir D:/hsds_data --host localhost --port 5101 --password_file config/passwd.txt --config_dir .\config --logfile hs.log

Under another project, I opened another command line to run hsds. At this time, I changed the port to 5199 and modified the parameters such as dn_port and head_port in config.yml, which were different from the first time. But at this point, an error was reported. I checked the log and found out
task: <Task finished name='Task-2' coro=<_run_app() done, defined at > exception=OSError(10048, "error while attempting to bind on address ('::', 6101, 0, 0): 通常每个套接字地址(协议/网络地址/端口)只允许使用一次。")>......and`WARNING:root:process sn ended, result: ('', None)
WARNING:root:_enqueue_output - ValueError (handle closed?): I/O operation on closed file
WARNING:root:process dn0 ended, result: ('', None)
WARNING:root:_enqueue_output - ValueError (handle closed?): I/O operation on closed file
WARNING:root:process dn1 ended, result: ('', None)
WARNING:root:_enqueue_output - ValueError (handle closed?): I/O operation on closed file
WARNING:root:process dn2 ended, result: ('', None)
WARNING:root:_enqueue_output - ValueError (handle closed?): I/O operation on closed file
WARNING:root:process dn3 ended, result: ('', None)

WARNING:root:_enqueue_output - ValueError (handle closed?): I/O operation on closed file
READY! use endpoint: http://localhost:5101`
I confirm that no other ports conflict with these two ports. It seems that my config.yml has no effect at all. It still uses the same configuration. I want to know how I can deploy multiple hsds on the same computer, and they use different ports

[jreadey]

I tried running multiple hsds apps and got the same error as you are seeing. The _enqueue_output operation reads from the process std out and combines output from the various HSDS processes to a shared log file. You'd think process std out would be independent no matter how many processes you have, so I'm a bit mystified by the error.

Can you run hsds in docker? That would ensure isolation from the multiple HSDS services. You'd just need to ensure that the port that get's mapped to the host (based on the SN_PORT env variable) is distinct for each Docker application.

Also, for Windows, I'd recommend running HSDS on WSL2. The HSDS ports will still be accessible from Windows processes and you'll have a more standard environment for running HSDS. I did a Call the Doctor talk about this a few weeks ago: https://www.youtube.com/watch?v=FP-8NQJ5bvw&pp=ygUcaGRmZ3JvdXAgY2FsbCB0aGUgZG9jdG9yIHdzbA%3D%3D.