Sponsored Content
Full Discussion: List grep results
Top Forums UNIX for Dummies Questions & Answers List grep results Post 302094083 by napolayan on Wednesday 25th of October 2006 05:47:34 AM
Old 10-25-2006
slire,

Its not possible to get the file creation date in UNIX. Thats the answer i have got after going thru the threads on this topic. The only things u can get are time of last modification n time of last access. Weird, but apparently true.
 

10 More Discussions You Might Find Interesting

1. Shell Programming and Scripting

How to refine results of grep -p

I need help to further reduce the output shown below. I want to be able to only return the paragraph where the 'Database alias' is exactly equal to DBIHP. I do not want the other paragraphs being shown below. $ echo $dbalias DBIHP $ db2 list db directory|grep -p 'Database alias ... (2 Replies)
Discussion started by: priceb
2 Replies

2. UNIX for Dummies Questions & Answers

My ps -ef|grep command results are chopped off

On our one HP-UX 11i box, we have some very long paths defined. When I want to check on our user processes running, the resulting paths are chopped off. /xyz/abc/123/......./server/b is really a process running in the ..../server/bin directory. Is this a terminal problem or buffer length... (1 Reply)
Discussion started by: bsp18974
1 Replies

3. Shell Programming and Scripting

Selecting patterns from the results of grep

Hi All, I'm struggling with a problem that I'm wondering (and hoping!) that someone can help me with. I have a number of .xml files which I'm using grep to search for the string 'include'. I need to extract the value of the include from the grep result. For example, on any given file, I... (2 Replies)
Discussion started by: Steve_altius
2 Replies

4. Shell Programming and Scripting

Adding grep'd results in a variable

