From 564859bff86173d28a51158edbba3e671fcc7ef5 Mon Sep 17 00:00:00 2001 From: Kevin Dalley Date: Wed, 15 Mar 2000 08:23:57 +0000 Subject: [PATCH] *** empty log message *** --- config.h.in | 291 +++++++++++++++++++++++++++++------------------- doc/find.info | 161 +++++++++++++-------------- doc/find.info-1 | 134 +++++++++++----------- doc/find.info-2 | 23 ++-- 4 files changed, 332 insertions(+), 277 deletions(-) diff --git a/config.h.in b/config.h.in index bf72e536..75509411 100644 --- a/config.h.in +++ b/config.h.in @@ -1,105 +1,5 @@ /* config.h.in. Generated automatically from configure.in by autoheader. */ -/* Define if on AIX 3. - System headers sometimes define this. - We just want to avoid a redefinition error message. */ -#ifndef _ALL_SOURCE -#undef _ALL_SOURCE -#endif - -/* Define if using alloca.c. */ -#undef C_ALLOCA - -/* Define if the closedir function returns void instead of int. */ -#undef CLOSEDIR_VOID - -/* Define to empty if the keyword does not work. */ -#undef const - -/* Define to one of _getb67, GETB67, getb67 for Cray-2 and Cray-YMP systems. - This function is required for alloca.c support on those systems. */ -#undef CRAY_STACKSEG_END - -/* Define to `int' if doesn't define. */ -#undef gid_t - -/* Define if you have alloca, as a function or macro. */ -#undef HAVE_ALLOCA - -/* Define if you have and it should be used (not on Ultrix). */ -#undef HAVE_ALLOCA_H - -/* Define if you don't have vprintf but do have _doprnt. */ -#undef HAVE_DOPRNT - -/* Define if you have the getmntent function. */ -#undef HAVE_GETMNTENT - -/* Define if your struct stat has st_blocks. */ -#undef HAVE_ST_BLOCKS - -/* Define if your struct stat has st_rdev. */ -#undef HAVE_ST_RDEV - -/* Define if you have the strftime function. */ -#undef HAVE_STRFTIME - -/* Define if you have that is POSIX.1 compatible. */ -#undef HAVE_SYS_WAIT_H - -/* Define if your struct tm has tm_zone. */ -#undef HAVE_TM_ZONE - -/* Define if you don't have tm_zone but do have the external array - tzname. */ -#undef HAVE_TZNAME - -/* Define if you have the vprintf function. */ -#undef HAVE_VPRINTF - -/* Define if major, minor, and makedev are declared in . */ -#undef MAJOR_IN_MKDEV - -/* Define if major, minor, and makedev are declared in . */ -#undef MAJOR_IN_SYSMACROS - -/* Define if on MINIX. */ -#undef _MINIX - -/* Define to `int' if doesn't define. */ -#undef pid_t - -/* Define if the system does not provide POSIX.1 features except - with this defined. */ -#undef _POSIX_1_SOURCE - -/* Define if you need to in order for stat and other things to work. */ -#undef _POSIX_SOURCE - -/* Define to `unsigned' if doesn't define. */ -#undef size_t - -/* If using the C implementation of alloca, define if you know the - direction of stack growth for your system; otherwise it will be - automatically deduced at run-time. - STACK_DIRECTION > 0 => grows toward higher addresses - STACK_DIRECTION < 0 => grows toward lower addresses - STACK_DIRECTION = 0 => direction of growth unknown - */ -#undef STACK_DIRECTION - -/* Define if the `S_IS*' macros in do not work properly. */ -#undef STAT_MACROS_BROKEN - -/* Define if you have the ANSI C header files. */ -#undef STDC_HEADERS - -/* Define if your declares struct tm. */ -#undef TM_IN_SYS_TIME - -/* Define to `int' if doesn't define. */ -#undef uid_t - /* Define if you have the Andrew File System. */ #undef AFS @@ -134,38 +34,197 @@ /* Define to `unsigned long' if doesn't define. */ #undef ino_t -/* Define if you have the fchdir function. */ -#undef HAVE_FCHDIR +/* Define if the `closedir' function returns void instead of `int'. */ +#undef CLOSEDIR_VOID -/* Define if you have the getcwd function. */ -#undef HAVE_GETCWD +/* Define to one of _getb67, GETB67, getb67 for Cray-2 and Cray-YMP systems. + This function is required for alloca.c support on those systems. */ +#undef CRAY_STACKSEG_END -/* Define if you have the strerror function. */ -#undef HAVE_STRERROR +/* Define if using `alloca.c'. */ +#undef C_ALLOCA -/* Define if you have the header file. */ +/* Define if you have `alloca', as a function or macro. */ +#undef HAVE_ALLOCA + +/* Define if you have and it should be used (not on Ultrix). */ +#undef HAVE_ALLOCA_H + +/* Define if you have the `basename' function. */ +#undef HAVE_BASENAME + +/* Define if you have the header file. */ #undef HAVE_DIRENT_H -/* Define if you have the header file. */ +/* Define if you don't have `vprintf' but do have `_doprnt.' */ +#undef HAVE_DOPRNT + +/* Define if you have the `fchdir' function. */ +#undef HAVE_FCHDIR + +/* Define if you have the header file. */ #undef HAVE_FCNTL_H -/* Define if you have the header file. */ +/* Define if you have the `getcwd' function. */ +#undef HAVE_GETCWD + +/* Define if you have the `getmntent' function. */ +#undef HAVE_GETMNTENT + +/* Define if you have the `dir' library (-ldir). */ +#undef HAVE_LIBDIR + +/* Define if you have the `gen' library (-lgen). */ +#undef HAVE_LIBGEN + +/* Define if you have the `intl' library (-lintl). */ +#undef HAVE_LIBINTL + +/* Define if you have the `seq' library (-lseq). */ +#undef HAVE_LIBSEQ + +/* Define if you have the `sun' library (-lsun). */ +#undef HAVE_LIBSUN + +/* Define if you have the `x' library (-lx). */ +#undef HAVE_LIBX + +/* Define if you have the header file. */ #undef HAVE_LIMITS_H -/* Define if you have the header file. */ +/* Define if you have the `memcmp' function. */ +#undef HAVE_MEMCMP + +/* Define if you have the `memset' function. */ +#undef HAVE_MEMSET + +/* Define if you have the `mktime' function. */ +#undef HAVE_MKTIME + +/* Define if you have the header file. */ #undef HAVE_NDIR_H -/* Define if you have the header file. */ +/* Define if you have the `stpcpy' function. */ +#undef HAVE_STPCPY + +/* Define if you have the `strdup' function. */ +#undef HAVE_STRDUP + +/* Define if you have the `strerror' function. */ +#undef HAVE_STRERROR + +/* Define if you have the `strftime' function. */ +#undef HAVE_STRFTIME + +/* Define if you have the header file. */ #undef HAVE_STRING_H -/* Define if you have the header file. */ +/* Define if you have the `strspn' function. */ +#undef HAVE_STRSPN + +/* Define if you have the `strstr' function. */ +#undef HAVE_STRSTR + +/* Define if you have the `strtol' function. */ +#undef HAVE_STRTOL + +/* Define if `st_blocks' is member of `struct stat'. */ +#undef HAVE_STRUCT_STAT_ST_BLOCKS + +/* Define if `st_rdev' is member of `struct stat'. */ +#undef HAVE_STRUCT_STAT_ST_RDEV + +/* Define if `tm_zone' is member of `struct tm'. */ +#undef HAVE_STRUCT_TM_TM_ZONE + +/* Define if your `struct stat' has `st_blocks'. Deprecated, use + `HAVE_STRUCT_STAT_ST_BLOCKS' instead. */ +#undef HAVE_ST_BLOCKS + +/* Define if your `struct stat' has `st_rdev'. Deprecated, use + `HAVE_STRUCT_STAT_ST_RDEV' instead. */ +#undef HAVE_ST_RDEV + +/* Define if you have the header file. */ #undef HAVE_SYS_DIR_H -/* Define if you have the header file. */ +/* Define if you have the header file. */ #undef HAVE_SYS_NDIR_H -/* Define if you have the header file. */ +/* Define if you have that is POSIX.1 compatible. */ +#undef HAVE_SYS_WAIT_H + +/* Define if your `struct tm' has `tm_zone'. Deprecated, use + `HAVE_STRUCT_TM_TM_ZONE' instead. */ +#undef HAVE_TM_ZONE + +/* Define if you don't have `tm_zone' but do have the external array `tzname'. + */ +#undef HAVE_TZNAME + +/* Define if you have the header file. */ #undef HAVE_UNISTD_H -/* Define if you have the sun library (-lsun). */ -#undef HAVE_LIBSUN +/* Define if you have the `vprintf' function. */ +#undef HAVE_VPRINTF + +/* Define if `major', `minor', and `makedev' are declared in . */ +#undef MAJOR_IN_MKDEV + +/* Define if `major', `minor', and `makedev' are declared in . */ +#undef MAJOR_IN_SYSMACROS + +/* If using the C implementation of alloca, define if you know the + direction of stack growth for your system; otherwise it will be + automatically deduced at run-time. + STACK_DIRECTION > 0 => grows toward higher addresses + STACK_DIRECTION < 0 => grows toward lower addresses + STACK_DIRECTION = 0 => direction of growth unknown */ +#undef STACK_DIRECTION + +/* Define if the `S_IS*' macros in do not work properly. */ +#undef STAT_MACROS_BROKEN + +/* Define if you have the ANSI C header files. */ +#undef STDC_HEADERS + +/* Define if your declares `struct tm'. */ +#undef TM_IN_SYS_TIME + +/* Define if on AIX 3. + System headers sometimes define this. + We just want to avoid a redefinition error message. */ +#ifndef _ALL_SOURCE +# undef _ALL_SOURCE +#endif + +/* Define if on MINIX. */ +#undef _MINIX + +/* Define if the system does not provide POSIX.1 features except with this + defined. */ +#undef _POSIX_1_SOURCE + +/* Define if you need to in order for stat and other things to work. */ +#undef _POSIX_SOURCE + +/* Define to empty if `const' does not conform to ANSI C. */ +#undef const + +/* Define to `unsigned long' if does not define. */ +#undef dev_t + +/* Define to `int' if doesn't define. */ +#undef gid_t + +/* Define to `unsigned long' if does not define. */ +#undef ino_t + +/* Define to `int' if does not define. */ +#undef pid_t + +/* Define to `unsigned' if does not define. */ +#undef size_t + +/* Define to `int' if doesn't define. */ +#undef uid_t diff --git a/doc/find.info b/doc/find.info index 330eddac..79128f98 100644 --- a/doc/find.info +++ b/doc/find.info @@ -1,5 +1,4 @@ -This is Info file find.info, produced by Makeinfo version 1.68 from the -input file find.texi. +This is find.info, produced by makeinfo version 4.0 from find.texi. START-INFO-DIR-ENTRY * Finding Files: (find). Listing and operating on files @@ -27,87 +26,87 @@ translation approved by the Foundation.  Indirect: -find.info-1: 1105 -find.info-2: 50768 +find.info-1: 1079 +find.info-2: 50721  Tag Table: (Indirect) -Node: Top1105 -Node: Introduction1917 -Node: Scope3088 -Node: Overview5008 -Node: find Expressions6766 -Node: Finding Files8387 -Node: Name8853 -Node: Base Name Patterns9477 -Node: Full Name Patterns10016 -Node: Fast Full Name Search11001 -Node: Shell Pattern Matching13156 -Node: Links14998 -Node: Symbolic Links15428 -Node: Hard Links16376 -Node: Time17412 -Node: Age Ranges17927 -Node: Comparing Timestamps18867 -Node: Size20146 -Node: Type20961 -Node: Owner21773 -Node: Permissions22586 -Node: Contents23271 -Node: Directories24439 -Node: Filesystems26913 -Node: Combining Primaries With Operators28185 -Node: Actions29486 -Node: Print File Name30033 -Node: Print File Information30637 -Node: Escapes32872 -Node: Format Directives33532 -Node: Name Directives34230 -Node: Ownership Directives34761 -Node: Size Directives35186 -Node: Location Directives35482 -Node: Time Directives36034 -Node: Time Formats36902 -Node: Time Components37329 -Node: Date Components37822 -Node: Combined Time Formats38632 -Node: Run Commands39116 -Node: Single File39469 -Node: Multiple Files40319 -Node: Unsafe File Name Handling42122 -Node: Safe File Name Handling43672 -Node: Limiting Command Size44358 -Node: Interspersing File Names46113 -Node: Querying47174 -Node: Adding Tests48090 -Node: Common Tasks50352 -Node: Viewing And Editing50768 -Node: Archiving51279 -Node: Cleaning Up52911 -Node: Strange File Names54472 -Node: Fixing Permissions56102 -Node: Classifying Files56661 -Node: Databases57379 -Node: Database Locations57993 -Node: Database Formats60298 -Node: New Database Format60949 -Node: Sample Database62511 -Node: Old Database Format63150 -Node: File Permissions64880 -Node: Mode Structure65448 -Node: Symbolic Modes67576 -Node: Setting Permissions68574 -Node: Copying Permissions71111 -Node: Changing Special Permissions71912 -Node: Conditional Executability73748 -Node: Multiple Changes74365 -Node: Umask and Protection76013 -Node: Numeric Modes77102 -Node: Reference78932 -Node: Invoking find79230 -Node: Invoking locate80277 -Node: Invoking updatedb81206 -Node: Invoking xargs82756 -Node: Primary Index85826 +Node: Top1079 +Node: Introduction1891 +Node: Scope3062 +Node: Overview4982 +Node: find Expressions6740 +Node: Finding Files8360 +Node: Name8826 +Node: Base Name Patterns9450 +Node: Full Name Patterns9988 +Node: Fast Full Name Search10972 +Node: Shell Pattern Matching13126 +Node: Links14967 +Node: Symbolic Links15397 +Node: Hard Links16344 +Node: Time17380 +Node: Age Ranges17895 +Node: Comparing Timestamps18835 +Node: Size20114 +Node: Type20927 +Node: Owner21739 +Node: Permissions22552 +Node: Contents23237 +Node: Directories24405 +Node: Filesystems26879 +Node: Combining Primaries With Operators28150 +Node: Actions29451 +Node: Print File Name29998 +Node: Print File Information30602 +Node: Escapes32834 +Node: Format Directives33494 +Node: Name Directives34192 +Node: Ownership Directives34723 +Node: Size Directives35148 +Node: Location Directives35444 +Node: Time Directives35995 +Node: Time Formats36860 +Node: Time Components37287 +Node: Date Components37780 +Node: Combined Time Formats38590 +Node: Run Commands39074 +Node: Single File39427 +Node: Multiple Files40277 +Node: Unsafe File Name Handling42080 +Node: Safe File Name Handling43630 +Node: Limiting Command Size44315 +Node: Interspersing File Names46070 +Node: Querying47129 +Node: Adding Tests48043 +Node: Common Tasks50305 +Node: Viewing And Editing50721 +Node: Archiving51232 +Node: Cleaning Up52864 +Node: Strange File Names54425 +Node: Fixing Permissions56055 +Node: Classifying Files56614 +Node: Databases57332 +Node: Database Locations57946 +Node: Database Formats60251 +Node: New Database Format60902 +Node: Sample Database62464 +Node: Old Database Format63103 +Node: File Permissions64833 +Node: Mode Structure65401 +Node: Symbolic Modes67529 +Node: Setting Permissions68526 +Node: Copying Permissions71062 +Node: Changing Special Permissions71863 +Node: Conditional Executability73698 +Node: Multiple Changes74315 +Node: Umask and Protection75962 +Node: Numeric Modes77051 +Node: Reference78881 +Node: Invoking find79179 +Node: Invoking locate80226 +Node: Invoking updatedb81155 +Node: Invoking xargs82705 +Node: Primary Index85775  End Tag Table diff --git a/doc/find.info-1 b/doc/find.info-1 index 0de538e3..f6b04239 100644 --- a/doc/find.info-1 +++ b/doc/find.info-1 @@ -1,5 +1,4 @@ -This is Info file find.info, produced by Makeinfo version 1.68 from the -input file find.texi. +This is find.info, produced by makeinfo version 4.0 from find.texi. START-INFO-DIR-ENTRY * Finding Files: (find). Listing and operating on files @@ -213,8 +212,7 @@ An expression can contain any of the following types of primaries: `-and'. *Note Combining Primaries With Operators::, for ways to connect primaries into more complex expressions. If the expression contains no actions other than `-prune', `-print' is performed on all -files for which the entire expression is true (*note Print File -Name::.). +files for which the entire expression is true (*note Print File Name::). Options take effect immediately, rather than being evaluated for each file when their place in the expression is reached. Therefore, for @@ -286,13 +284,13 @@ File: find.info, Node: Base Name Patterns, Next: Full Name Patterns, Up: Name Base Name Patterns ------------------ - - Test: -name PATTERN - - Test: -iname PATTERN + - Test: -name pattern + - Test: -iname pattern True if the base of the file name (the path with the leading directories removed) matches shell pattern PATTERN. For `-iname', the match is case-insensitive. To ignore a whole directory tree, - use `-prune' (*note Directories::.). As an example, to find - Texinfo source files in `/usr/local/doc': + use `-prune' (*note Directories::). As an example, to find Texinfo + source files in `/usr/local/doc': find /usr/local/doc -name '*.texi' @@ -302,16 +300,16 @@ File: find.info, Node: Full Name Patterns, Next: Fast Full Name Search, Prev: Full Name Patterns ------------------ - - Test: -path PATTERN - - Test: -ipath PATTERN + - Test: -path pattern + - Test: -ipath pattern True if the entire file name, starting with the command line argument under which the file was found, matches shell pattern PATTERN. For `-ipath', the match is case-insensitive. To ignore a whole directory tree, use `-prune' rather than checking every - file in the tree (*note Directories::.). + file in the tree (*note Directories::). - - Test: -regex EXPR - - Test: -iregex EXPR + - Test: -regex expr + - Test: -iregex expr True if the entire file name matches regular expression EXPR. This is a match on the whole path, not a search. For example, to match a file named `./fubar3', you can use the regular expression @@ -351,7 +349,7 @@ name. databases contain information. The differences are that the `locate' information might be out of date, and that `locate' handles wildcards in the pattern slightly differently than `find' (*note Shell Pattern -Matching::.). +Matching::). The file name databases contain lists of files that were on the system when the databases were last updated. The system administrator @@ -406,7 +404,7 @@ so does escaping with a backslash. works even in character classes. In the `find' tests that do shell pattern matching (`-name', -`-path', etc.), wildcards in the pattern do not match a `.' at the +`-path', etc.), wildcards in the pattern do not match a `.' at the beginning of a file name. This is not the case for `locate'. Thus, `find -name '*macs'' does not match a file named `.emacs', but `locate '*macs'' does. @@ -440,8 +438,8 @@ File: find.info, Node: Symbolic Links, Next: Hard Links, Up: Links Symbolic Links -------------- - - Test: -lname PATTERN - - Test: -ilname PATTERN + - Test: -lname pattern + - Test: -ilname pattern True if the file is a symbolic link whose contents match shell pattern PATTERN. For `-ilname', the match is case-insensitive. *Note Shell Pattern Matching::, for details about the PATTERN @@ -462,7 +460,7 @@ Symbolic Links * `-type' reports the types of the files that symbolic links point to. - * Implies `-noleaf' (*note Directories::.). + * Implies `-noleaf' (*note Directories::).  File: find.info, Node: Hard Links, Prev: Symbolic Links, Up: Links @@ -480,7 +478,7 @@ such as `/usr' on many systems. Doing this saves needless searching, since hard links to a file must be on the same filesystem. *Note Filesystems::. - - Test: -inum N + - Test: -inum n File has inode number N. You can also search for files that have a certain number of links, @@ -488,7 +486,7 @@ with `-links'. Directories normally have at least two hard links; their `.' entry is the second one. If they have subdirectories, each of those also has a hard link called `..' to its parent directory. - - Test: -links N + - Test: -links n File has N hard links.  @@ -522,15 +520,15 @@ Age Ranges These tests are mainly useful with ranges (`+N' and `-N'). - - Test: -atime N - - Test: -ctime N - - Test: -mtime N + - Test: -atime n + - Test: -ctime n + - Test: -mtime n True if the file was last accessed (or its status changed, or it was modified) N*24 hours ago. - - Test: -amin N - - Test: -cmin N - - Test: -mmin N + - Test: -amin n + - Test: -cmin n + - Test: -mmin n True if the file was last accessed (or its status changed, or it was modified) N minutes ago. These tests provide finer granularity of measurement than `-atime' et al. For example, to @@ -563,9 +561,9 @@ current year: find /usr -newer /tmp/stamp$$ rm -f /tmp/stamp$$ - - Test: -anewer FILE - - Test: -cnewer FILE - - Test: -newer FILE + - Test: -anewer file + - Test: -cnewer file + - Test: -newer file True if the file was last accessed (or its status changed, or it was modified) more recently than FILE was modified. These tests are affected by `-follow' only if `-follow' comes before them on @@ -575,7 +573,7 @@ current year: find . -newer /bin/sh - - Test: -used N + - Test: -used n True if the file was last accessed N days after its status was last changed. Useful for finding files that are not being used, and could perhaps be archived or removed to save disk space. @@ -586,7 +584,7 @@ File: find.info, Node: Size, Next: Type, Prev: Time, Up: Finding Files Size ==== - - Test: -size N[BCKW] + - Test: -size n[bckw] True if the file uses N units of space, rounding up. The units are 512-byte blocks by default, but they can be changed by adding a one-character suffix to N: @@ -609,8 +607,8 @@ Size - Test: -empty True if the file is empty and is either a regular file or a directory. This might make it a good candidate for deletion. - This test is useful with `-depth' (*note Directories::.) and - `-exec rm -rf '{}' ';'' (*note Single File::.). + This test is useful with `-depth' (*note Directories::) and `-exec + rm -rf '{}' ';'' (*note Single File::).  File: find.info, Node: Type, Next: Owner, Prev: Size, Up: Finding Files @@ -618,7 +616,7 @@ File: find.info, Node: Type, Next: Owner, Prev: Size, Up: Finding Files Type ==== - - Test: -type C + - Test: -type c True if the file is of type C: `b' @@ -642,7 +640,7 @@ Type `s' socket - - Test: -xtype C + - Test: -xtype c The same as `-type' unless the file is a symbolic link. For symbolic links: if `-follow' has not been given, true if the file is a link to a file of type C; if `-follow' has been given, true @@ -656,13 +654,13 @@ File: find.info, Node: Owner, Next: Permissions, Prev: Type, Up: Finding Fil Owner ===== - - Test: -user UNAME - - Test: -group GNAME + - Test: -user uname + - Test: -group gname True if the file is owned by user UNAME (belongs to group GNAME). A numeric ID is allowed. - - Test: -uid N - - Test: -gid N + - Test: -uid n + - Test: -gid n True if the file's numeric user ID (group ID) is N. These tests support ranges (`+N' and `-N'), unlike `-user' and `-group'. @@ -684,12 +682,12 @@ Permissions *Note File Permissions::, for information on how file permissions are structured and how to specify them. - - Test: -perm MODE + - Test: -perm mode True if the file's permissions are exactly MODE (which can be numeric or symbolic). Symbolic modes use mode 0 as a point of - departure. If MODE starts with `-', true if *all* of the + departure. If MODE starts with `-', true if _all_ of the permissions set in MODE are set for the file; permissions not set - in MODE are ignored. If MODE starts with `+', true if *any* of + in MODE are ignored. If MODE starts with `+', true if _any_ of the permissions set in MODE are set for the file; permissions not set in MODE are ignored. @@ -733,12 +731,12 @@ Directories searches them. These two options allow you to process a horizontal slice of a directory tree. - - Option: -maxdepth LEVELS + - Option: -maxdepth levels Descend at most LEVELS (a non-negative integer) levels of directories below the command line arguments. `-maxdepth 0' means only apply the tests and actions to the command line arguments. - - Option: -mindepth LEVELS + - Option: -mindepth levels Do not apply any tests or actions at levels less than LEVELS (a non-negative integer). `-mindepth 1' means process all files except the command line arguments. @@ -798,7 +796,7 @@ is to tell `find' to only search one filesystem: The other way is to check the type of filesystem each file is on, and not descend directories that are on undesirable filesystem types: - - Test: -fstype TYPE + - Test: -fstype type True if the file is on a filesystem of type TYPE. The valid filesystem types vary among different versions of Unix; an incomplete list of filesystem types that are accepted on some @@ -807,7 +805,7 @@ not descend directories that are on undesirable filesystem types: You can use `-printf' with the `%F' directive to see the types of your filesystems. *Note Print File Information::. `-fstype' is usually used with `-prune' to avoid searching remote filesystems - (*note Directories::.). + (*note Directories::).  File: find.info, Node: Combining Primaries With Operators, Prev: Filesystems, Up: Finding Files @@ -884,7 +882,7 @@ Print File Name True; print the full file name on the standard output, followed by a newline. - - Action: -fprint FILE + - Action: -fprint file True; print the full file name into file FILE, followed by a newline. If FILE does not exist when `find' is run, it is created; if it does exist, it is truncated to 0 bytes. The file @@ -916,7 +914,7 @@ Print File Information 3. The file's type and permissions. The type is shown as a dash for a regular file; for other file types, a letter like for - `-type' is used (*note Type::.). The permissions are read, + `-type' is used (*note Type::). The permissions are read, write, and execute for the file's owner, its group, and other users, respectively; a dash means the permission is not granted. *Note File Permissions::, for more details about @@ -936,19 +934,19 @@ Print File Information 9. The file's name. `-ls' quotes non-printable characters in the file names using C-like backslash escapes. - - Action: -fls FILE + - Action: -fls file True; like `-ls' but write to FILE like `-fprint' (*note Print - File Name::.). + File Name::). - - Action: -printf FORMAT + - Action: -printf format True; print FORMAT on the standard output, interpreting `\' escapes and `%' directives. Field widths and precisions can be specified as with the `printf' C function. Unlike `-print', `-printf' does not add a newline at the end of the string. - - Action: -fprintf FILE FORMAT + - Action: -fprintf file format True; like `-printf' but write to FILE like `-fprint' (*note Print - File Name::.). + File Name::). * Menu: @@ -1090,7 +1088,7 @@ Location Directives `%F' Type of the filesystem the file is on; this value can be used for - `-fstype' (*note Directories::.). + `-fstype' (*note Directories::). `%l' Object of symbolic link (empty string if file is not a symbolic @@ -1119,7 +1117,7 @@ depends on the current locale, but it typically looks like `%AK' File's last access time in the format specified by K (*note Time - Formats::.). + Formats::). `%c' File's last status change time in the format returned by the C @@ -1127,7 +1125,7 @@ depends on the current locale, but it typically looks like `%CK' File's last status change time in the format specified by K (*note - Time Formats::.). + Time Formats::). `%t' File's last modification time in the format returned by the C @@ -1135,7 +1133,7 @@ depends on the current locale, but it typically looks like `%TK' File's last modification time in the format specified by K (*note - Time Formats::.). + Time Formats::).  File: find.info, Node: Time Formats, Prev: Format Directives, Up: Print File Information @@ -1285,7 +1283,7 @@ Single File Here is how to run a command on one file at a time. - - Action: -exec COMMAND ; + - Action: -exec command ; Execute COMMAND; true if 0 status is returned. `find' takes all arguments after `-exec' to be part of the command until an argument consisting of `;' is reached. It replaces the string @@ -1409,9 +1407,9 @@ option to GNU `xargs', GNU `tar', GNU `cpio', or `perl'. True; print the full file name on the standard output, followed by a null character. - - Action: -fprint0 FILE + - Action: -fprint0 file True; like `-print0' but write to FILE like `-fprint' (*note Print - File Name::.). + File Name::).  File: find.info, Node: Limiting Command Size, Next: Interspersing File Names, Prev: Safe File Name Handling, Up: Multiple Files @@ -1466,8 +1464,8 @@ Interspersing File Names `xargs' can insert the name of the file it is processing between arguments you give for the command. Unless you also give options to -limit the command size (*note Limiting Command Size::.), this mode of -operation is equivalent to `find -exec' (*note Single File::.). +limit the command size (*note Limiting Command Size::), this mode of +operation is equivalent to `find -exec' (*note Single File::). `--replace[=REPLACE-STR]' `-i[REPLACE-STR]' @@ -1493,15 +1491,15 @@ Querying To ask the user whether to execute a command on a single file, you can use the `find' primary `-ok' instead of `-exec': - - Action: -ok COMMAND ; - Like `-exec' (*note Single File::.), but ask the user first (on - the standard input); if the response does not start with `y' or - `Y', do not run the command, and return false. + - Action: -ok command ; + Like `-exec' (*note Single File::), but ask the user first (on the + standard input); if the response does not start with `y' or `Y', + do not run the command, and return false. When processing multiple files with a single command, to query the user you give `xargs' the following option. When using this option, you might find it useful to control the number of files processed per -invocation of the command (*note Limiting Command Size::.). +invocation of the command (*note Limiting Command Size::). `--interactive' `-p' @@ -1539,7 +1537,7 @@ the test. Because `-exec' evaluates to the exit status of the executed program, you can write a program (which can be a shell script) that tests for a special attribute and make it exit with a true (zero) or false (non-zero) status. It is a good idea to place such a special -test *after* the builtin tests, because it starts a new process which +test _after_ the builtin tests, because it starts a new process which could be avoided if a builtin test evaluates to false. Use this method only when `xargs' is not flexible enough, because starting one or more new processes to test each file is slower than using `xargs' to start diff --git a/doc/find.info-2 b/doc/find.info-2 index 6a9f8dbc..30f3bafd 100644 --- a/doc/find.info-2 +++ b/doc/find.info-2 @@ -1,5 +1,4 @@ -This is Info file find.info, produced by Makeinfo version 1.68 from the -input file find.texi. +This is find.info, produced by makeinfo version 4.0 from find.texi. START-INFO-DIR-ENTRY * Finding Files: (find). Listing and operating on files @@ -183,7 +182,7 @@ and fix their permissions: find . -type d -not -perm -ug=w | xargs chmod ug+w You could also reverse the operations, if you want to make sure that -directories do *not* have world write permission. +directories do _not_ have world write permission.  File: find.info, Node: Classifying Files, Prev: Fixing Permissions, Up: Common Tasks @@ -480,7 +479,7 @@ Symbolic Modes operations on single-character symbols. They allow you to modify either all or selected parts of files' permissions, optionally based on their previous values, and perhaps on the current `umask' as well (*note -Umask and Protection::.). +Umask and Protection::). The format of symbolic modes is: @@ -516,7 +515,7 @@ symbolic modes can not contain spaces. The USERS part tells which users' access to the file is changed. It consists of one or more of the following letters (or it can be empty; -*note Umask and Protection::., for a description of what happens then). +*note Umask and Protection::, for a description of what happens then). When more than one of these letters is given, the order that they are in does not matter. @@ -645,13 +644,13 @@ mode: Remember that the special permissions only affect files that are executable, plus, on some systems, directories (on which they have -different meanings; *note Mode Structure::.). Using `a' in the USERS +different meanings; *note Mode Structure::). Using `a' in the USERS part of a symbolic mode does not cause the special permissions to be affected; thus, a+s -has *no effect*. You must use `u', `g', and `o' explicitly to affect +has _no effect_. You must use `u', `g', and `o' explicitly to affect the special permissions. Also, the combinations `u+t', `g+t', and `o+s' have no effect. @@ -690,7 +689,7 @@ Making Multiple Changes ----------------------- The format of symbolic modes is actually more complex than described -above (*note Setting Permissions::.). It provides two ways to make +above (*note Setting Permissions::). It provides two ways to make multiple changes to files' permissions. The first way is to specify multiple OPERATION and PERMISSIONS parts @@ -741,8 +740,8 @@ The Umask and Protection ------------------------ If the USERS part of a symbolic mode is omitted, it defaults to `a' -(affect all users), except that any permissions that are *set* in the -system variable `umask' are *not affected*. The value of `umask' can +(affect all users), except that any permissions that are _set_ in the +system variable `umask' are _not affected_. The value of `umask' can be set using the `umask' command. Its default value varies from system to system. @@ -757,12 +756,12 @@ permission for users who are not in the file's group, then the mode: +w adds permission to write to the file to its owner and to other users who -are in the file's group, but *not* to other users. In contrast, the +are in the file's group, but _not_ to other users. In contrast, the mode: a+w -ignores `umask', and *does* give write permission for the file to all +ignores `umask', and _does_ give write permission for the file to all users.