07-29-2016
find(1) - Linux manual page
Quote:
-noleaf
Do not optimize by assuming that directories contain 2 fewer
subdirectories than their hard link count. This option is
needed when searching filesystems that do not follow the Unix
directory-link convention, such as CD-ROM or MS-DOS
filesystems or AFS volume mount points. Each directory on a
normal Unix filesystem has at least 2 hard links: its name and
its `.' entry. Additionally, its subdirectories (if any)
each have a `..' entry linked to that directory. When find is
examining a directory, after it has statted 2 fewer
subdirectories than the directory's link count, it knows that
the rest of the entries in the directory are non-directories
(`leaf' files in the directory tree). If only the files'
names need to be examined, there is no need to stat them; this
gives a significant increase in search speed.
To be honest, I never looked to see if a mounted CDROM used .. and . Good question, Don.
I assume this would apply to SMB mounts from FAT32 filesystems.
9 More Discussions You Might Find Interesting
1. Shell Programming and Scripting
Hi ,
I 'm trying to check if multiple directories exist on a server, if not create the missing ones and print " creating missing directory.
how to write this in a simple script, I have made my code complex
if ; then
taskStatus="Schema extract directory exists, checking if SQL,Count and... (7 Replies)
Discussion started by: ramky79
7 Replies
2. Shell Programming and Scripting
Hello all,
Here's the deal...I have one directory with many subdirs and files.
What I want to find out is who is keeping old files and directories...say files and dirs that they didn't use since a number of n days, only one level under the initial dir. Output to a file.
A script for... (5 Replies)
Discussion started by: ejianu
5 Replies
3. Shell Programming and Scripting
Hi ,
I am very new to unix as well as shell scripting. I have to write a script for the following requirement.
In a particular mount, have to list all the directories and sub directories along with size of the directory and sub directory in ascending order.
Please help me in this regard and many... (4 Replies)
Discussion started by: nmakkena
4 Replies
4. UNIX for Dummies Questions & Answers
Hi all,
Using grep command, i want to find the pattern of text in all directories and sub-directories.
e.g: if i want to search for a pattern named "parmeter", i used the command
grep -i "param" ../*
is this correct? (1 Reply)
Discussion started by: vinothrajan55
1 Replies
5. Shell Programming and Scripting
Can anyone come up with a unix command that lists
all the files, directories and sub-directories in the current directory
except a folder called log.?
Thank you in advance. (7 Replies)
Discussion started by: Manjunath B
7 Replies
6. UNIX for Dummies Questions & Answers
It is for HP-Unix B.11.31.
Requirement:
1. List the directories, having given pattern in the directories name, sorted by creation date.
Example: Directories with name "pkg32*" or "pkg33*"
2. On the output of 1. list the directories by creation date as sort order, with creation date... (2 Replies)
Discussion started by: Siva SQL
2 Replies
7. UNIX for Advanced & Expert Users
tcsh: have the following in .cshrc (or .tcshrc)
set prompt=": "
zsh: have the following in .zshrc
PS1="%# "
bash: have the following in .bashrc
PS1='\$ 'Lacking direct support this is a good approximation. (0 Replies)
Discussion started by: MadeInGermany
0 Replies
8. Solaris
I have searched this quite a long time but couldn't find the right method for me to use. I need to assign read write permission to the user for specific directories and it's sub directories and files. I do not want to use ACL. This is for Solaris. Please help. (1 Reply)
Discussion started by: blinkingdan
1 Replies
9. UNIX for Beginners Questions & Answers
We have regularly questions about how to create users and user accounts. But regularly user accounts need to be deleted too. It is quite easy to delete the user account itself but usually the HOME directory of the user remains.
It is good style to remove these directories but simply deleting... (3 Replies)
Discussion started by: bakunin
3 Replies
LN(1) BSD General Commands Manual LN(1)
NAME
link, ln -- make links
SYNOPSIS
ln [-Ffhinsv] source_file [target_file]
ln [-Ffhinsv] source_file ... target_dir
link source_file target_file
DESCRIPTION
The ln utility creates a new directory entry (linked file) which has the same modes as the original file. It is useful for maintaining mul-
tiple copies of a file in many places at once without using up storage for the ``copies''; instead, a link ``points'' to the original copy.
There are two types of links; hard links and symbolic links. How a link ``points'' to a file is one of the differences between a hard and
symbolic link.
The options are as follows:
-F If the target file already exists and is a directory, then remove it so that the link may occur. The -F option should be used with
either -f or -i options. If none is specified, -f is implied. The -F option is a no-op unless -s option is specified.
-h If the target_file or target_dir is a symbolic link, do not follow it. This is most useful with the -f option, to replace a symlink
which may point to a directory.
-f If the target file already exists, then unlink it so that the link may occur. (The -f option overrides any previous -i options.)
-i Cause ln to write a prompt to standard error if the target file exists. If the response from the standard input begins with the char-
acter 'y' or 'Y', then unlink the target file so that the link may occur. Otherwise, do not attempt the link. (The -i option over-
rides any previous -f options.)
-n Same as -h, for compatibility with other ln implementations.
-s Create a symbolic link.
-v Cause ln to be verbose, showing files as they are processed.
By default, ln makes hard links. A hard link to a file is indistinguishable from the original directory entry; any changes to a file are
effectively independent of the name used to reference the file. Hard links may not normally refer to directories and may not span file sys-
tems.
A symbolic link contains the name of the file to which it is linked. The referenced file is used when an open(2) operation is performed on
the link. A stat(2) on a symbolic link will return the linked-to file; an lstat(2) must be done to obtain information about the link. The
readlink(2) call may be used to read the contents of a symbolic link. Symbolic links may span file systems and may refer to directories.
Given one or two arguments, ln creates a link to an existing file source_file. If target_file is given, the link has that name; target_file
may also be a directory in which to place the link; otherwise it is placed in the current directory. If only the directory is specified, the
link will be made to the last component of source_file.
Given more than two arguments, ln makes links in target_dir to all the named source files. The links made will have the same name as the
files being linked to.
When the utility is called as link, exactly two arguments must be supplied, neither of which may specify a directory. No options may be sup-
plied in this simple mode of operation, which performs a link(2) operation using the two passed arguments.
COMPATIBILITY
The -h, -i, -n and -v options are non-standard and their use in scripts is not recommended. They are provided solely for compatibility with
other ln implementations.
The -F option is FreeBSD extention and should not be used in portable scripts.
SEE ALSO
link(2), lstat(2), readlink(2), stat(2), symlink(2), symlink(7)
STANDARDS
The ln utility conforms to IEEE Std 1003.2-1992 (``POSIX.2'').
The simplified link command conforms to Version 2 of the Single UNIX Specification (``SUSv2'').
HISTORY
An ln command appeared in Version 1 AT&T UNIX.
BSD
February 14, 2006 BSD