5 $ nncp-exec [options] [-use-tmp] [-nocompress] NODE HANDLE [ARG0 ARG1 ...]
6 $ nncp-exec [options] [-use-tmp] [-nocompress] area:AREA HANDLE [ARG0 ARG1 ...]
9 Send execution command to @option{NODE} for specified @option{HANDLE}.
10 Body is read from @code{stdin} into memory and compressed (unless
11 @option{-nocompress} is specified). After receiving, remote side will
12 execute specified @ref{CfgExec, handle} command with @option{ARG*}
13 appended and decompressed body fed to command's @code{stdin}.
15 If @option{-use-tmp} option is specified, then @code{stdin} data is read
16 into temporary file first, requiring twice more disk space, but no
17 memory requirements. @ref{StdinTmpFile, Same temporary file} rules
18 applies as with @ref{nncp-file, nncp-file -} command.
20 For example, if remote side has following configuration file for your
25 sendmail: [/usr/sbin/sendmail, "-t"]
26 appender: ["/bin/sh", "-c", "cat >> /append"]
30 then executing @verb{|echo My message | nncp-exec -replynice 123 REMOTE
31 sendmail root@localhost|} will lead to execution of:
36 NNCP_SENDER=OurNodeId \
38 /usr/sbin/sendmail -t root@@localhost
41 If @ref{CfgNotify, notification} is enabled on the remote side for exec
42 handles, then it will sent simple letter after successful command
43 execution with its output in message body.
45 @strong{Pay attention} that packet generated with this command won't be
48 If you use @option{area:AREA} instead of @option{NODE}, then
49 @ref{Multicast, multicast} packet will be sent to specified area. That
50 creates outgoing packet to the @strong{self} node, so you have to run
51 @ref{nncp-toss, tossing} to create outgoing packets to required subscribers.