nondcesvc(4)nondcesvc(4)NAMEnondcesvc - file for dceping(8) that lists non-DCE services.
DESCRIPTION
dceping will ping services named in nondcesvc.
Supported naming conventions for this file are:
· CDS Name. Example entry:
/.:/hosts/foo/someService NAMESPACE PROMPT
/.:/hosts/foo/someService NAMESPACE NOPROMPT
You can find CDS namespace entries by using the cdsbrowser(8) com‐
mand.
· RPC String Binding. Example entry:
ncacn_ip_tcp:foo.entity.company.com[1755] STRING_BINDING
You can obtain string bindings from the endpoint map maintained by
rpcd. Use the command: rpccp show mappings. Note that the host
name (foo.entity.company.com in the example) can be replaced with
the IP address.
· RPC Service Interface ID. Example entry:
someOtherService INTERFACE_ID hostname
When using this form of name, also include the same entry in the
wellknownif file.
Note in the examples above that NAMESPACE, STRING_BINDING, and INTER‐
FACE_ID are literal strings that identify which naming convention is
being used. PROMPT is a literal string that will associate a login
context with the NAMESPACE Entry. This keyword will cause dceping to
prompt the user for a principal and password that has sufficient rights
to access the Entry. NOPROMPT does not cause prompting. PROMPT and
NOPROMPT are supported by the NAMESPACE naming convention only.
Environment Variables are supported in the Service Name. Use of these is sim‐
ilar to environment variable usage in the shell with the exception that thevariable must reference an absolute name, and not another environment vari‐
able. Use of environment variables is supported in all naming conventions.
· Environment Variable Name. Example entry:
/.:/hosts/foo/$SOME_SERVICE NAMESPACE PROMPT
/.:/hosts/foo/bankServer$(CITY)$(STATE) NAMESPACE NOPROMPT
$(SECD_STRING_BINDING) STRING_BINDING
$(SECD_INTERFACE_ID) INTERFACE_ID hostname
If you do not know the names of services that you want to ping before
dceping is run, and/or you would like to determine such names at run‐
time by providing your own function, you may do so through an entry of
the following form in nondcesvc:
full_path_name_of_your_executable BUILD_SVCNAMES
You specify your function's full path name in
full_path_name_of_your_executable followed by the literal string
BUILD_SVCNAMES. Your function should generate, on its stdout, a file
identical to the nondcesvc file with one difference. The output of the
executable should not have any BUILD_SVCNAMES entry. It can however
have any number of NAMESPACE, STRING_BINDING or INTERFACE_ID types of
entries.
Blank lines or lines beginning with # are ignored. You can use either spaces
or tabs to separate items in a line. The string, endNonDCESvc, must occur in
the last line of the file as an end of file indicator.FILE
/opt/dcelocal/hpadmin/etc/nondcesvc (for HP-UX version 9.x)
/etc/opt/dce/hpadmin/etc/nondcesvc (for HP-UX version 10.x)
SEE ALSOdceping(8), wellknownif(4), rpccp(8), cdsbrowser(8)HP DCEnondcesvc(4)
