public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Norbert van Nobelen <Norbert@edusupport.nl>
To: linux-kernel@vger.kernel.org
Subject: Time of process changes to earlier time in process list
Date: 26 Aug 2004 09:52:07 +0200	[thread overview]
Message-ID: <1093506726.2331.34.camel@linux.local> (raw)

Hello,

I did two times a 'ps -ef' on a red hat machine. The strange part was
that the time of the following process changed to the past:
First 'ps -ef':
root     14527   902  0 07:17 ?        00:00:00 CROND
root     14529 14527  0 07:17 ?        00:00:00 /bin/sh -c
/root/runtracker.sh >/dev/null
root     14531 14529  0 07:17 ?        00:00:00 /bin/sh -c
/root/runtracker.sh >/dev/null
root     14533 14531  5 07:17 ?        00:00:00 /usr/local/php5/bin/php
/misc/tracker/track.php
root     14536 14423  0 07:17 pts/0    00:00:00 ps -ef

The second process list:
root     14527   902  0 07:16 ?        00:00:00 CROND
root     14529 14527  0 07:16 ?        00:00:00 /bin/sh -c
/root/runtracker.sh >/dev/null
root     14531 14529  0 07:16 ?        00:00:00 /bin/sh -c
/root/runtracker.sh >/dev/null
root     14533 14531  2 07:16 ?        00:00:00 /usr/local/php5/bin/php
/misc/tracker/track.php
root     14537 14423  0 07:17 pts/0    00:00:00 ps -ef

Has anyone observed this behaviour before?

Is it behaviour of the kernel or of the 'ps' program?

Can it cause problems in anyway? (I don't know if the starttime
registration does have any important value in the kernel or not)

Other relevant system info:
/proc/version
Linux version 2.4.18-3smp (bhcompile@daffy.perf.redhat.com) (gcc version
2.96 20000731 (Red Hat Linux 7.3 2.96-110)) #1 SMP Thu Apr 18 07:27:31
EDT 2002

2 cpus:
processor       : 0
vendor_id       : GenuineIntel
cpu family      : 6
model           : 8
model name      : Pentium III (Coppermine)
stepping        : 6
cpu MHz         : 996.894
cache size      : 256 KB
fdiv_bug        : no
hlt_bug         : no
f00f_bug        : no
coma_bug        : no
fpu             : yes
fpu_exception   : yes
cpuid level     : 2
wp              : yes
flags           : fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge
mca cmov pat pse36 mmx fxsr sse
bogomips        : 1985.74

processor       : 1
vendor_id       : GenuineIntel
cpu family      : 6
model           : 8
model name      : Pentium III (Coppermine)
stepping        : 6
cpu MHz         : 996.894
cache size      : 256 KB
fdiv_bug        : no
hlt_bug         : no
f00f_bug        : no
coma_bug        : no
fpu             : yes
fpu_exception   : yes
cpuid level     : 2
wp              : yes
flags           : fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge
mca cmov pat pse36 mmx fxsr sse
bogomips        : 1992.29

Best regards,

Norbert van Nobelen



-- 
Met vriendelijke groet,

Norbert van Nobelen
EduSupport

Postbus 95963
2509CZ Den Haag
T: 070-3280200
M: 06-43036586
F: 070-3280029
E: Norbert@edusupport.nl
I: www.edusupport.nl
B: ABN AMRO
R: 47.38.00.411


             reply	other threads:[~2004-08-26  7:51 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-08-26  7:52 Norbert van Nobelen [this message]
2004-08-26 18:35 ` Time of process changes to earlier time in process list Lee Revell

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=1093506726.2331.34.camel@linux.local \
    --to=norbert@edusupport.nl \
    --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