279 True if the current file has been modified more
280 recently than the argument file.
281
282
283 -nogroup
284 True if the file belongs to non-existing group.
285
286
287 -nouser
288 True if the file belongs to non-existing user.
289
290
291 -ok command
292 Like -exec, except that the generated command line is
293 printed with a question mark first, and is executed
294 only if the response is affirmative.
295
296
297 -path
298 Like -name, but matches the entire file path and not
299 just basename.
300
301
302 -perm [-]mode
303 The mode argument is used to represent file mode bits.
304 It is identical in format to the symbolic mode
305 operand, symbolic_mode_list, described in chmod(1),
306 and is interpreted as follows. To start, a template is
307 assumed with all file mode bits cleared. An op symbol
308 of:
309
310 +
311 Set the appropriate mode bits in the template
312
313
314 -
315 Clear the appropriate bits
316
317
318 =
319 Set the appropriate mode bits, without regard
663 all files.
664
665
666 Some files that might be under the Solaris root file system are
667 actually mount points for virtual file systems, such as mntfs or
668 namefs. When comparing against a ufs file system, such files are not
669 selected if -mount or -xdev is specified in the find expression.
670
671
672 Using the -L or -follow option is not recommended when descending a
673 file-system hierarchy that is under the control of other users. In
674 particular, when using -exec, symbolic links can lead the find command
675 out of the hierarchy in which it started. Using -type is not sufficient
676 to restrict the type of files on which the -exec command operates,
677 because there is an inherent race condition between the type-check
678 performed by the find command and the time the executed command
679 operates on the file argument.
680
681
682
683 September 5, 2011 FIND(1)
|
279 True if the current file has been modified more
280 recently than the argument file.
281
282
283 -nogroup
284 True if the file belongs to non-existing group.
285
286
287 -nouser
288 True if the file belongs to non-existing user.
289
290
291 -ok command
292 Like -exec, except that the generated command line is
293 printed with a question mark first, and is executed
294 only if the response is affirmative.
295
296
297 -path
298 Like -name, but matches the entire file path and not
299 just basename, and without any special treatment of
300 leading periods.
301
302
303 -perm [-]mode
304 The mode argument is used to represent file mode bits.
305 It is identical in format to the symbolic mode
306 operand, symbolic_mode_list, described in chmod(1),
307 and is interpreted as follows. To start, a template is
308 assumed with all file mode bits cleared. An op symbol
309 of:
310
311 +
312 Set the appropriate mode bits in the template
313
314
315 -
316 Clear the appropriate bits
317
318
319 =
320 Set the appropriate mode bits, without regard
664 all files.
665
666
667 Some files that might be under the Solaris root file system are
668 actually mount points for virtual file systems, such as mntfs or
669 namefs. When comparing against a ufs file system, such files are not
670 selected if -mount or -xdev is specified in the find expression.
671
672
673 Using the -L or -follow option is not recommended when descending a
674 file-system hierarchy that is under the control of other users. In
675 particular, when using -exec, symbolic links can lead the find command
676 out of the hierarchy in which it started. Using -type is not sufficient
677 to restrict the type of files on which the -exec command operates,
678 because there is an inherent race condition between the type-check
679 performed by the find command and the time the executed command
680 operates on the file argument.
681
682
683
684 February 20, 2020 FIND(1)
|