Cuong Manh Le 8e164185b9 cmd/ctrld: always pass config file on windows start mode ...

On windows, the SYSTEM user is used to run ctrld service. This user has
different environment with the user that run the `ctrld` binary via CLI.
That causes the mismatch issue in config file path, log path, or more
generally, everything that involve with home directory.

To circumvent this pain, just always passing the config path and the
original home dir in start mode. So `ctrld run` command can setup things
correctly.

2023-01-20 21:37:50 +07:00

..

cli.go

cmd/ctrld: always pass config file on windows start mode

2023-01-20 21:37:50 +07:00

dns_proxy_test.go

Import code, preparing for release

2022-12-13 01:27:48 +07:00

dns_proxy.go

all: add starting service with Control D config

2023-01-20 21:33:38 +07:00

main.go

cmd/ctrld: always pass config file on windows start mode

2023-01-20 21:37:50 +07:00

net.go

cmd/ctrld: make "--cd" always owerwrites the config

2023-01-20 21:37:34 +07:00

os_linux.go

Import code, preparing for release

2022-12-13 01:27:48 +07:00

os_mac.go

Import code, preparing for release

2022-12-13 01:27:48 +07:00

os_windows.go

Import code, preparing for release

2022-12-13 01:27:48 +07:00

prog.go

all: add local caching

2023-01-20 21:33:01 +07:00

service.go

cmd/ctrld: add commands to control ctrld as a system service

2023-01-20 21:33:31 +07:00