08-10-2006
ls -ltr
ls -lutr
ls -lctr
Check MAN page, my dear MAN
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 MINIX
man.conf
MAN.CONF(5) File Formats Manual MAN.CONF(5)
NAME
man.conf - configuration file for man
DESCRIPTION
This is the configuration file for the man(1), apropos(1), and makewhatis(8) utilities. Its presence, and all directives, are optional.
This file is an ASCII text file. Leading whitespace on lines, lines starting with '#', and blank lines are ignored. Words are separated
by whitespace. The first word on each line is the name of a configuration directive.
The following directives are supported:
manpath path
Override the default search path for man(1), apropos(1), and makewhatis(8). It can be used multiple times to specify multiple
paths, with the order determining the manual page search order.
Each path is a tree containing subdirectories whose names consist of the strings 'man' and/or 'cat' followed by the names of
sections, usually single digits. The former are supposed to contain unformatted manual pages in mdoc(7) and/or man(7) format; file
names should end with the name of the section preceded by a dot. The latter should contain preformatted manual pages; file names
should end with '.0'.
Creating a mandoc.db(5) database with makewhatis(8) in each directory configured with manpath is recommended and necessary for
apropos(1) to work, but not strictly required for man(1).
output option [value]
Configure the default value of an output option. These directives are overridden by the -O command line options of the same names.
For details, see the mandoc(1) manual.
option value used by -T
fragment none html
includes string html
indent integer ascii, utf8
man string html
paper string ps, pdf
style string html
width integer ascii, utf8
_whatdb path/whatis.db
This directive provides the same functionality as manpath, but using a historic and misleading syntax. It is kept for backward
compatibility for now, but will eventually be removed.
FILES
/etc/man.conf
EXAMPLES
The following configuration file reproduces the defaults: installing it is equivalent to not having a man.conf file at all.
manpath /usr/share/man
manpath /usr/X11R6/man
manpath /usr/local/man
SEE ALSO
apropos(1), man(1), makewhatis(8)
HISTORY
A relatively complicated man.conf file format first appeared in 4.3BSD-Reno. For OpenBSD 5.8, it was redesigned from scratch, aiming for
simplicity.
AUTHORS
Ingo Schwarze <schwarze@openbsd.org>
Debian December 28, 2016 MAN.CONF(5)