find: Warning Messages

1 
1 8.1.2 Warning Messages
1 ----------------------
1 
1 If there is an error on the 'find' command line, an error message is
1 normally issued.  However, there are some usages that are inadvisable
1 but which 'find' should still accept.  Under these circumstances, 'find'
1 may issue a warning message.
1 
1    By default, warnings are enabled only if 'find' is being run
1 interactively (specifically, if the standard input is a terminal) and
1 the 'POSIXLY_CORRECT' environment variable is not set.  Warning messages
1 can be controlled explicitly by the use of options on the command line:
1 
1 '-warn'
1      Issue warning messages where appropriate.
1 '-nowarn'
1      Do not issue warning messages.
1 
1    These options take effect at the point on the command line where they
1 are specified.  Therefore it's not useful to specify '-nowarn' at the
1 end of the command line.  The warning messages affected by the above
1 options are triggered by:
1 
1    - Use of the '-d' option which is deprecated; please use '-depth'
1      instead, since the latter is POSIX-compliant.
1    - Use of the '-ipath' option which is deprecated; please use
1      '-iwholename' instead.
1    - Specifying an option (for example '-mindepth') after a non-option
1      (for example '-type' or '-print') on the command line.
1    - Use of the '-name' or '-iname' option with a slash character in the
1      pattern.  Since the name predicates only compare against the
1      basename of the visited files, the only file that can match a slash
1      is the root directory itself.
1 
1    The default behaviour above is designed to work in that way so that
1 existing shell scripts don't generate spurious errors, but people will
1 be made aware of the problem.
1 
1    Some warning messages are issued for less common or more serious
1 problems, and consequently cannot be turned off:
1 
1    - Use of an unrecognised backslash escape sequence with '-fprintf'
1    - Use of an unrecognised formatting directive with '-fprintf'
1