From: Athanasius <link@miggy.org>
To: Reg Clemens <reg@dwf.com>, linux-kernel <linux-kernel@vger.kernel.org>
Subject: Re: Confused: 'tail -f' how can this happen???
Date: Mon, 28 Jul 2008 11:52:22 +0100 [thread overview]
Message-ID: <20080728105222.GB17871@miggy.org> (raw)
In-Reply-To: <200807252137.m6PLbAkj008998@deneb.dwf.com>
On Fri, Jul 25, 2008 at 03:37:10PM -0600, Reg Clemens wrote:
> OK, I dont understand this at all.
> I was debugging another problem, and had a 'tail -f' running on my maillog
> file.
> It showed data down to the present, namely 15:18:18
What date ?
> Something had gone by fast enough that I brought the maillog up in an editor
> but IT only showed data down to 14:02:16
And what date here ?
> Looking at the 'ls' of /var/log, the maillog file shows a write date of 14:02.
>
> If I do a 2nd tail -f, it too stops at 14:02.
And here ?
> What is going on with the file system to cause the bizare behaviour?
> Why cant I see ALL the data in maillog, or why could I see it only once?
>
> Confused.
I'm hoping this is as simple as:
1) You opened the initial tail on one day and left it running
2) Log rotation happens, mail software, via syslog or directly,
starts logging to the new 'maillog', the other one now being
'maillog.1' or whatever
3) You don't realise this and get confused by the differing data
when you look afresh at what is now 'maillog'
And of course, depending on local configuration, maybe your maillog
rotates more often than once a day (although that alone wouldn't explain
the 'gone backwards' timestamp).
HTH,
-Ath
--
- Athanasius = Athanasius(at)miggy.org / http://www.miggy.org/
Finger athan(at)fysh.org for PGP key
"And it's me who is my enemy. Me who beats me up.
Me who makes the monsters. Me who strips my confidence." Paula Cole - ME
prev parent reply other threads:[~2008-07-28 10:52 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-07-25 21:37 Reg Clemens
2008-07-28 10:52 ` Athanasius [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=20080728105222.GB17871@miggy.org \
--to=link@miggy.org \
--cc=linux-kernel@vger.kernel.org \
--cc=reg@dwf.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
all inboxes | Powered by JetHome®