From: Colin Booth <colin@heliocat.net>
To: supervision@list.skarnet.org
Subject: Re: s6-log run xz compression processor on .u files
Date: Fri, 23 Feb 2018 19:50:03 +0000 [thread overview]
Message-ID: <20180223195003.2cj2evylcfsnbk2o@cathexis.xen.prgmr.com> (raw)
In-Reply-To: <CAGi2YbGv=G-Hon_jz=rYPmzj8-BGcBgwHF=f4ztEFRqX86=2Fg@mail.gmail.com>
On Fri, Feb 23, 2018 at 09:40:37AM -0700, Brad Grissom wrote:
> Hi I'd like to re-run my xz compression processor on .u files, maybe during
> the next rotation. My problem is that I'm running an embedded Linux system
> and it gets unplugged all the time, so I end up with .u log files that are
> uncompressed by the s6-log processor.
>
> I am using this to log:
>
> s6-log -b n30 s5242880 S15728640 !xz /appdata
>
> This is an issue because I have limited flash storage space and would love
> to be able to store as many (compressed) logs as possible. I figure I must
> be missing something because this is probably a common occurrence for many
> people.
>
> If anybody has any ideas, I would love to hear it! Thanks!
Lots of ways to fix this. If you have a cron-alike, an @reboot trigger
can do it:
@reboot sleep SOMEPERIOD find /path/to/dirs -name '*.u' -exec xz "{}" \;
If you don't mind polling, something similar but as an s6 service works,
though you can use s6-pause from s6-portable-utils to stop it from
refiring (and as such no longer polling). If you don't have that, a
finish script that puts the service down works, but that's kinda ugly.
>
> ~~Brad Grissom
Cheers!
--
Colin Booth
prev parent reply other threads:[~2018-02-23 19:50 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-02-23 16:40 Brad Grissom
2018-02-23 19:50 ` Colin Booth [this message]
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=20180223195003.2cj2evylcfsnbk2o@cathexis.xen.prgmr.com \
--to=colin@heliocat.net \
--cc=supervision@list.skarnet.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).