2.0rc1: `-C/--engine-conf` from the command line is ignored; the engine always runs with /etc/snapraid.conf

[karan]

The SnapRAID array config cannot be relocated out of its -sysconfdir default even with the documented override.

Starting snapraidd with both -c ...snapraidd.conf -C ...snapraid.conf (systemd ExecStart or CLI) has no effect on spawned engine commands. The runner only passes -c to the engine.

Repro:

1. snapraidd 39d55cd (built with ./autogen.sh && ./configure --prefix=/usr --sysconfdir=/etc && make && sudo make install)
2. sudo cp /etc/snapraid.conf /home/user/snapraid.conf
3. Start with: sudo /usr/bin/snapraidd -c /etc/snapraidd.conf -C /home/user/snapraid.conf
4. Trigger a task (REST /schedule -> diff or probe)
5. Inspect task log - engine argv is snapraid -c /etc/snapraid.conf ...

Expected: snapraid -c /home/user/snapraid.conf ...

Actual: snapraid -c /etc/snapraid.conf ...

Env: Ubuntu 24.04 (x86_64, kernel 6.8.0-138-generic), systemd Type=forking service.

[amadvance]

Passing -c to the engine is expected because the SnapRAID CLI only accepts -c for its configuration file.
The -C override appeared to have no effect because the daemon was silently reloading the default /etc/snapraid.conf path from previous execution logs found in the log directory during startup.
The command-line override is now decoupled from log history parsing, so the -C path is strictly preserved and passed to all spawned engine commands.

[karan]

Thank you - verified fixed!