AdGuardHome binary ignores its working direcotry

[flipreverse]

AdGuardHome binary ignores its working direcotry

[ElTopo]

I think you are confused with systemd service's WorkingDirectory and AdGuardHome's work-dir.

systemd service's WorkingDirectory: the directory that systemd uses to launch service
https://www.freedesktop.org/software/systemd/man/latest/systemd.exec.html#WorkingDirectory=

AdGuardHome's work-dir: the directory that AdGuardHome uses to store data. From the code, either you use -w option, or the executable file path

AdGuardHome/internal/home/home.go

Line 780 in 48c6242

func initWorkingDir(opts options) (err error) {

Basically, they are different things... until the developer decides to use systemd service's WorkingDirectory as AdGuardHome's work-dir.

Hi @flipreverse, thanks for the report.
Can you confirm which OS you're using?

[flipreverse]

Hi @flipreverse, thanks for the report. Can you confirm which OS you're using?

I see this behavior on Debian Testing arm64 (aka Trixie) as well as on Debian 12 arm64 (bookworm aka Raspbian) .

Hi @flipreverse, it is working correctly, it will place the working directory by default within the AdGuard Home binary folder.

As you've mentioned in the first comment, using the -w argument resolves this, and that will be persistent until it's changed again.

Does this resolve your issue?

[flipreverse]

Hi @flipreverse, it is working correctly, it will place the working directory by default within the AdGuard Home binary folder.

As you've mentioned in the first comment, using the -w argument resolves this, and that will be persistent until it's changed again.

Does this resolve your issue?

Yeah, that resolves my issue. Thank you!
AS @ElTopo mentioned, I got mislead by systemd's WorkingDirectory direcive