Open evert-mouw opened 9 months ago
that's cool but provision of service scripts has and will always be the responsibility of linux distros, not the software package itself. means i won't be adding this to the repo. i'll leave this open though so users can immediately see and copy/paste your script.
Could go in a "docs/examples" directory?
On Fri, 15 Dec 2023, 10:06 rofl0r, @.***> wrote:
that's cool but provision of service scripts has and will always be the responsibility of linux distros, not the software package itself. means i won't be adding this to the repo. i'll leave this open though so users can immediately see and copy/paste your script.
— Reply to this email directly, view it on GitHub https://github.com/rofl0r/microsocks/issues/69#issuecomment-1857603520, or unsubscribe https://github.com/notifications/unsubscribe-auth/AB4TJUXAFINOA55OZOWH46DYJQOLLAVCNFSM6AAAAABAOT5V42VHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMYTQNJXGYYDGNJSGA . You are receiving this because you are subscribed to this thread.Message ID: @.***>
TBH I'm not a huge fan of SystemD (although it has its uses) so I like software staying init neutral.
But adding it to e.g. docs/examples
as @srd424 suggested maybe makes more sense than leaving issues open?
PS: Thanks for creating microsocks, it Just Works :-)
e.g. this works for me on Debian
microsocks.service
/etc/microsocks.conf
It's a bit simple, and could be expanded by improving security (chroot, user=nobody, logging, whatever) but it just works.