Login or Register to Ask a Question and Join Our Community

Sponsored Content
Full Discussion: Problems with find command
Top Forums UNIX for Dummies Questions & Answers Problems with find command Post 302142545 by bakunin on Saturday 27th of October 2007 07:47:03 AM
Old 10-27-2007
First off, "-mtime" uses the modification time. You spoke about "access time" above, which would make the "-atime" clause correct - check if what you do is what you want.

The next thing would be analogously with -ctime and -atime: my find (AIX 5.3, ML 06) is NOT understanding "-mtime -1" because "-1" would be treated as a separate option. It understands "-mtime +1" (everything more than 1 day ago) and "-mtime 1" (everything up to one day ago). I don't know, but i suppose your find doesn't find what you think it finds either.

Now to your last question: no, you can't find out which process or host has last accessed the file. The reason is these times (mtime, atime, ctime) are stored in the inode of the file as timestamps. Information about what was the cause for creation, modification or access is not stored, only the time in form of a timestamp. If you "touch" (man touch) a file for instance the mtime gets changed to the current system time, but no information about touch being responsible for that change is stored.

bakunin
 

10 More Discussions You Might Find Interesting

1. Programming

CC command problems

Apparently I do not have C on my Sun Blade. It's a fresh install, and I'l fairly new to using this box. When I type cc, I get the following: /usr/ucb/cc: language optional software package not installed... Does this mean I do not have C on this Blade? How can I get it and set it up? Thanks! (1 Reply)
Discussion started by: jpeery
1 Replies

2. Shell Programming and Scripting

find: problems escaping printf-command string

Hi Folks! Can you help me with this find -printf command. I seem to be unable to execute the printf-command from my shell script. I'm confused: :confused: My shell script snippet looks like this: #!/bin/sh .. COMMAND="find ./* -printf '%p %m %s %u %g \n'" echo "Command: ${COMMAND}"... (1 Reply)
Discussion started by: grahamb
1 Replies

3. Shell Programming and Scripting

Find problems

Hey, I was hoping for some help, my point was to search for all "core" files with only digits in the extension Eg: 1) core.153498 < He should find it 2) core.1 < He should find it 3) core.919jasj < shouldn't find it 4) core.abdijs < shouldn't find it find . -name 'core.*' -printf "%s... (6 Replies)
Discussion started by: candyzouk
6 Replies

4. Shell Programming and Scripting

find & dirname:problems with white spaces in Directories

Hi all, my problem: (little extract from my bash-script) I want to move each file (.mov) from one directory (and many Subdirectories) to another directory (only one); after moving i want to create hardlinks to the old directories. Thatīs no problem, but now: source-directories... (4 Replies)
Discussion started by: tubian
4 Replies

5. Shell Programming and Scripting

Problems with find's -newer Flag

