You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I support @jsmeix point, we should not modify the existing defaults: admins may have implemented some post-processing with the rear log file (parse it/copy it somewhere/...) and changing the default name would break that.
Currently we have ./usr/share/rear/conf/default.conf:LOGFILE="$LOG_DIR/rear-$HOSTNAME.log" as a default. If there is a consensus to keep it as it is now then that is fine for me.
Others may have a different opinion, but then I would like to read it here...
Currently subsequent runs of "rear <workflow>"
keep exactly one old log file in a hardcoded way
in usr/sbin/rear
Because of #709 (comment) I like to discuss here
whether or not this should be changed to use rear-$(hostname)-$WORKFLOW-.log in any case
The advantage is that unlimited old log files are kept.
The disadvantage is that unlimited old log files are kept
which could fill up the harddisk.
Perhaps the solution is to make the behaviour configurable
via usr/share/rear/conf/default.conf and voila! it is already there
The admin can change this to
Therefore from my point of view there is nothing to change here
and I set this issue initially to "fixed" and "waiting for feedback".
FYI:
With unique LOGFILE names like
one does not get *.old copies because for each "rear" run
the new LOGFILE name does not already exist.
The text was updated successfully, but these errors were encountered: