Setup skeleton audit log

[corbin-phipps]

Type

• Bug fix
• Feature addition
• Feature update
• Documentation
• Build Infrastructure

Side Effects

• Breaking change
• Non-functional change

Goals

This PR sets up the foundation for the Wi-Fi state audit log.

Technical Details

• Added a PLOG RollingFileAppender separate from the existing logging to be used for writing to the audit log file.
• Added audit log macros in the form of AUDIT_LOG*.
• Ensured that log files are actually present by specifying the path to /usr/local/.

Test Results

Verified that the AUDIT_LOGN line added to Main shows up in /usr/local/202407-LogNetRemote-audit.txt.

Reviewer Focus

I'm not sure if /usr/local is the best place, but omitting that and just using what is returned by GetLogName doesn't seem to create a log file anywhere.

Future Work

Write Wi-Fi state and events to the audit log.

Checklist

• Build target all compiles cleanly.
• clang-format and clang-tidy deltas produced no new output.
• Newly added functions include doxygen-style comment block.

[abeltrano]

I'm not sure if /usr/local is the best place, but omitting that and just using what is returned by GetLogName doesn't seem to create a log file anywhere.

The log file as currently used, will be created in the current working directory of the binary. This is configurable using the WorkingDirectory= configuration directive in [Service] section of the netremote-server systemd unit file. I'd guess the binary doesn't have permission to write to that directory (/usr/bin or /usr/local/bin) since the service is started as a non-root user. So, the fix should be to set WorkingDirectory to something a regular user can access.

[abeltrano]

I'm not sure if /usr/local is the best place, but omitting that and just using what is returned by GetLogName doesn't seem to create a log file anywhere.

The log file as currently used, will be created in the current working directory of the binary. This is configurable using the WorkingDirectory= configuration directive in [Service] section of the netremote-server systemd unit file. I'd guess the binary doesn't have permission to write to that directory (/usr/bin or /usr/local/bin) since the service is started as a non-root user. So, the fix should be to set WorkingDirectory to something a regular user can access, like /var/log.