All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Ángel González" <ingenit@zoho.com>
To: Ruediger Meier <sweet_f_a@gmx.de>
Cc: "Pádraig Brady" <P@draigbrady.com>, util-linux@vger.kernel.org
Subject: Re: tailf, really needed?
Date: Fri, 13 Mar 2015 21:22:18 +0100	[thread overview]
Message-ID: <550346FA.3060006@zoho.com> (raw)
In-Reply-To: <201503131402.30431.sweet_f_a@gmx.de>

On 13/03/15 14:02, Ruediger Meier wrote:
> BTW I think there could be a minor improvement for coreutils tail for
> the cases "file is empty" or "-n 0". Maybe we could skip opening the
> file one time at the beginning. So that "tail -n0 -f logfile" would
> really never access the file unless it grows.
>
> cu,
> Rudi

I suspect that might break filesystems lying about the file size, such 
as proc or some compressed fs. There may also be issues with some 
network fs.

A tail <file> with <file> of len 0, would usually be empty. However, it 
would be a problem not to provide an output for tail /proc/$$/status



PS: tail -f already acts a bit funny in that case, as it tails the end 
of the file, then thinks it has been truncated and shows it in full.


  parent reply	other threads:[~2015-03-13 20:37 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-03-13  9:00 tailf, really needed? Ruediger Meier
2015-03-13  9:32 ` Sami Kerola
2015-03-13 11:37 ` Pádraig Brady
2015-03-13 13:02   ` Ruediger Meier
2015-03-13 13:35     ` Pádraig Brady
2015-03-13 14:02       ` Ruediger Meier
2015-03-13 20:22     ` Ángel González [this message]
2015-03-14  4:50   ` Peter Cordes

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=550346FA.3060006@zoho.com \
    --to=ingenit@zoho.com \
    --cc=P@draigbrady.com \
    --cc=sweet_f_a@gmx.de \
    --cc=util-linux@vger.kernel.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.