public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: David Ford <david+challenge-response@blue-labs.org>
To: linux-kernel mailing list <linux-kernel@vger.kernel.org>,
	albert@users.sourceforge.net
Subject: /proc or ps tools bug?  2.6.3, time is off
Date: Tue, 24 Feb 2004 20:58:39 -0500	[thread overview]
Message-ID: <403C014F.2040504@blue-labs.org> (raw)

Kernel 2.6.3, procps 3.2.0

# while [ 1 ]; do (ps aux|grep "grep ps aux" && date) ; sleep 1; done
root     20043  0.0  0.0  1504  456 pts/0    R    20:45   0:00 grep grep 
ps aux
Tue Feb 24 20:45:25 EST 2004
root     20062  0.0  0.0  1504  460 pts/0    S    20:45   0:00 grep grep 
ps aux
Tue Feb 24 20:45:26 EST 2004
root     20081  0.0  0.0  1504  460 pts/0    S    20:46   0:00 grep grep 
ps aux
Tue Feb 24 20:45:27 EST 2004

Note the change in the timestamp as reported by 'ps' v.s. the time 
reported by 'date'.

Repeatable every time at 26 seconds after the minute +/- a portion of a 
second.

David


             reply	other threads:[~2004-02-25  1:59 UTC|newest]

Thread overview: 36+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-02-25  1:58 David Ford [this message]
2004-02-25  1:54 ` /proc or ps tools bug? 2.6.3, time is off Albert Cahalan
2004-02-25  5:10   ` David Ford
2004-02-25  3:27     ` Albert Cahalan
2004-02-25 16:28       ` George Anzinger
2004-02-25 16:04         ` Albert Cahalan
2004-02-25 20:45           ` George Anzinger
2004-02-25 19:16             ` Albert Cahalan
2004-02-25 21:10           ` George Anzinger
2004-02-26  1:52             ` john stultz
2004-02-26 23:06               ` George Anzinger
2004-02-26 23:10                 ` john stultz
2004-02-27  0:20                   ` George Anzinger
2004-04-13 22:38                     ` john stultz
2004-04-13 22:59                       ` George Anzinger
2004-04-14 12:10                       ` Tim Schmielau
2004-04-14 17:03                         ` George Anzinger
2004-04-14 18:28                         ` john stultz
2004-04-15 10:37                           ` Petri Kaukasoina
2004-04-15 11:05                             ` Tim Schmielau
2004-04-15 16:14                               ` Petri Kaukasoina
2004-05-01 13:51                                 ` Tim Schmielau
2004-05-02  1:41                                   ` Andrew Morton
2004-05-02  1:59                                     ` Tim Schmielau
2004-05-04  2:40                                       ` john stultz
2004-05-04  6:12                                         ` Tim Schmielau
2004-05-04 14:59                                           ` john stultz
2004-05-04 16:50                                             ` Tim Schmielau
2004-05-07  0:33                                             ` George Anzinger
2004-05-07  1:21                                               ` john stultz
2004-05-07 20:41                                                 ` George Anzinger
2004-05-07 21:38                                                   ` john stultz
2004-02-26 23:14               ` George Anzinger
2004-02-25  9:14 ` Petri Kaukasoina
2004-02-25  9:18   ` Petri Kaukasoina
2004-02-25 21:39   ` David Ford

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=403C014F.2040504@blue-labs.org \
    --to=david+challenge-response@blue-labs.org \
    --cc=albert@users.sourceforge.net \
    --cc=linux-kernel@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox