QUESTION - npbackup log file location

[netinvent]

QUESTION - npbackup log file location

[deajan]

As of current NPBackup version, logfile path is not configurable.
New version of NPBackup is comming soon, and the workflow will look like:

• If --logfile= then create logfile in
• else if /var/log exists and is writable, then create logfile there
• else if current directory is writable, then create logfile there
• else create logfile in tmpdir

Is that behavior something you'd expect ?

[GuitarBilly]

yes this behaviour makes sense to me.

Can you elaborate on how to handle the situation if the --logfile= location cannot be written to? I would expect to throw an error and abort as the user explicitly/deliberately wants to override the logfile location.

But (as you already described) without --logfile= provided I would expect it to try /var/log then currentdir then tmpdir.

[deajan]

IMO, even with --logfile=/some/unwritable/path, I prefer the backups to run.
Imagine being stuck because your log partition is full, and no backup is run anymore.

[GuitarBilly]

Fair enough, and I think either way will be an improvement!

Do you want to keep this issue open for tracking of the feature?
Else it can be closed as my question is answered.

[deajan]

Thanks for the "housekeeping", but yes, I'll keep that open until everything is implemented.
I've rewritten the logging code after the CLI/GUI split, and it's not writing to /var/log by default right now.