From: Steffen Nurpmeso <steffen@sdaoden.eu>
To: John Cowan <cowan@ccil.org>
Cc: The Eunuchs Hysterical Society <tuhs@tuhs.org>
Subject: Re: [TUHS] Binary log files
Date: Mon, 05 Jul 2021 21:25:37 +0200 [thread overview]
Message-ID: <20210705192537.oT7gj%steffen@sdaoden.eu> (raw)
In-Reply-To: <CAD2gp_RLYVFx8CK6PAiSrPV8BvSrYHGiB2WPxQGJO=Bh-x3nRA@mail.gmail.com>
John Cowan wrote in
<CAD2gp_RLYVFx8CK6PAiSrPV8BvSrYHGiB2WPxQGJO=Bh-x3nRA@mail.gmail.com>:
|On Mon, Jul 5, 2021 at 9:42 AM Steffen Nurpmeso <steffen@sdaoden.eu> wrote:
|
|And how did you handle it?
|
|The simplest way to truncate the file is with truncate or just ">file",
|since writes are small enough to be atomic. The sa utility, which also
Hm, ok, sure. I thought maybe, you know. Availability of some
weeks or the quarter of a year is a good thing (tm).
|goes back to v7, will summarize process accounting data and write it to a
|different file; it can then report on either unsummarized data or
|summarized data before unsummarized data). Unfortunately Linux has broken
|the wtmp/utmp convention of "no logfile, no logging", so a cron job to
|truncate wtmp is your only man.
Too bad weather to make something out of that.
The fruits of South Africa were so sweet that we hoped for a good
summer. Well 2000 KM more southern it is, but that Island low
pressure area now lies in front of Ireland i think, what a mess.
Yes the script is not atomic, but good enough for very occasional
usage by a logged in administrator.
--steffen
|
|Der Kragenbaer, The moon bear,
|der holt sich munter he cheerfully and one by one
|einen nach dem anderen runter wa.ks himself off
|(By Robert Gernhardt)
next prev parent reply other threads:[~2021-07-05 19:26 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-07-05 2:53 John Cowan
2021-07-05 13:41 ` Steffen Nurpmeso
2021-07-05 15:12 ` John Cowan
2021-07-05 19:25 ` Steffen Nurpmeso [this message]
2021-07-05 20:26 Norman Wilson
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20210705192537.oT7gj%steffen@sdaoden.eu \
--to=steffen@sdaoden.eu \
--cc=cowan@ccil.org \
--cc=tuhs@tuhs.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).