I am writing a script that looks in a reports directory, copies a specified script to a working folder, copies some data files into the working folder, runs the report, zips the new files, then uploads them. Right now to determine what files to zip (as I don't know how many report files there... (6 Replies)
Discussion started by: droppedonjapan
6 Replies

6. UNIX for Dummies Questions & Answers

Problems with find & -size

Hi I am trying to find files over a size given by the user. this is what I have so far echo "Enter a pathname to check (example = /home/jsk1gcc/testwork): " read input echo "Enter a the size (examples = 100k, 10M, 1G): " read size find $input -size +$size echo echo "Hit the Enter... (2 Replies)
Discussion started by: AngelFlesh
2 Replies

7. Shell Programming and Scripting

Execution problems with Find

the below cmd is not wrking in perl script find . -name "*e*" -exec wc -l {} \; its show the following error Can't modify system in scalar assignment at prjt.pl line 4, near ");" Execution of prjt.pl aborted due to compilation errors. (11 Replies)
Discussion started by: natraj005
11 Replies

8. Shell Programming and Scripting

Problems with find | ls within a for statement

Hello, for dir in `find /root/test -type d` ;do echo "$dir" done for dir in `ls -1d /root/test/*/` ;do echo "$dir" done If there's a directory with spaces in name, it does echo each word of that dir separately... solution? mkdir "test" cd test mkdir "example_1_2_3"... (6 Replies)
Discussion started by: TehOne
6 Replies

9. Shell Programming and Scripting

problems with ksh array and find command

set -A allfiles `find $usrhtml -type f` i am trying to populate this array with the find command. It works fine when find is looking through a single directory but when i add a new subdirectory the files in the subdirectory get duplicated. Can anyone help me and fix this so each files in... (1 Reply)
Discussion started by: bjhum33
1 Replies

10. Shell Programming and Scripting

Problems with script to find file names

Have a text file "test-array.txt" with contents below a23003 b23406 c23506 Tying to read the above file into an array and search for file-names in a directory TEST_DIR ,recursively with the above names in them. Example: If TEST_DIR has a files named xyxa_a23003_test.sql,... (4 Replies)
Discussion started by: gaurav99
4 Replies

LEARN ABOUT REDHAT

tmpwatch

TMPWATCH(8)						   System Administrator's Manual					       TMPWATCH(8)

NAME

       tmpwatch - removes files which haven't been accessed for a period of time

SYNOPSIS

       tmpwatch [-u|-m|-c] [-faqstv] [--verbose] [--force] [--all] [--test]
		      [--fuser ] [--atime|--mtime|--ctime] [--quiet] <hours> <dirs>

DESCRIPTION

       tmpwatch  recursively  removes  files  which haven't been accessed for a given number of hours. Normally, it's used to clean up directories
       which are used for temporary holding space such as /tmp.

       When changing directories, tmpwatch is very sensitive to possible race conditions and will exit with an error if one is detected.  It  does
       not follow symbolic links in the directories it's cleaning (even if a symbolic link is given as its argument), will not switch filesystems,
	and only removes empty directories and regular files.

       By  default,  tmpwatch dates files by their atime (access time), not their mtime (modification time). If files aren't being removed when ls
       -l implies they should be, use ls -u to examine their atime to see if that explains the problem.

       If the --atime, --ctime or --mtime options are used in combination, the decision about deleting a file will be based on the maximum of this
       times.

       The hours parameter defines the threshold for removing files. If the file has not been accessed for hours hours, the file is removed.  Fol-
       lowing this, one or more directories may be given for tmpwatch to clean up.

OPTIONS

       -u, --atime
	      Make the decision about deleting a file based on the file's atime (access time). This is the default.

       -m, --mtime
	      Make the decision about deleting a file based on the file's mtime (modification time) instead of the atime.

       -c, --ctime
	      Make the decision about deleting a file based on the file's ctime (inode change time) instead of the atime;  for	directories,  make
	      the decision based on the mtime.

       -a, --all
	      Remove all file types, not just regular files and directories.

       -d, --nodirs
	      Do not attempt to remove directories, even if they are empty.

       -f, --force
	      Remove files even if root doesn't have write access (akin to rm -f).

       -t, --test
	      Doesn't remove files, but goes through the motions of removing them. This implies -v.

       -s, --fuser
	      Attempt to use the "fuser" command to see if a file is already open before removing it.  Not enabled by default.	 Does help in some
	      circumstances, but not all.  Dependent on fuser being installed in /sbin.

       -v, --verbose
	      Print a verbose display. Two levels of verboseness are available -- use this option twice to get the most verbose output.

SEE ALSO

       cron(1), ls(1), rm(1), fuser(1)

WARNINGS

       GNU-style long options are not supported on HP-UX.

AUTHORS

       Erik Troan <ewt@redhat.com>
       Preston Brown <pbrown@redhat.com>
       Nalin Dahyabhai <nalin@redhat.com>

4th Berkeley Distribution					  Wed Nov 28 2001						       TMPWATCH(8)
All times are GMT -4. The time now is 09:53 AM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy