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
{{ message }}
This repository has been archived by the owner on Dec 10, 2019. It is now read-only.
The only reason I choose to use this rather than C# version is to run a SS client on a server (and then allows other computers to access the proxy without a SS client). However, this version of SS has to run in interactive mode, and thus I can't install it as a service (Windows would consider that this "service" has never completed the starting up).
Linux server isn't an option so no "screen" program available (plus "screen" also isn't the best solution in this case). I don't want to enable startup program feature (since it's a server not a workstation), nor do I want to use a probably proprietary 3rd-party daemonizing program to do the job.
My only solution for now is to run the program as a never-ending scheduled task that is triggered on system startup, which isn't the best solution since it will not automatically restart after crashes.
So, would anyone implementing the feature that, when the program is run with "--service" parameter, it will run in background rather than occupying the terminal, so that daemonizing this program (run it as a Windows or Linux service) become possible?
The text was updated successfully, but these errors were encountered:
The only reason I choose to use this rather than C# version is to run a SS client on a server (and then allows other computers to access the proxy without a SS client). However, this version of SS has to run in interactive mode, and thus I can't install it as a service (Windows would consider that this "service" has never completed the starting up).
Linux server isn't an option so no "screen" program available (plus "screen" also isn't the best solution in this case). I don't want to enable startup program feature (since it's a server not a workstation), nor do I want to use a probably proprietary 3rd-party daemonizing program to do the job.
My only solution for now is to run the program as a never-ending scheduled task that is triggered on system startup, which isn't the best solution since it will not automatically restart after crashes.
So, would anyone implementing the feature that, when the program is run with "--service" parameter, it will run in background rather than occupying the terminal, so that daemonizing this program (run it as a Windows or Linux service) become possible?
The text was updated successfully, but these errors were encountered: