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
The story is around having some sort of feedback, to actually see the process is not stuck. IIRC in case of a rsync failure the logs of rsync are kept and included within elemental logs, that's why the --human-readable is there. We used to have weird race issues while trying to also stream the logs from rsync to elemental-logs (we were using an external library we dropped because of that) so we opted for a safe an simple approach. We can revisit it though and do an attempt of including some sort of progress data on each Syncing data....
In any case this can be slightly tricky and provide arguable value.
in case of a rsync failure the logs of rsync are kept
maybe simply adding one log line, saying where the logs are ?
Then people interested in details can switch from journalctl -f to tail -f <rsync-log-file> ?!
NOTE: issue transfered from elemental-operator to elemental-toolkit as the rsync call and logs come from the "install" call of the toolkit "elemental" binary.
I see that
rsync
gets called with--human-readable
but the actual output doesn't reach the logs.There is a (repeated)
Syncing data...
output but that's rather useless for actual progress.The text was updated successfully, but these errors were encountered: