Partly transferred files are stored with @file{.part} suffix. And
possibly they also require cleanup if they are completely lost.
- Also it can contain @file{.seen} files, that should be cleaned too
- from time to time.
+ It can contain @file{.nock} files: fully downloaded, but still not
+ checksummed. Can be checksummed (with @file{.nock} extension removing)
+ with @command{nncp-check -nock}.
+
+ Also it can contain @file{seen/} and @file{hdr/} subdirectories,
+ that should be cleaned too from time to time.
All of that cleaning tasks can be done with @ref{nncp-rm} utility.
@item
Possibly long running @ref{nncp-daemon}, @ref{nncp-caller},
- @ref{nncp-toss} daemons. As all software, they can fail and you
- should place them under some supervisor control.
+ @ref{nncp-toss}, @ref{nncp-check} daemons. As all software, they can
+ fail and you should place them under some supervisor control.
For example you can use @url{http://cr.yp.to/daemontools.html,
daemontools} for that task to run them under probably existing
@url{https://en.wikipedia.org/wiki/Inetd, inetd} service on UUCP's port:
@example
-uucp stream tcp6 nowait nncpuser /usr/local/bin/nncp-daemon nncp-daemon -quiet -inetd
+uucp stream tcp6 nowait nncpuser /usr/local/bin/nncp-daemon nncp-daemon -quiet -ucspi
@end example
@item
Or it can be also run as a @command{daemontools} daemon under
- @url{http://cr.yp.to/ucspi-tcp.html, UCSPI-TCP}:
+ @url{http://cr.yp.to/ucspi-tcp.html, UCSPI-TCP}. In the example
+ below it uses native daemontools's logging capability:
@example
# mkdir -p /var/service/.nncp-daemon/log
# cat > run <<EOF
#!/bin/sh -e
-exec envuidgid nncpuser tcpserver -DRHU -l 0 0 uucp \
- /usr/local/bin/nncp-daemon -quiet -inetd
+NNCPLOG=FD:4 exec envuidgid nncpuser tcpserver -DHRU -l 0 ::0 uucp \
+ /usr/local/bin/nncp-daemon -quiet -ucspi 4>&1
EOF
# cat > log/run <<EOF
#!/bin/sh -e
-exec setuidgid uucp multilog t ./main
+exec setuidgid uucp multilog ./main
EOF
# chmod -R 755 /var/service/.nncp-daemon