@command{nncp-call} again, remote node will receive completion
notification.
-@option{-autotoss} options runs tosser on node's spool after call
-is finished. All @option{-autotoss-*} options is the same as in
+@option{-autotoss} option runs tosser on node's spool every second
+during the call. All @option{-autotoss-*} options is the same as in
@ref{nncp-toss} command.
@node nncp-caller
BLAKE2b hash output of their contents. That supplementary command is
not used often in practice, if ever.
+@node nncp-cronexpr
+@section nncp-cronexpr
+
+@example
+$ nncp-cronexpr -num 12 "*/1 * * * * SAT,SUN 2021"
+@end example
+
+Check validity of specified @ref{CronExpr, cron expression} and print 12
+next time entities.
+
@node nncp-daemon
@section nncp-daemon
uucp stream tcp6 nowait nncpuser /usr/local/bin/nncp-daemon nncp-daemon -quiet -inetd
@end verbatim
-@option{-autotoss} options runs tosser on node's spool after call
-is finished. All @option{-autotoss-*} options is the same as in
+@option{-autotoss} option runs tosser on node's spool every second
+during the call. All @option{-autotoss-*} options is the same as in
@ref{nncp-toss} command.
@node nncp-exec
If @option{-use-tmp} option is specified, then @code{stdin} data is read
into temporary file first, requiring twice more disk space, but no
memory requirements. @ref{StdinTmpFile, Same temporary file} rules
-applies as with @ref{nncp-file -} command.
+applies as with @ref{nncp-file, nncp-file -} command.
For example, if remote side has following configuration file for your
node: