11-29-2011
inodes are data about a file in a given filesystem. What is stored in an inode is system dependent, there is no standard.
POSIX compliant systems specifically update ctime (where ever it is kept) only with a change involving:
1. file creation
2. file permissions
3. acl changes
Otherwise ctime would have no meaning because it would be identical to atime. Every read access would update the file status time as well as the access time
Check out the utime() call on your system, or google for 'opengroup.org: utime'. utime() does update ctime.
9 More Discussions You Might Find Interesting
1. UNIX for Dummies Questions & Answers
i have used all forms of the unix find command.. and right now this is the only command i can think of that might have this option..:
if i use mtime i am looking at a time interval.. but if i wanted to find out intervals of access, change and modification according to when a file changed size... (4 Replies)
Discussion started by: moxxx68
4 Replies
2. Tips and Tutorials
Unix keeps 3 timestamps for each file: mtime, ctime, and atime. Most people seem to understand atime (access time), it is when the file was last read. There does seem to be some confusion between mtime and ctime though. ctime is the inode change time while mtime is the file modification time. ... (2 Replies)
Discussion started by: Perderabo
2 Replies
3. Shell Programming and Scripting
Hello,
I read and search through this wonderful forum and tried different approaches but it seems I lack some knowledge and neurones ^^
Here is what I'm trying to achieve :
file1:
test filea 3495;
test fileb 4578;
test filec 7689;
test filey 9978;
test filez 12300;
file2:
test filea... (11 Replies)
Discussion started by: mecano
11 Replies
4. Shell Programming and Scripting
Can any one tell me how to find out ctime , mtime ,atime for a file/directory on unix.
Cheers,
Nilesh (5 Replies)
Discussion started by: nilesrex
5 Replies
5. UNIX for Advanced & Expert Users
hi, in trying to maintain your directories, one needs to do some housekeeping like removing old files. the tool "find" comes in handy. but how would you decide which option to use when it comes to, say, deleting files that are older than 5 days?
mtime - last modified
atime - last accessed... (4 Replies)
Discussion started by: pinoy43v3r
4 Replies
6. Shell Programming and Scripting
Hello guys,
I could use advise from more experienced guys about my Makefile. In short, the problem with my Makefile is that $< doesnt change
inside my rule.
Here is my Makefile:
# Makefile for CORE
CC = gcc.exe
AS = as.exe
AR = ar.exe
INCLUDE = \
-I../lib/tomcrypt/inc \... (1 Reply)
Discussion started by: Kodreanu
1 Replies
7. UNIX for Dummies Questions & Answers
I need to sort through a volume that contains video files by access time and delete files that have not been accessed over x days. I have to use the access time as video files are originals that do not get modified, just read
Testing commands on a local test folder...
$ date
Wed Sep 28... (10 Replies)
Discussion started by: canon273
10 Replies
8. AIX
Hello.
An update of TL from TL7 to TL8 is ending with errors :
Requisite Failures
------------------
SELECTED FILESETS: The following is a list of filesets that you asked to
install. They cannot be installed until all of their requisite filesets
are also installed. See subsequent... (4 Replies)
Discussion started by: stephnane
4 Replies
9. Solaris
It is widely documented that on zfs atime updates the access time on zfs.
Where is the access time updated on Solaris 11.2?
If I create file atimetest.txt under rpool/export/home:
# zfs list rpool/export/home
NAME USED AVAIL REFER MOUNTPOINT
rpool/export/home 13.3G ... (5 Replies)
Discussion started by: jabberwocky
5 Replies
LEARN ABOUT DEBIAN
explain_utime_or_die
explain_utime_or_die(3) Library Functions Manual explain_utime_or_die(3)
NAME
explain_utime_or_die - change file times and report errors
SYNOPSIS
#include <libexplain/utime.h>
void explain_utime_or_die(const char *pathname, const struct utimbuf *times);
DESCRIPTION
The explain_utime_or_die function is used to call the utime(2) system call. On failure an explanation will be printed to stderr, obtained
from explain_utime(3), and then the process terminates by calling exit(EXIT_FAILURE).
This function is intended to be used in a fashion similar to the following example:
explain_utime_or_die(pathname, times);
pathname
The pathname, exactly as to be passed to the utime(2) system call.
times The times, exactly as to be passed to the utime(2) system call.
Returns:
This function only returns on success. On failure, prints an explanation and exits.
SEE ALSO
utime(2)
change file last access and modification times
explain_utime(3)
explain utime(2) errors
exit(2) terminate the calling process
COPYRIGHT
libexplain version 0.52
Copyright (C) 2008 Peter Miller
explain_utime_or_die(3)