Very Computer

1. finding new files with 'find'

|> maui /usr/tomt/src/nms% cat >zzz
|> maui /usr/tomt/src/nms% ls -l zzz
|> -rw-r--r--  1 tomt            0 Jul 23 15:41 zzz
|> maui /usr/tomt/src/nms% find . -name '*.[CEHh]' -mtime -1 -ls
|> maui /usr/tomt/src/nms% find . -name '*.[CEHh]' -ctime -1 -ls

Well, since you told find to locate files whose names are '*.[CEHh]' AND whose
mtime/ctime is less than 1 day, it does not surprise me that find failed to
list the file named "zzz", which does not meet the file name requirements you
specified.

How about this:

cats% cat > zzz.C
cats% ls -l zzz.C
-rw-rw-r--  1 jik             0 Jul 23 17:55 zzz.C
cats% find . -name '*.[CEHh]' -mtime -1 -ls
26891    0 -rw-rw-r--  1 jik      101             0 Jul 23 17:55 ./zzz.C
cats% find . -name '*.[CEHh]' -ctime -1 -ls
26891    0 -rw-rw-r--  1 jik      101             0 Jul 23 17:55 ./zzz.C

It seems to me to work just fine.

--

2. Ressource busy

3. New kernel can't find find any files

4. gilib23 in modules. but witch one ???

5. 'Find' 'Updatedb' or find database replacement for Solaris 2.X?

6. GPL and Microsoft

7. 'find' arguments find file containing permission

8. Accessing an NT file server from AIX

9. Finding multiple files with 'find'

10. Usind 'find' command to find certain text within a file

11. New kernel stops booting at ''finding module dependencies''

12. man can't format new man pages - can't find DESC file