Skip to content

Instantly share code, notes, and snippets.

@infernalsirius
Last active April 16, 2023 05:43
Show Gist options
  • Star 1 You must be signed in to star a gist
  • Fork 0 You must be signed in to fork a gist
  • Save infernalsirius/505b919e23812c767806ac07f5cda07c to your computer and use it in GitHub Desktop.
Save infernalsirius/505b919e23812c767806ac07f5cda07c to your computer and use it in GitHub Desktop.
[Edgerouter] Cheatsheet #edgeOS #shell

Running as a service

The next step would be to register AdGuard Home as a system service on Windows, Linux/(systemd | Upstart | SysV), or OSX/Launchd.

Run sudo ./AdGuardHome -s install to install AdGuard Home as a system service.

On Windows run cmd.exe with admin privileges and run AdGuardHome.exe -s install to register a windows service.

Here are the other commands you might need to control the service.

AdGuardHome -s uninstall - uninstalls the AdGuard Home service.
AdGuardHome -s start - starts the service.
AdGuardHome -s stop - stops the service.
AdGuardHome -s restart - restarts the service.
AdGuardHome -s status - shows the current service status.

Logs

By default, the log is written to stderr when you run AdGuard Home as a console application.

If you run it as a service/daemon, the log output depends on the platform:

Linux: the log is written to syslog.
MacOS: the log is written to /var/log/AdGuardHome.*.log files.
Windows: the log is written to the Windows event log.

You can redefine this behavior in the AdGuard Home configuration file.

cat /proc/net/arp
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment