NAME | SYNOPSIS | DESCRIPTION | OPTIONS | OPERANDS | EXAMPLES | EXIT STATUS | ATTRIBUTES | SEE ALSO
fnlist displays the names and references bound in the context of composite_name.
If composite_name is not provided, the default initial context is displayed.
The following options are supported:
Consult the authoritative source for information.
Display the references as well as the names bound in the context of composite_name. Without this option, only the names are displayed.
Display the references in detail. For onc_fn_* references, this option is useful to derive the name of the NIS+ table that stores the reference for every name bound in the context of composite_name.
The following operand is supported:
An FNS named object. Composite names, like UNIX file names, depend on the subcontexts created. Examples of commands with valid composite_name operands are:
eg% fnlist thisorgunit eg% fnlist thisorgunit/service eg% fnlist thisorgunit/service/printer |
When FNS is deployed, the composite name is specific to the deployed site.
In the following example, the command with no operand provides the listing with reference and address types for the initial context:
eg% fnlist -l |
In the following examples, where a user context is given (that is, composite_name = user/), FNS must first be deployed via fncreate(1M), using one of the naming services NIS, NIS+, or files. If FNS is not deployed, there are no user contexts and the commands will fail with the "Name not found" error message.
The following command shows the names bound in the context of user/:
eg% fnlist user/ |
The following command displays the names and references bound in the context of user/:
eg% fnlist -l user/ |
See attributes(5) for descriptions of the following attributes:
ATTRIBUTE TYPE | ATTRIBUTE VALUE |
---|---|
Availability | SUNWfns |
fnbind(1), fnlookup(1), fnunbind(1), fncreate(1M), fndestroy(1M), attributes(5), fns(5), fns_references(5)
NAME | SYNOPSIS | DESCRIPTION | OPTIONS | OPERANDS | EXAMPLES | EXIT STATUS | ATTRIBUTES | SEE ALSO