From: Jari Aalto <jari.aalto@cante.net>
To: cygwin-apps@cygwin.com
Subject: ITP: flog -- File logger to read stdin and write to a file
Date: Wed, 26 Sep 2012 22:42:00 -0000 [thread overview]
Message-ID: <87k3vgs8x0.fsf@picasso.cante.net> (raw)
wget --recursive --no-host-directories --cut-dirs=3 \
http://cante.net/~jaalto/tmp/cygwin/flog/flog-1.8-1-src.tar.bz2 \
http://cante.net/~jaalto/tmp/cygwin/flog/flog-1.8-1.tar.bz2 \
http://cante.net/~jaalto/tmp/cygwin/flog/setup.hint
Included in Debian:
http://packages.debian.org/flog
To check packaging:
tar -xf *-src.tar.bz2
./*.sh --color --verbose all
Jari
[ setup.hint ]
sdesc: "File logger to read stdin and write to a file"
ldesc: "If SIGHUP is received, the file will be reopened, allowing for
log rotation. The log file will only be reopened if flog detects that
rotation has occurred; i.e. old file gone or inode changed. The
program itself is extremly small."
category: Utils
requires: cgwin
next reply other threads:[~2012-09-26 22:42 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-09-26 22:42 Jari Aalto [this message]
2012-10-20 19:34 ` marco atzeri
2012-10-20 19:59 ` RFU: flog -- File logger to read stdin and write to a file (new, GTG) Jari Aalto
2012-10-20 22:48 ` Christopher Faylor
2012-10-20 22:49 ` Christopher Faylor
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=87k3vgs8x0.fsf@picasso.cante.net \
--to=jari.aalto@cante.net \
--cc=cygwin-apps@cygwin.com \
/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 read-only IMAP folder(s) and NNTP newsgroup(s).