1 – child
Deletes a child pointer from the namespace.
SYNOPSIS
DELETE CHILD child-name
ARGUMENTS
child-name
The full name of the child pointer.
NOTE
The delete child command should be used only when the directory
to which the child pointer refers has been deleted and the
child pointer accidentally remains.
ACCESS RIGHTS
You must have delete access to the directory in which the child
pointer is stored.
PRIVILEGES REQUIRED
You must have system administrator's privileges.
1.1 – example
The following command deletes the child pointer that accidentally remained after the .sales.east directory was deleted: dns> delete child .sales.east
2 – directory
Deletes a directory from the namespace. The directory must be empty
and the master replica must be the only remaining replica of it in
the namespace. Use the delete replica command if you need to remove
read-only replicas.
SYNOPSIS
DELETE DIRECTORY directory-name
Argument
directory-name
The full name of the directory.
ACCESS RIGHTS
You need write access to the clearinghouse that stores the master
replica of the directory and delete access to the directory itself.
2.1 – example
The following command deletes the .eng directory. dns> delete directory .eng
3 – dns
3.1 – clerk
Deletes the DECdns clerk on the specified node. You must disable a
clerk before you delete it (see the disable command). You can also
enter this command through the NCL interface.
SYNOPSIS
DELETE [NODE node-id] DNS CLERK
Argument
node-id
The name of the node. If you do not specify a node name, the local
node is assumed.
PRIVILEGES REQUIRED
You must have the NET$MANAGE rights identifier (VMS systems) or
superuser privileges (ULTRIX systems).
3.1.1 – example
The following command deletes a clerk running on node .mfg.umbriel. dns> delete node .mfg.umbriel dns clerk
3.1.2 – known_namespace
Removes a namespace from a specified clerk's list of known
namespaces.
SYNOPSIS
DELETE [NODE node-id] DNS CLERK
KNOWN NAMESPACE identifier
Arguments
node-id
The name of the node. If you do not specify a node name, the local
node is assumed.
identifier
The identifier of the namespace. This is a required argument. You
can use one of the following:
name The name of the namespace. The name argument may
be different from the nickname if the nickname is
ambiguous.
nscts The value of the namespace creation timestamp (NSCTS)
assigned to the specified namespace when it was
created. The format is 14 pairs of hex digits (xx-
xx).
NOTE
You are not permitted to delete the known namespace that is
currently the default namespace (that is, the one shown by show
dns clerk default namespace).
PRIVILEGES REQUIRED
You must have the NET$MANAGE rights identifier (VMS systems) or
superuser privileges (ULTRIX systems).
3.1.2.1 – example
The following command removes the namespace with the name jns from the clerk's list of known namespaces. dns> delete dns clerk known namespace jns
3.1.3 – manual_nameserver
Removes the knowledge of a server that exists across a WAN from the
local clerk's cache. You can also enter this command through the NCL
interface.
SYNOPSIS
DELETE [NODE node-id] DNS CLERK
MANUAL NAMESERVER name
Arguments
node-id
The name of the node on which the clerk exists. If you do not
specify a node name, the local node is assumed.
name
The simple name of the manual nameserver entity you want to delete.
PRIVILEGES REQUIRED
You must have the NET$MANAGE rights identifier (VMS systems) or
superuser privileges (ULTRIX systems).
3.1.3.1 – example
The following command removes knowledge of server nrl from the clerk cache on node .mfg.umbriel. dns> delete node .mfg.umbriel dns clerk manual nameserver nrl
3.2 – server
Deletes the DECdns server on the specified node and reclains all
server resources except clearinghouses, which remain. You must
disable a server before you can delete it. You can also enter
this command through the NCL interface.
SYNOPSIS
DELETE [NODE node-id] DNS SERVER
Argument
node-id
The name of the node. If you do not specify a node name, the local
node is assumed.
PRIVILEGES REQUIRED
You must have the NET$MANAGE rights identifier (VMS systems) or
superuser privileges (ULTRIX systems).
3.2.1 – example
The following command deletes the DECdns server from node .mfg.polaris. dns> delete node .mfg.polaris dns server
3.2.2 – clearinghouse
Deletes a clearinghouse on the specified node. You must disable a
clearinghouse before you can delete it. You can also enter this
command through the NCL interface. This command also automatically
deletes all read-only replicas from the clearinghouse when executed.
DECdns does not permit you to delete a clearinghouse that contains
a master replica.
SYNOPSIS
DELETE [NODE node-id] DNS SERVER CLEARINGHOUSE
clearinghouse-name
Arguments
node-id
The name of the node. If you do not specify a node name, the local
node is assumed.
clearinghouse-name
The full name of the clearinghouse.
ACCESS RIGHTS
You must have delete access to the directories in the clearinghouse
as well as to the clearinghouse.
PRIVILEGES REQUIRED
You must have the NET$MANAGE rights identifier (VMS systems) or
superuser privileges (ULTRIX systems).
3.2.2.1 – example
The following command deletes a clearinghouse named .sales.ny_ch from the node .sales.orion. dns> delete node .sales.orion dns server clearinghouse .sales.ny_ch
4 – group
Deletes a group from the namespace. The group does not have to be
empty to be deleted.
SYNOPSIS
DELETE GROUP group-name
Argument
group-name
The full name of the group.
ACCESS RIGHTS
You must have delete access to the group you are deleting.
4.1 – example
The following command deletes the group named .sales_group1 from the .sales directory: dns> delete group .sales.sales_group1
5 – link
Deletes a soft link.
SYNOPSIS
DELETE LINK link-name
Argument
link-name
The full name of the soft link.
ACCESS RIGHTS
You must have delete access to the soft link you want to delete.
5.1 – example
The following command deletes the soft link named .sales.asia. dns> delete link .sales.asia
6 – object
Deletes an object entry from the namespace. This task is usually
done through the client application that created the object entry,
except under specific circumstances (for example, if the application
is obsolete or no longer has access to the namespace).
SYNOPSIS
DELETE OBJECT object-name
Argument
object-name
The full name of the object entry.
ACCESS RIGHTS
You must have delete access to the object entry that you want to
delete.
6.1 – example
The following command deletes the object entry .floor1pr2 from the directory .sales.east. dns> delete object .sales.east.floor1pr2
7 – replica
Removes a replica of a directory from a clearinghouse. Use this
command to delete read-only replicas. Use the delete directory
command to delete the master replica and the entire directory.
SYNOPSIS
DELETE REPLICA directory-name [AT] CLEARINGHOUSE
clearinghouse-name
Arguments
directory-name
The full name of the directory.
clearinghouse-name
The full name of the clearinghouse.
ACCESS RIGHTS
You must have control access to the directory whose replica you
intend to delete, write access to the clearinghouse from which
you are deleting the replica, and write and delete access to the
directory's parent.
7.1 – example
The following command deletes a replica of the .mfg directory from the .paris1_ch clearinghouse. dns> delete replica .mfg at clearinghouse .paris1_ch
8 – subtree
Deletes a specified directory and its contents, or a hierarchy of
directories and their contents.
SYNOPSIS
DELETE SUBTREE tree-name[...]
[EXCLUDE DIRECTORY directory-name]
Argument
tree-name
The name of the topmost directory in the subtree. The recursion
notation causes the change to additionally apply to all child
directories and their contents. When used without the optional
recursion notation, the change applies only to the specified
directory. This then behaves just like the delete directory command
in that the directory must be empty to be deleted.
directory-name
The full name of a directory that you want to exclude from deletion.
When you exclude a directory, its parent directory is preserved.
Description
This command deletes the specified directory and its contents,
or a hierarchy of directories and their contents. Before using
this command, you must delete all read-only replicas and all
clearinghouse object entries in any of the affected directories.
You can use the optional recursion notation (...) to additionally
delete all child directories and their contents. The optional
exclude directory argument lets you specify one or more directories
to exclude from deletion. Multiple directories are specified in the
following format:
exclude directory directory-name, directory directory-name,
directory directory-name
ACCESS RIGHTS
You must have read, write, and delete access to the directory you
specify as well as the contents of the directory. If you use the
command recursively, you also need read, write, and delete access
to all child directories (and their contents) of the directory you
specify.
8.1 – example
The following command deletes the .pjl directory and its contents as well as all of its child directories and their contents. dns> delete subtree .pjl...