From: Sergey Matveev Date: Thu, 19 Jan 2017 20:27:35 +0000 (+0300) Subject: Rename nncp-newnode to nncp-newcfg for convenience and short name X-Git-Tag: 0.4^2~2 X-Git-Url: http://www.git.cypherpunks.su/?a=commitdiff_plain;h=679216fc7be93627a60499b7707310c1cd6e8d64;p=nncp.git Rename nncp-newnode to nncp-newcfg for convenience and short name --- diff --git a/common.mk b/common.mk index 0f7345e..c13ba52 100644 --- a/common.mk +++ b/common.mk @@ -26,7 +26,7 @@ ALL = \ nncp-freq \ nncp-log \ nncp-mincfg \ - nncp-newnode \ + nncp-newcfg \ nncp-pkt \ nncp-stat \ nncp-toss \ @@ -61,8 +61,8 @@ nncp-mail: nncp-mincfg: GOPATH=$(GOPATH) go build -ldflags "$(LDFLAGS)" cypherpunks.ru/nncp/cmd/nncp-mincfg -nncp-newnode: - GOPATH=$(GOPATH) go build -ldflags "$(LDFLAGS)" cypherpunks.ru/nncp/cmd/nncp-newnode +nncp-newcfg: + GOPATH=$(GOPATH) go build -ldflags "$(LDFLAGS)" cypherpunks.ru/nncp/cmd/nncp-newcfg nncp-pkt: GOPATH=$(GOPATH) go build -ldflags "$(LDFLAGS)" cypherpunks.ru/nncp/cmd/nncp-pkt diff --git a/doc/cmds.texi b/doc/cmds.texi index 2751006..42197da 100644 --- a/doc/cmds.texi +++ b/doc/cmds.texi @@ -178,15 +178,16 @@ spool}, path to log file, neighbours public keys are stayed. This is useful mainly for usage with @ref{nncp-xfer} that has to know only neighbours, without private keys involving. -@node nncp-newnode -@section nncp-newnode +@node nncp-newcfg +@section nncp-newcfg @verbatim -% nncp-newnode [options] > mynewnode.yaml +% nncp-newcfg [options] > new.yaml @end verbatim -Generate new node: private keys, example configuration file and print it -to stdout. You must use this command when you setup the new node. +Generate new node configuration: private keys, example configuration +file and print it to stdout. You must use this command when you setup +the new node. Pay attention that private keys generation consumes an entropy from your operating system. diff --git a/doc/workflow.texi b/doc/workflow.texi index 7803a78..5ec2c73 100644 --- a/doc/workflow.texi +++ b/doc/workflow.texi @@ -5,7 +5,7 @@ NNCP consists of several utilities. As a rule you will have the following workflow: @enumerate -@item Run @ref{nncp-newnode} on each node to create an initial +@item Run @ref{nncp-newcfg} on each node to create an initial @ref{Configuration, configuration} file. @item Tune it up and set at least @ref{Spool, spool} and log paths. @item Share your public keys and reachability addressees with your diff --git a/src/cypherpunks.ru/nncp/cmd/nncp-newnode/main.go b/src/cypherpunks.ru/nncp/cmd/nncp-newcfg/main.go similarity index 93% rename from src/cypherpunks.ru/nncp/cmd/nncp-newnode/main.go rename to src/cypherpunks.ru/nncp/cmd/nncp-newcfg/main.go index 080160b..cd36aa9 100644 --- a/src/cypherpunks.ru/nncp/cmd/nncp-newnode/main.go +++ b/src/cypherpunks.ru/nncp/cmd/nncp-newcfg/main.go @@ -16,7 +16,7 @@ You should have received a copy of the GNU General Public License along with this program. If not, see . */ -// Generate new NNCP node keys +// Generate new NNCP node keys and configuration file package main import ( @@ -30,7 +30,7 @@ import ( func usage() { fmt.Fprintf(os.Stderr, nncp.UsageHeader()) - fmt.Fprintln(os.Stderr, "nncp-newnode -- generate new node keys\nOptions:") + fmt.Fprintln(os.Stderr, "nncp-newcfg -- generate new configuration and keys\nOptions:") flag.PrintDefaults() }