Sponsored Content
Top Forums Shell Programming and Scripting how to find ot ctime , mtime ,atime Post 302084312 by nilesrex on Thursday 10th of August 2006 10:51:17 AM
Old 08-10-2006
Thanks mate.

One of those days where head is buzzing offf....!!!!!! Smilie
 

10 More Discussions You Might Find Interesting

1. UNIX for Dummies Questions & Answers

mtime vs ctime

: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

atime, ctime, mtime somewhere along csize..

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

mtime, ctime, and atime

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

(find) mtime vs. (unix) mtime

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

mtime VS atime VS ctime

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

Why updating atime doesn't update ctime?

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

find -ctime

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

Ls -l displays ctime or mtime?

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

find -ctime -1 cannot find files without extention

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

find -ctime -1 cannot find files without extention

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
NNGOBACK(1)						      General Commands Manual						       NNGOBACK(1)

NAME
nngoback - make news articles unread on a day-by-day basis (nn) SYNOPSIS
nngoback [ -NQvi ] [-d] days [ group ]... DESCRIPTION
nngoback will rewind the .newsrc record file of nn(1) one or more days. It can be used to rewind all groups, or only a specified set of groups. In other words, nngoback can mark news articles which have arrived on the system during the last days days unread. Only subscribed groups that occur in the current presentation sequence are rewound. That means that if no group arguments are specified, all groups occurring in the sequence defined in the init file will be rewound. Otherwise, only the groups specified on the argument line will be rewound. When a group is rewound, the information about selections, partially read digests etc. are discarded. It will print notifications about this unless the -Q (quiet) option is used. If the -i (interactive) option is specified, nngoback will report for each how many articles can be marked unread, and ask for confirmation before going back in that group. If the -v (verbose) option is specified, nngoback will report how many articles are marked unread. If the -N (no-update) option is specified, nngoback will perform the entire goback operation, but not update the .newsrc file. If you are not up-to-date with your news reading, you can also use nngoback to catch up to only have the last few days of news waiting to be read in the following way: nn -a0 nngoback 3 The nn command will mark all articles in all groups as read (answer all to the catch-up question.) The following nngoback will then make the last three days of news unread again. Examples: nngoback 0 Mark the articles which have arrived today as unread. nngoback 1 Mark the articles which have arrived yesterday and today as unread. nngoback 6 Mark the articles which have arrived during the last week as unread. You cannot go more than 14 days back with nngoback. (You can change this limit as described below.) THE BACK_ACT DAEMON It is a prerequisite for the use of nngoback that the script back_act is executed at an appropriate time once (and only once) every day. Preferably this is done by cron right before the bacth of news for `today' is received. back_act will maintain copies of the active file for the last 14 days. Optionally, the back_act program accepts a single numerical argument specifying how many copies of the active file it should maintain. This is useful if news is expired after 7 days, in which case keeping more than 7 days of active file copies is wasteful. FILES
~/.newsrc The record of read articles. ~/.newsrc.goback The original rc file before goback. $db/active.N The N days `old' active file. $master/back_act Script run by cron to maintain old active files. SEE ALSO
nn(1), nncheck(1), nngrab(1), nngrep(1), nnpost(1), nntidy(1) nnadmin(1M), nnusage(1M), nnmaster(8) NOTES
nngoback does not check the age of the `old' active files; it will blindly believe that active.0 was created today, and that active.7 is really seven days old! Therefore, the back_act script should be run once and only once every day for nngoback to work properly. The days are counted relative to the time the active files were copied. AUTHOR
Kim F. Storm, Texas Instruments A/S, Denmark E-mail: storm@texas.dk 4th Berkeley Distribution Release 6.6 NNGOBACK(1)
All times are GMT -4. The time now is 12:49 PM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy