$ nncp-file [options] [-chunked INT] SRC NODE:[DST] $ nncp-file [options] [-chunked INT] SRC area:AREA:[DST]
Send SRC file to remote NODE. DST specifies destination file name in remote’s incoming directory. If this file already exists there, then counter will be appended to it.
This command queues file in spool directory immediately – so pay attention that sending 2 GiB file will create 2 GiB outbound encrypted packet.
If SRC equals to -, to data is read from
If SRC points to directory, then
will be created on the fly with directory contents and destination
filename .tar appended. It won’t contain any entities
metainformation, but modification time with the names. UID/GID are set
to zero. Directories have 777 permissions, files have 666, for being
umask. Also each entity will have comment like
Autogenerated by NNCP version X.Y.Z built with goXXX.
If -chunked is specified, then source file will be split on chunks. INT is the desired chunk size in KiBs. This mode is more CPU hungry. Pay attention that chunk is saved in spool directory immediately and it is not deleted if any error occurs. -minsize option is applied per each chunk. Do not forget about possible ZFS deduplication issues. Zero -chunked disables chunked transmission.
If notification is enabled on the remote side for file transmissions, then it will sent simple letter after successful file receiving.
If you use area:AREA instead of NODE, then multicast packet will be sent to specified area. That creates outgoing packet to the self node, so you have to run tossing to create outgoing packets to required subscribers.