Updated 17 May 2007 Aardvark Summary Table ______________________ ERN 1 Accept ERN 2 Accept ERN 3 Accept ERN 4 Reject ERN 5 Accept ERN 6 Accept as marked ERN 7 Accept as marked _____________________________________________________________________________ OBJECTION Enhancement Request Number 1 nick:xxxxxxxxxx Fine grain timestamp updates (rdvk# 1) _____________________________________________________________________________ Accept_X___ Accept as marked below_____ Duplicate_____ Reject_____ Rationale for rejected or partial changes: _____________________________________________________________________________ Page: 4 Line: 126-127 Section: 1.7.1.4 Problem: Fine Grain timestamp updates Action: Change from: The st_atime, st_ctime, and st_mtime fields of the file shall be updated as specified in the System Interfaces volume of IEEE Std 1003.1-200x, Section 2.5, Standard I/O Streams. to: The last data access, last data modification and last file status change timestamps of the file shall be updated as specified in the Base Definitions volume of IEEE Std 1003.1-200x, Section 4.8, File Times Update. _____________________________________________________________________________ OBJECTION Enhancement Request Number 2 nick:xxxxxxxxxx Fine grain timestamp updates (rdvk# 2) _____________________________________________________________________________ Accept_X___ Accept as marked below_____ Duplicate_____ Reject_____ Rationale for rejected or partial changes: _____________________________________________________________________________ Page: 5 Line: 169 Section: 1.7.1.4 Problem: Fine Grain timestamp updates Action: Change from: 3. The st_ctime and st_mtime fields shall be marked for update to 3. The last data modification and last file status change timestamps shall be marked for update _____________________________________________________________________________ OBJECTION Enhancement Request Number 3 nick:xxxxxxxxxx Fine grain timestamp updates (rdvk# 3) _____________________________________________________________________________ Accept_X___ Accept as marked below_____ Duplicate_____ Reject_____ Rationale for rejected or partial changes: _____________________________________________________________________________ Page: 6 Line: 199-201 Section: 1.7.1.5 Problem: Fine Grain timestamp updates Action: Change from: b. If the link count is not reduced to zero, the st_ctime field shall be marked for update. 6. The st_ctime and st_mtime fields of the containing directory shall be marked for update. to: b. If the link count is not reduced to zero, the last file status change timestamp shall be marked for update. 6. The last data modification and last file status change timestamps of the containing directory shall be marked for update. _____________________________________________________________________________ OBJECTION Enhancement Request Number 4 nick:xxxxxxxxxx Fine grain timestamp updates (rdvk# 4) _____________________________________________________________________________ Accept_____ Accept as marked below_____ Duplicate_____ Reject_X___ Rationale for rejected or partial changes: Only seconds are permitted in this instance _____________________________________________________________________________ Page: 139 Line: 5273 Section: ar Problem: Fine Grain timestamp updates Action: Change from: The modification time is the file st_mtime field. to: The modification time is the last data modificaction timestamp. _____________________________________________________________________________ OBJECTION Enhancement Request Number 5 nick:xxxxxxxxxx Fine grain timestamp updates (rdvk# 5) _____________________________________________________________________________ Accept_X___ Accept as marked below_____ Duplicate_____ Reject_____ Rationale for rejected or partial changes: _____________________________________________________________________________ Page: 659 Line: 25898-25900 Section: mv Problem: Fine Grain timestamp updates Action: Change from: Some implementations mark for update the st_ctime field of renamed files and some do not. Applications which make use of the st_ctime field may behave differently with respect to renamed files unless they are designed to allow for either behavior. to: Some implementations mark for update the last file status change timestamp of renamed files and some do not. Applications which make use of the last file status change timestamp may behave differently with respect to renamed files unless they are designed to allow for either behavior. _____________________________________________________________________________ OBJECTION Enhancement Request Number 6 nick:xxxxxxxxxx Fine grain timestamp updates (rdvk# 6) _____________________________________________________________________________ Accept_____ Accept as marked below_X___ Duplicate_____ Reject_____ Rationale for rejected or partial changes: Change 1st paragraph of the touch DESCRIPTION from: The touch utility shall change the modification times, access times, or both of files. The modification time shall be equivalent to the value of the st_mtime member of the stat structure for a file, as described in the System Interfaces volume of IEEE Std 1003.1-200x; the access time shall be equivalent to the value of st_atime. To: The touch utility shall change the last data modification timestamps, the last data access timestamps, or both of files. _____________________________________________________________________________ Page: 921 Line: 36329-36332 Section: touch Problem: Fine Grain timestamp updates Action: Change from: The modification time shall be equivalent to the value of the st_mtime member of the stat structure for a file, as described in the System Interfaces volume of IEEE Std 1003.1-200x; the access time shall be equivalent to the value of st_atime. to: The modification time shall be equivalent to the value of the st_mtim member of the stat structure for a file, as described in the System Interfaces volume of IEEE Std 1003.1-200x; the access time shall be equivalent to the value of st_atim. _____________________________________________________________________________ OBJECTION Enhancement Request Number 7 nick:xxxxxxxxxx Fine grain timestamp updates (rdvk# 7) _____________________________________________________________________________ Accept_____ Accept as marked below_X___ Duplicate_____ Reject_____ Rationale for rejected or partial changes: Change from: 1. If file does not exist, a creat( ) function call is made with the file operand used as the path argument and the value of the bitwise-inclusive OR of S_IRUSR, S_IWUSR, S_IRGRP, S_IWGRP, S_IROTH, and S_IWOTH used as the mode argument. 2. The utime( ) function is called with the following arguments: a. The file operand is used as the path argument. b. The utimbuf structure members actime and modtime are determined as described in the OPTIONS section. to: 1. If file does not exist: a. the creat( ) function is called with the following arguments: - the file operand is used as the path argument - the value of the bitwise-inclusive OR of S_IRUSR, S_IWUSR, S_IRGRP, S_IWGRP, S_IROTH and S_IWOTH is used as the mode argument. b. the futimens() function is called with the following arguments: - the file descriptor opened in step 1a - the access time and the modification time, set as described in the OPTIONS section, are used as the first and second elements of the times array argument respectively. (cathy check what you want for the sublist - or i. ii..) 2. If /file/ exists, the utimensat( ) function is called with the following arguments: a. the AT_FDCWD special value is used as the fd argument b. the file operand is used as the path argument c. the access time and the modification time, set as described in the OPTIONS section, are used as the first and second elements of the times array argument respectively. d. the /flag/ argument set to zero [ Note mail seq 10330 has been applied ] _____________________________________________________________________________ Page: 921 Line: 36343-36346 Section: touch Problem: Fine Grain timestamp updates Action: Change from: 2. The utime( ) function is called with the following arguments: a. The file operand is used as the path argument. b. The utimbuf structure members actime and modtime are determined as described in the OPTIONS section. to: 2. The utimensat( ) function is called with the following arguments: a. the AT_FDCWD special value is used as the fd argument b. the file operand is used as the path argument c. the access time and the modification time, set as described in the OPTIONS section, are used as the first and second elements of the times array argument respectively. [ Note mail seq 10330 has been applied ]