Sponsored Content
Full Discussion: Warning using 'find'.
Operating Systems OS X (Apple) Warning using 'find'. Post 302994611 by bakunin on Saturday 25th of March 2017 06:15:10 AM
Old 03-25-2017
It is a - quite common - misconception to think that files/directories which names start with a dot are somehow special. They are not. In fact the only "special treatment" they receive is by the ls-command which does not display them as long as the option -a (display them anyway) is not given.

For all other commands (including find) directories and/or filenames starting with a dot a just as normal as all the others. If you want to exclude them from your result set you have to take specific precautions to filter them out. For the same reason:

Code:
rm ..

might not do what you wanted/expected it to do, but syntactically the command is OK and - given the right privileges - will do what it is supposed to do (which, again, might not be what you wanted, but that is another problem).

I hope this helps.

bakunin
 

2 More Discussions You Might Find Interesting

1. Solaris

Jumpstart -- Warning: Could not find matching rule in rules.ok

I just setup a new jumpstart server, and I'm having problems with rules.ok errors. I'm coming up blank after many Google searches, forum searches, etc..... This is the error I receive: Skipped interface e1000g1 Attempting to configure interface e1000g0... Configured interface e1000g0... (0 Replies)
Discussion started by: christr
0 Replies

2. Shell Programming and Scripting

find command giving incomplete sentence warning

Hi , I am adding a line in my shell scripts to delete all the old directory with the below command. On running this command it is coming out with the message find: incomplete statement find /ersdg3/ERS/ERS_INPUT_LOGS/RIO/rio_archive -type d -mtime +47 -exec rm -rf {} What is wrong or... (3 Replies)
Discussion started by: guddu_12
3 Replies
name(1m)																  name(1m)

NAME
name - A dcecp object that compares and expands DCE names SYNOPSIS
name compare name name name expand name name get string_binding name help [operation | -verbose] name operations name parse name ARGUMENTS
The name of an object in the DCE namespace. Examples of names include principal names, names of security groups, names of Cell Directory Service (CDS) objects like directories, softlinks, child pointers and so on, names of remote procedure call (RPC) entries and RPC groups, and Distributed File Service (DFS) filenames. The name of the name operation for which to display help information. An RPC string binding (without the object UUID) that identifies the network location of the target name. It contains an RPC protocol and a network address in the form: rpc_prot_seq:network_addr DESCRIPTION
The name object resolves, compares, and parses DCE names and string bindings. OPERATIONS
name compare Compares two names. The syntax is as follows: name compare name name The compare operation compares two names given as arguments and returns 1 if both syntactically refer to the same name. Otherwise, it returns 0. Privileges Required No special privileges are needed to use the name compare command. Examples dcecp> name compare /.:/sales/east east Error: Incomplete name dcecp> dcecp> name compare /.:/sales/east /.../org_cell/sales/east 1 dcecp> name expand Expands a simple DCE name to a global name. The syntax is as follows: name expand name The expand operation takes a single name as an argument and returns the canonical form of the name. This operation has the effect of con- verting /.: to /.../cellname. Privileges Required No special privileges are needed to use the name expand command. Examples dcecp> name expand /.:/sales /.../org_cell/sales dcecp> name get Returns a hostname given a full or partial string binding. The syntax is as follows: name get string_binding The get operation returns the host name identified by a specified string binding. The string_binding argument is a single string binding; you cannot supply multiple bindings in one operation. Privileges Required No special privileges are needed to use the name get command. Examples dcecp> name get ncan_ip_tcp:15.21.248.170 hosts/goober dcecp> name help Returns help information about the name object and its operations. The syntax is as follows: name help [operation | -verbose] Options Displays information about the name object. Used without an argument or option, the name help operation returns brief information about each name operation. The optional operation argument is the name of the operation about which you want detailed information. Alternatively, you can use the -verbose option for more detailed information about the name object itself. Privileges Required No special privileges are needed to use the name help command. Examples dcecp> name help compare Compares two names syntactically. expand Returns the canonical form of a name. get Gets host name from a partial or full string binding. parse Parses name into cell name and residual name. help Prints a summary of command-line options. operations Returns a list of the valid operations for this command. dcecp> name operations Returns a list of the operations supported by the name object. The syntax is as follows: name operations The list of available operations is in alphabetical order except for help and operations, which are listed last. Privileges Required No special privileges are needed to use the name operations command. Examples dcecp> name operations compare expand get parse help operations dcecp> name parse Divides a name into a cell name and a residual name. The syntax is as follows: name parse name The parse operation parses a name into a cell name and a residual name. The argument is a single DCE name. The operation returns a list of two elements: cell name and residual name. A name not beginning with a / (slash) is considered to be a name in the local cell. Privileges Required No special privileges are needed to use the name parse command. Examples dcecp> name parse hosts/goober /.../pokey hosts/goober dcecp> RELATED INFORMATION
Commands: dcecp(1m). name(1m)
All times are GMT -4. The time now is 08:18 AM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy