08-10-2006
when I do the execute ls -l command I get the long listing of the files/dir
what I am after is how to get the ctime,mtime and atime for a file.
/home/den/sedscripts> ls -lc
total 48
-rwxrwxrwx 1 dhawalen ccm_scd 23 Aug 10 10:17 ouput
-rwxrwxrwx 1 dhawalen ccm_scd 147 Aug 10 10:27 sedscript
-rwxrwxrwx 1 dhawalen ccm_scd 134 Aug 10 10:17 testdata
is there any way to find out the same.
also if I want to know why year file in created how would I know tht as above dosent say any thing about year ??
10 More Discussions You Might Find Interesting
1. UNIX for Dummies Questions & Answers
:D i have a slight problem and would appreciate if someone could clarify the confusion.. i use find alot and so far i have done ok.. but it just struck me a couple of days ago that I am not quite sure what the difference between the modification time and the change time as in ctime and mtime and... (3 Replies)
Discussion started by: moxxx68
3 Replies
2. 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
3. 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
4. UNIX for Dummies Questions & Answers
Hi
I've made some test with perl script to learn more about mtime...
So, my question is :
Why the mtime from findfind /usr/local/sbin -ctime -1 -mtime -1 \( -name "*.log" -o -name "*.gz" \) -print are not the same as mtime from unix/linux in ls -ltr or in stat() function in perl : stat -... (2 Replies)
Discussion started by: hiddenshadow
2 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. UNIX for Advanced & Expert Users
Hi,
ctime is the inode change time. If reading a file, its atime will be updated, which should cause inode member i_atime changed, which is an inode change. So ctime should also be updated. But if I try to ls a directory on redhat, only the directory atime gets updated, not ctime. Why?
THANKS! (2 Replies)
Discussion started by: password636
2 Replies
7. Shell Programming and Scripting
I know that find -ctime +1 will find ALL files that have been modified
that are greater than 1 day old and -ctime 1 will find files that are
ONLY 1 day old -ctime -1 mean files that are less than a day old?
Can find actually use this granularity? (5 Replies)
Discussion started by: BeefStu
5 Replies
8. UNIX for Dummies Questions & Answers
commands ls -l or just l displays ctime (changed time) or mtime (modified time)? (10 Replies)
Discussion started by: rupeshkp728
10 Replies
9. Shell Programming and Scripting
The problem is this one. I tar and gzip files on remote server
Code:
find . -ctime -1 | tar -cvf transfer_dmz_start_daily.tar *${Today}*.*;
Command
Code:
find . -ctime -1
Doesn't find files without extension
Code:
.csv .txt
I have to collect all files for current... (1 Reply)
Discussion started by: digioleg54
1 Replies
10. Shell Programming and Scripting
The problem is this one. I tar and gzip files on remote server
find . -ctime -1 | tar -cvf transfer_dmz_start_daily.tar *${Today}*.*;
Command
find . -ctime -1
Doesn't find files without extension
.csv .txt
I have to collect all files for current day, when the program... (1 Reply)
Discussion started by: digioleg54
1 Replies
LEARN ABOUT OPENDARWIN
mkdir
MKDIR(1) BSD General Commands Manual MKDIR(1)
NAME
mkdir -- make directories
SYNOPSIS
mkdir [-pv] [-m mode] directory_name ...
DESCRIPTION
The mkdir utility creates the directories named as operands, in the order specified, using mode rwxrwxrwx (0777) as modified by the current
umask(2).
The options are as follows:
-m mode
Set the file permission bits of the final created directory to the specified mode. The mode argument can be in any of the formats
specified to the chmod(1) command. If a symbolic mode is specified, the operation characters ``+'' and ``-'' are interpreted rela-
tive to an initial mode of ``a=rwx''.
-p Create intermediate directories as required. If this option is not specified, the full path prefix of each operand must already
exist. On the other hand, with this option specified, no error will be reported if a directory given as an operand already exists.
Intermediate directories are created with permission bits of rwxrwxrwx (0777) as modified by the current umask, plus write and search
permission for the owner.
-v Be verbose when creating directories, listing them as they are created.
The user must have write permission in the parent directory.
DIAGNOSTICS
The mkdir utility exits 0 on success, and >0 if an error occurs.
SEE ALSO
rmdir(1)
COMPATIBILITY
The -v option is non-standard and its use in scripts is not recommended.
STANDARDS
The mkdir utility is expected to be IEEE Std 1003.2 (``POSIX.2'') compatible.
HISTORY
A mkdir command appeared in Version 1 AT&T UNIX.
BSD
January 25, 1994 BSD