You shouldn't need to do that if you're running systemd. Everything is
written to the journal. Just do journalctl --since=today and you'll get
everything since midnight. You really don't need the text logs at all.
On 10/20/22 18:28, Kenneth Porter wrote:
On 10/20/2022 6:52 AM, G.W. Haywood
I haven't found a good explanation of how the /media mount system works.
It seems that mechanism changes frequently.
For my CentOS 7 system with a USB external drive for backups, I use
systemd mount units to mount the drive when anything tries to touch
/var/lib/BackupPC. I'd suggest doing
On 10/20/2022 6:52 AM, G.W. Haywood via BackupPC-users wrote:
I checked in the syslog and I can't see any other log files that it
might be using.
You can spend hours trawling through logs, but mostly I'd search in
/var/log/(daemon.log|debug|kern.log|messages|syslog) - not necessarily
in that
Adam Hardy wrote at about 22:25:31 +0100 on Thursday, October 20, 2022:
> Looking through those logs for anything at the time of the modification
> timestamp on the backuppc xferlog, I can see this one line which
> appears about 25 mins after the backup fails:
>
>Oct 17 16:13:48
-Original Message-
> Be careful with smartctl if you use it for anything other than
> reading
> information from the drive. Heed the warnings in the 'man' page, and
> before you do anything like setting or changing drive characteristics
> search online for reports from people who've done
Hello again,
On Thu, 20 Oct 2022, Adam Hardy wrote:
I scanned the problem USB drive with smartctl and with
gnome-utilities and it logged nothing.?
Be careful with smartctl if you use it for anything other than reading
information from the drive. Heed the warnings in the 'man' page, and
-Original Message-
> Don't assume what the problem is and try to solve it. First find it.
> There may be something interesting in the system logs (in /var/log/).
>
> Your subject line says "tar causing problems" but I feel sure it
> won't
> be tar which is causing the problems. I also
