You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I believe this FR is applicable to all OS's currently. In the DN implementation of Nebula (dnclient), we offer a -name flag that allows running multiple services at once.
Originally posted by zodiaq April 12, 2024
Now, we can install Nebula in Windows platform as a Windows service.
However, because it always creates a service with the same name "Nebula", I need to run nebula.exe as a process instead when I need to connect another Nebula network.
Could we run multiple Nebula services to connect multiple Nebula networks rather than running individual user processes?
For example, how is it if we could specify the service name when installing the service?
Unless Nebula has a problem when running as multiple services in the same PC, I think it's a useful feature.
The text was updated successfully, but these errors were encountered:
I have the same need (on Windows) to run more than one service instance (2, to be exact). I added an optional "-name" parameter to the service registration that replaces the constant string "Nebula" in cmd/service.go, when setting up svcConfig, and adjusted DisplayName to contain this name so that the Services manager window shows different names in the Name column, and different Description in task manager, for differently registered instances. "It seems to work for me (TM)".
I believe this FR is applicable to all OS's currently. In the DN implementation of Nebula (dnclient), we offer a
-name
flag that allows running multiple services at once.Discussed in #1117
Originally posted by zodiaq April 12, 2024
Now, we can install Nebula in Windows platform as a Windows service.
However, because it always creates a service with the same name "Nebula", I need to run nebula.exe as a process instead when I need to connect another Nebula network.
Could we run multiple Nebula services to connect multiple Nebula networks rather than running individual user processes?
For example, how is it if we could specify the service name when installing the service?
Unless Nebula has a problem when running as multiple services in the same PC, I think it's a useful feature.
The text was updated successfully, but these errors were encountered: