From: "George Georgalis" <george@galis.org>
Subject: Re: monitoring svlogd-produced logfiles
Date: Fri, 16 Jun 2006 07:03:03 -0400 [thread overview]
Message-ID: <20060616110303.GB4804@run.galis.org> (raw)
In-Reply-To: <20060614234004.GH8706@home.power>
On Thu, Jun 15, 2006 at 02:40:04AM +0300, Alex Efros wrote:
>
>Tail can follow ./current after rotate:
> tail -F
>
Unfortunatly that is not universal...
I use a few different alias in my bourne profile
OS=$(uname)
case $OS in
NetBSD|FreeBSD|Dragonfly|Darwin)
alias t='tail -F'
;;
Linux)
alias t='tail --follow=name'
;;
OpenBSD)
alias t='tail -f'
;;
esac
Cheers,
// George
--
George Georgalis, systems architect, administrator <IXOYE><
http://galis.org/ cell:646-331-2027 mailto:george@galis.org
next prev parent reply other threads:[~2006-06-16 11:03 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-06-14 23:35 Vincent Danen
2006-06-14 23:40 ` Alex Efros
2006-06-16 11:03 ` George Georgalis [this message]
2006-06-16 11:08 ` Alex Efros
2006-06-16 13:18 ` George Georgalis
2006-06-16 19:08 ` Vincent Danen
2006-06-18 2:48 ` George Georgalis
2006-06-18 2:57 ` Alex Efros
2006-06-14 23:59 ` Alex Efros
2006-06-15 0:10 ` Vincent Danen
2006-06-15 0:25 ` Alex Efros
2006-06-15 3:32 ` Vincent Danen
2006-06-15 16:32 ` Vincent Danen
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=20060616110303.GB4804@run.galis.org \
--to=george@galis.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).