-
Notifications
You must be signed in to change notification settings - Fork 195
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Detached mode and logs #8
Comments
"-d" argument seems like an interesting idea. However, adding this might bring some issue with Windows compatibility. First, you would like to create a start.sh file next to your zoraxy binary. Assuming your binary file is located at /home/user/zoraxy/src/zoraxy
Put the following lines into start.sh, save and exit
Then assign the correct permission to the start script
Next, you can add it to systemd service with the following commands
In the service file, fill in the following info
Lastly, enable and start the systemd service
Then it should be running as a valid daemon which will start following your server (or container) startup. As I am no expert in LXC, I can only provide you answer under normal Linux (Debian) based installation. If you have issues using systemd in your container, I guess you might need to seek help from the developer who provided the container / docker configs. |
Okay now it is running with systemd. Did not think about systemd :D I needed to modify your scripts and now it runs just fine. For quick testing a "-d" would still be great :) Here are my steps:
Put in those lines
Put in following lines:
Now status and logs can be displayed with:
Logs-files would still be great, but thanks for the help with autostart |
Thanks for that grate tool! 👍🏻 A little fix. :)
|
init.d script for those who want (some thin lxc images still use rc.d - alpine for example)
|
First: Thanks for this great program!
I am testing zoraxy inside LXC and I would like to know if there is any detached mode? At the moment I use screen to detach zoraxy output. I can not leave the CLI open the whole time.
It would be cool to start zoraxy with a "-d" argument in the background.
Then I would like to know if there are any logs?
The text was updated successfully, but these errors were encountered: