mtkennerly / shawl

Windows service wrapper for arbitrary commands
MIT License
520 stars 15 forks source link

Custom log path for "shawl_for" #13

Closed mark05e closed 2 years ago

mark05e commented 3 years ago

Thank you for making this project. 🙂

Wondering if you could add parameter to allow custom log path for shawl_for_<service>_*.log instead of at the shawl executable. I understand that there is a possibility of redirecting the logs but then it might be harder to maintain the size or rotation.

mtkennerly commented 3 years ago

That sounds like a good idea :+1:

adiroiban commented 3 years ago

Thanks for creating shawl :)

Another reason for having a custom log path is to improve the security of the deployment.

You might want to have your window service run under a dedicated service account. That service account should not have write access to the application files.

The service account has write access to a separate log directory.

Then shawl can use the same log directory.