You are not logged in.
Hi,
Before upgrading XSIBackup-DC to version 1.7.1.7 I was at 1.5.2.1 where I had no problems to invoke xsibackup while redirecting its output into a dedicated log file. I used the following command, adapted to the new location of xsibackup:
TS=`date +%Y%m%d%H%M%S`
/scratch/XSI/XSIBackup-DC/xsibackup <options> >> "/scratch/XSI/XSIBackup-DC/var/log/xsibackup-$TS.log" 2>&1
The result now is that XSIBackup-DC creates a separate log file by its own, stored in /scratch/XSI/XSIBackup-DC/var/log/xsibackup.log. A very small portion of the log file content was in my file /scratch/XSI/XSIBackup-DC/var/log/xsibackup-$TS.log and another part in the automatically created /scratch/XSI/XSIBackup-DC/var/log/xsibackup.log.
As a second try, I removed my redirection and started again. Unfortunately, the written log file did not contain all the output that was shown on screen.
What I would like to obtain is that the full output is written into a file.
Do you have any hints as how to achieve this with the latest version of XSIBackup-DC?
Best regards,
Peter
Offline
We created a date line prefixed log file as requested by the majority of users. This is also something rather canonical. If you miss some info in the log increase verbosity, if you still miss something create a feature request for that info to be added.
Offline
I realized that the log file that is automatically written includes a lot of #00 (ASCII character zero) before the log output actually starts. How can this be avoided? Opening such a log file with a plain text editor causes problems as you need to scroll down a long time until the relevant log file content is visible.
Last edited by herrep (2024-04-07 17:23:50)
Offline
I have the same problem.
It's not about verbosity or timestamp, after updating from version 1.5.2.1 to version 1.7.1.7 the log redirect in the scripts is ignored and always sent to "/scratch/XSI/XSIBackup-DC/var/log/xsibackup.log".
What can we do to be free to manage output redirection as we did before?
Thank you
Offline