From owner-freebsd-bugs Mon Mar 18 23:00:03 1996 Return-Path: owner-bugs Received: (from root@localhost) by freefall.freebsd.org (8.7.3/8.7.3) id XAA10936 for bugs-outgoing; Mon, 18 Mar 1996 23:00:03 -0800 (PST) Received: (from gnats@localhost) by freefall.freebsd.org (8.7.3/8.7.3) id XAA10900 Mon, 18 Mar 1996 23:00:01 -0800 (PST) Date: Mon, 18 Mar 1996 23:00:01 -0800 (PST) Message-Id: <199603190700.XAA10900@freefall.freebsd.org> To: freebsd-bugs Cc: From: Bruce Evans Subject: Re: docs/1089: stat manpage unclear about st_mtime & friends Reply-To: Bruce Evans Sender: owner-bugs@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk The following reply was made to PR docs/1089; it has been noted by GNATS. From: Bruce Evans To: FreeBSD-gnats-submit@freebsd.org, msmith@atrad.adelaide.edu.au Cc: Subject: Re: docs/1089: stat manpage unclear about st_mtime & friends Date: Tue, 19 Mar 1996 17:49:06 +1100 >Consider this portion of the stat(2) manapage (trimmed): > struct stat { > ... > struct timespec st_atimespec; /* time of last access */ > ... The man page was apparently once copied from stat.h. Bits have rotted. There are now ordinary st_atime etc. fields for the _POSIX_SOURCE case. > The time-related fields of struct stat are as follows: > st_atime Time when file data last accessed. Changed by the mknod(2), > ... >It should be mentioned that the names 'st_atime' 'st_mtime' and 'st_ctime' >are compatability macros which referece the ts_sec fields in the timespec >structs for each of the three. Should it? This is an implementation detail, and the implementation is different for the _POSIX_SOURCE case. Bruce