From owner-freebsd-bugs  Wed Apr 16 05:40:07 1997
Return-Path: <owner-bugs>
Received: (from root@localhost)
          by freefall.freebsd.org (8.8.5/8.8.5) id FAA24634
          for bugs-outgoing; Wed, 16 Apr 1997 05:40:07 -0700 (PDT)
Received: (from gnats@localhost)
          by freefall.freebsd.org (8.8.5/8.8.5) id FAA24623;
          Wed, 16 Apr 1997 05:40:05 -0700 (PDT)
Date: Wed, 16 Apr 1997 05:40:05 -0700 (PDT)
Message-Id: <199704161240.FAA24623@freefall.freebsd.org>
To: freebsd-bugs
Cc: 
From: Martin Kammerhofer <mkamm@icg.tu-graz.ac.at>
Subject: Re: kern/3267: mtime/ctime sometimes updated when a program is run
Reply-To: Martin Kammerhofer <mkamm@icg.tu-graz.ac.at>
Sender: owner-bugs@FreeBSD.ORG
X-Loop: FreeBSD.org
Precedence: bulk

The following reply was made to PR kern/3267; it has been noted by GNATS.

From: Martin Kammerhofer <mkamm@icg.tu-graz.ac.at>
To: freebsd-gnats-submit@freebsd.org, sigma@pair.com
Cc:  Subject: Re: kern/3267: mtime/ctime sometimes updated when a program is run
Date: Wed, 16 Apr 1997 14:37:41 +0200

 When I was running FreeBSD 2.2-BETA_A I experienced similar problems:
 Modification times of files occassionally changed (to current time,
 i.e. they seemed to have been touched) without apparent reason.
 Since it was reproducable (a Makefile's rules broke consistently due
 to a modified mtime) I tried to track it down.
 The mtime changed during an 'install -c' of a large file (a kernel).
 I ran install under gdb and it was exactly during the *large* read(2)
 call (when install slurps in the source file) when mtimes changed.