dncopynodes(8) [debian man page]

DNCOPYNODES(8)						      System Manager's Manual						    DNCOPYNODES(8)

NAME

       dncopynodes - copy a list of nodes from a remote DEC system

SYNOPSIS

       dncopynodes <nodename> [ldif-dn]

DESCRIPTION

       This  program will generate a decnet.conf file by contacting a remote DECnet host (running VMS or RSX-11 probably) and doing the equivalent
       of "NCP COPY KNOWN NODES". The resulting file can be copied over the existing decnet.conf file if you like.
       You do need a fully-functioning DECnet system before using this command but you don't need any nodes other than	the  executor  defined	in
       decnet.conf.  dncopynodes will copy the executor information already there into the new file.
       The  program  copies  its  output  to standard output. It is strongly recommended that you review it before replacing an existing /etc/dec-
       net.conf file.
       The node name can also be a node address if you don't have any nodes defined in your existing decnet.conf.
       DO NOT attempt to redirect the output of dncopynodes directly into /etc/decnet.conf. It will fail and destroy your  existing  configuration
       file! Send it to a temporary file and then copy it (see EXAMPLES)
       dncopynodes  can  also  create  an  LDIF file suitable for importing into an LDAP database. With dnprogs 2.48 or later, DECnet programs can
       quiry this for node address information.

EXAMPLE

       # dncopynodes 3.34 > /tmp/decnet.conf
       # dncopynodes 3.34 dc=example,dc=com > /tmp/decnet.ldif
       # mv /tmp/decnet.conf /etc

SEE ALSO

       decnet.conf(5), setether(8)

DECnet utilities						 September 03 2008						    DNCOPYNODES(8)

DNETNML(8)						      System Manager's Manual							DNETNML(8)

NAME

       dnetnml - DECnet Network Management Listener

SYNOPSIS

       dnetnml [options]
       Options:
       [-dVh]

DESCRIPTION

       dnetnml is a daemon that serves incoming management requests from remote systems, usually NCP in the case of VMS and RSX. It is recommended
       that the daemon be run from dnetd by adding the following line to /etc/dnetd.conf:
       NML	      19	 N	   nobody	dnetnml

       Currently it only serves a subset of information requests. These are (in NCP terms):
       SHOW KNOWN NODES
       SHOW ADJACENT NODES
       SHOW EXEC CHAR
       SHOW KNOWN OBJECTS
       SHOW KNOWN LINKS
       Note that for SHOW KNOWN OBJECTS to work, /etc/dnetd.conf needs to be readable by the daemon user (usually 'nobody') or it  will  return  a
       Privilege  Violation.  There  is  no  sensitive	data  in this file so it's quite OK to set the permissions to 0644. Though this is not the
       default.

OPTIONS

       -d     Don't fork and run the background. Use this for debugging.

       -v     Verbose. The more of these there are the more verbose dnetnml will be. Don't use more than one for normal operation because it  will
	      seriously impair performance.

       -h -?  Displays help for using the command.

       -V     Show the version of dnetnml.

BUGS

       Probably lots, particularly as some of the functions are undocumented and I've had to reverse-engineer them.  SHOW KNOWN LINKS doesn't show
       quite the same information as VMS does. dnetnml relies on the information it can get from /proc/net/decnet so it can't show  load  PIDs	or
       processes unfortunately.

SEE ALSO

       dnetd(8), dnetd.conf(5)

DECnet utilities						 September 5 2008							DNETNML(8)