On Wed, 2021-06-16 at 16:44 +, Peter Heiner wrote:
>
> > On Tue, 2021-06-15 at 08:42 +, Peter Heiner wrote:
> > > > $ file as-log.out
> > > > as-log.out: data
> > > This looks like the file utility was unable to determine the type
> > > of
> > > as-log.out. As it should normally be able
Hi Peter,
On Tue, 2021-06-15 at 08:42 +, Peter Heiner wrote:
> > $ file as-log.out
> > as-log.out: data
> This looks like the file utility was unable to determine the type of
> as-log.out. As it should normally be able to identify all types emitted
> by logrotate, this suggests to me that the
> On Tue, 2021-06-15 at 08:42 +, Peter Heiner wrote:
> > > $ file as-log.out
> > > as-log.out: data
> > This looks like the file utility was unable to determine the type of
> > as-log.out. As it should normally be able to identify all types emitted
> > by logrotate, this suggests to me that
$ file as-log.out
as-log.out: data
This looks like the file utility was unable to determine the type of
as-log.out. As it should normally be able to identify all types emitted by
logrotate, this suggests to me that the actual file it was ran on is corrupt.
archivesspace/logs/archivesspace.out {
2021 3:00 PM
To: archivesspace_users_group@lyralists.lyrasis.org
Subject: [Archivesspace_Users_Group] logrotate and "binary" logs
Hi all -
I recently setup logrotate according to the helpful blurb in the tech-
docs[1], which has been great for our disk usage but seems to have
introduced
