** Changed in: backintime
Status: New => Confirmed
--
Backintime log line truncated
https://bugs.launchpad.net/bugs/503914
You received this bug notification because you are a member of Back In
Time Team, which is subscribed to Back In Time.
Status in Back In Time: Confirmed
Bug description:
I've just noticed that my daily backups have been failing for the past few
days, I suspect that this is is because I've moved some large folders and am
encountering problems space problems as a result.
A WARNING message is written to the messages log file, but it is truncated at
1028 characters (as are several other INFO messages), leaving me with no
meaningful information as to what it is trying to tell me. It's important that
backup failures are reported very clearly and explicitely. I'd expect the
failure to be reported as ERROR, or possibly even FATAL.
Eg
Jan 5 00:20:04 ACHILLES backintime (root): INFO: Call rsync to take the
snapshot
Jan 5 00:40:19 ACHILLES backintime (root): WARNING: Command "rsync -aEAX -v
--delete-excluded --chmod=Fa-w,D+w --whole-file --delete --exclude="/backup"
--exclude="/root/.local/share/backintime" --include="/bin/" --include="/boot/"
--include="/dev/" --include="/etc/" --include="/home/" --include="/lib/"
--include="/lib32/" --include="/lib64/" --include="/opt/" --include="/root/"
--include="/sbin/" --include="/selinux/" --include="/srv/" --include="/sys/"
--include="/usr/" --include="/var/" --include="//" --exclude="/backup"
--exclude="/cdrom" --exclude="/lost+found" --exclude="/media" --exclude="/mnt"
--exclude="/proc" --exclude="/tmp" --exclude="/var/cache" --exclude="/var/tmp"
--exclude="*.vdi" --exclude=".gvfs" --exclude="*~" --include="/bin/**"
--include="/boot/**" --include="/dev/**" --include="/etc/**"
--include="/home/**" --include="/lib/**" --include="/lib32/**"
--include="/lib64/**" --include="/opt/**" --include="/root/**"
--include="/sbin/**" --include="/selinux/**" --include="/srv/**" --include="/
Jan 5 00:40:19 ACHILLES backintime (root): INFO: Save permissions
Would it be possible for you to use multiple log statements sequentially to
split the log line across as many lines as necessary?
_______________________________________________
Mailing list: https://launchpad.net/~bit-team
Post to : bit-team@lists.launchpad.net
Unsubscribe : https://launchpad.net/~bit-team
More help : https://help.launchpad.net/ListHelp