Here is one I am baffled with; I have not used unix for a while and now that I am back it has been fun remembering and I have enjoyed it, for the most past. this is in ksh. I need to search in a file for the line with X1 and cut columns 20-25, put them into a variable, added them (dollar... (3 Replies)
Discussion started by: CougarMutt
3 Replies

5. Shell Programming and Scripting

Grep no results

Hello guys, I have been looking around but can't find the answer to my problem: If the grep command displays no results, print "no results have been found" and increment x. But if the grep command find something, do nothing. if echo "no results have been found $x" x=`expr $x + 1 `... (3 Replies)
Discussion started by: Benou
3 Replies

6. UNIX for Dummies Questions & Answers

How to do ls -l on results of grep and find?

Hi, Am running the command below to search for files that contains a certain string. grep -il "shutdown" `find . -type f -mtime -1 -print` | grep "^./scripts/active" How do I get it to do a ls -l on the list of files? I tried doing ls -l `grep -il "shutdown" `find . -type f -mtime -1... (5 Replies)
Discussion started by: newbie_01
5 Replies

7. Shell Programming and Scripting

How to analyse results of grep

Hi all, I'm working with a peice of software that runs on Linux that allows planning trips in cars through maps. This software has different variations depending on the type of car, e.g. BMW, Audi, Hyundai, etc... Each variation has a dependency on common external components that are not... (1 Reply)
Discussion started by: emoshaya
1 Replies

8. UNIX for Dummies Questions & Answers

Grep not giving expected results

Version: RHEL 5.8 I am doing a grep of the piped output from ps command as shown below. I am grepping for the pattern ora_dbw* . But, in the result set I am seeing strings with ora_dbr* as well like ora_dbrm_SDLM1DAS3 as shown below. Any idea why is this happening ? $ ps -ef | grep... (6 Replies)
Discussion started by: John K
6 Replies

9. Shell Programming and Scripting

How to concatenate grep results?

hi, let's say we have input in files test1.txt, test2.txt, text3.txt ... ... ... ('...' means more files & lines not just 'dots') test1.txt has: A B C D ... ... ... test2.txt has A B C D ... ... ... (4 Replies)
Discussion started by: msonoth
4 Replies

10. Shell Programming and Scripting

Cannot get results from grep command

Hi, i have a file hello.log which as several line that look like the below 2015-12-07 09:46:56 0:339 120.111.12.12 POST /helloWorld 2015-12-07 09:46:57 0:439 122.111.12.12 POST /helloWorld .... when i grep expecting to see results like the below. ... (6 Replies)
Discussion started by: mohtashims
6 Replies
touch(1)						      General Commands Manual							  touch(1)

NAME
touch - Updates file access and modification times SYNOPSIS
touch [-acfm] [-r reference_file | -t time] file... The following older syntax is now maintained for backward compatibility, but may be withdrawn in future issues: touch [-acfm] [time] file... STANDARDS
Interfaces documented on this reference page conform to industry standards as follows: touch: XCU5.0 Refer to the standards(5) reference page for more information about industry standards and associated tags. OPTIONS
Changes only the access time. Suppresses the creation of the file. [Tru64 UNIX] Attempts to force the touch in spite of read and write permissions on a file. The -f option is actually a dummy option; it is not used by the touch code, but is recognized by getopt(). Changes only the modification time. Uses the time of the file named by the pathname reference_file instead of the current time. You cannot use -r and -t together. Uses the specified time instead of the current time. The time argument is a decimal number in the following form: [[CC]YY]MMDDhhmm[.SS] The paired decimal numbers in the preceding syntax line represent the following: The first two digits of the year (the century) The second two digits of the year (00-99) The month of the year (01-12) The day of the month (01-31) The hour of the day (00-23) The minute of the hour (00-59) The second of the minute (00-61) Both CC and YY are optional. If neither is specified, the current year is assumed. If YY is specified, but CC is not, CC is derived as follows: If YY is 69-99, CC is 19. If YY is 00-68, CC is 20. The resulting time is affected by the value of the TZ environment variable. If the resulting time value precedes the Epoch, touch exits immediately with an error status. The range of valid times past the Epoch extends to at least midnight 1 January 2000 UCT. The range for SS is 00-61 rather than 00-59 because of leap seconds. If SS is 60 or 61, and the resulting time, as affected by the TZ environment variable, does not refer to a leap second, the resulting time is one or two seconds after a time where SS is 59. If SS is not given a value, it is assumed to be 0 (zero). If neither the -a option nor the -m options are specified, touch behaves as if you have specified both options. OPERANDS
The file for which times should be modified, or which should be created. In the obsolescent version, if both the -r and -t options are omitted, and if the first file parameter is an eight or ten digit dec- imal integer, it is interpreted as a time parameter. The format for the time parameter in the obsolesent syntax is MMDDhhmm[YY] DESCRIPTION
The touch command updates the access and modification times of each file or directory named to the one specified on the command line or to the current time if you do not specify a time. You can specify the time with -t or by the time of the reference file with the -r option. If you do not specify a time, touch uses the current time. If you specify a file that does not exist, touch creates a file with that name unless you request otherwise with the -c option. The LC_TIME environment variable, if defined, specifies the order of month and day in the date specification and of hour and minute in the time specification. Otherwise, these orders default to MMdd and hhmm. The format for the time argument is MMddhhmm[yy]. The obsolescent format for the time argument is MMddhhmm[YY]. NOTES
The obsolescent version may be withdrawn from future versions of the XCU5.0 standards. The -r or -t options should be used. EXIT STATUS
The following exit values are returned: Successful completion. [Tru64 UNIX] The number of files whose times could not be successfully modified (including files that did not exist and were not created). When the -c option is specified, files are suppressed purposely, an error does not occur and a message is not written to standard error. The exit status returns zero (0) for success. EXAMPLES
To update the access and modification times of a file, enter: touch program.c This sets the last access and last modification times of program.c to the current date and time. If program.c does not exist, touch creates an empty file with that name. To avoid creating a new file, enter: touch -c program.c To update only the modification time, enter: touch -m *.o This updates only the last modification times of the files in the current directory that end with touch command is often used in this way to alter the results of the make command. To explicitly set the access and modification times, enter: touch -c 02171425 program.c This sets the access and modification dates to 14:25 (2:25 p.m.) February 17 of the current year. (This assumes that you are using the default format.) To touch a file with a numeric file name, include its full pathname or precede it with not mistaken for the time argument. For example, to touch the file 123.abc enter: touch -c ./123.abc ENVIRONMENT VARIABLES
The following environment variables affect the execution of touch: Provides a default value for the internationalization variables that are unset or null. If LANG is unset or null, the corresponding value from the default locale is used. If any of the internationalization vari- ables contain an invalid setting, the utility behaves as if none of the variables had been defined. If set to a non-empty string value, overrides the values of all the other internationalization variables. Determines the locale for the interpretation of sequences of bytes of text data as characters (for example, single-byte as opposed to multibyte characters in arguments). Determines the locale for the for- mat and contents of diagnostic messages written to standard error. [Tru64 UNIX] This environment variable, if defined, specifies the order of month and day in the date specification and of hour and minute in the time specification. Otherwise, these orders default to MMdd and hhmm. The format for the time argument is MMddhhmm[yy]. Determines the location of message catalogues for the processing of LC_MES- SAGES. Determines the time zone to be used for interpreting the time specification. SEE ALSO
Commands: date(1) Functions: creat(2), utime(2) Files: locale(4) Standards: standards(5) touch(1)
All times are GMT -4. The time now is 06:03 AM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy