Created
November 19, 2022 15:25
-
-
Save MBurchard/e166dc0c3c041c7e6f179efd88385cdb to your computer and use it in GitHub Desktop.
snowflake-proxy service
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
| [Unit] | |
| Description=Snowflake | |
| Wants=network.target | |
| After=syslog.target network-online.target | |
| StartLimitIntervalSec=300 | |
| StartLimitBurst=10 | |
| [Service] | |
| Type=simple | |
| ExecStart=/home/snowflake/snowflake/proxy/proxy -verbose | |
| Restart=on-failure | |
| RestartSec=5 | |
| KillMode=process | |
| User=snowflake | |
| Group=snowflake | |
| StandardOutput=append:/var/log/snowflake.log | |
| StandardError=append:/var/log/snowflake.log | |
| [Install] | |
| WantedBy=multi-user.target |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Just came across this and figured I'd explain in case someone else does too.
When you're using the systemd StandardOutput or StandardError directives, these streams are redirected by the systemd daemon itself, which is running as root, so the snowflake proxy service doesn't need write access to the log file. When you use the command line switch, it opens the log file itself, in which case it does need write access.