X-Git-Url: http://www.git.cypherpunks.ru/?p=nncp.git;a=blobdiff_plain;f=doc%2Fadmin.texi;h=e17c136644bd8e68868a1d3751bd183e15cc70eb;hp=8c46a681cd47483b4774ab9ba1289a957d2a94d3;hb=203dfe36da7adf2b3089e4fa4017a67409cbad70;hpb=205976b511d29cd6376c71049d86f7bafc609a53 diff --git a/doc/admin.texi b/doc/admin.texi index 8c46a68..e17c136 100644 --- a/doc/admin.texi +++ b/doc/admin.texi @@ -1,4 +1,5 @@ @node Administration +@cindex administration @unnumbered Administration NNCP uses following files/directories you should be aware of: @@ -20,11 +21,18 @@ NNCP uses following files/directories you should be aware of: 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. + @cindex shared spool + @cindex setgid + @pindex umask @anchor{Shared spool} If you want to share single spool directory with multiple grouped Unix users, then you can @command{setgid} it and assure that umask @@ -43,6 +51,7 @@ $ echo 'umask: "007"' >> /usr/local/etc/nncp.hjson @ref{Log} file, for example @file{/var/spool/nncp/log}. It should be rotated. Choose you own preferable way to do it. + @pindex newsyslog Example @url{https://www.newsyslog.org/manual.html, newsyslog}'s entry: @example /var/spool/nncp/log 644 7 100 * BCYN @@ -58,42 +67,70 @@ $ echo 'umask: "007"' >> /usr/local/etc/nncp.hjson */1 * * * * nncp-reass -all -noprogress @end example +@pindex daemontools +@pindex supervise +@pindex multilog @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 @verb{|uucp|} user: @example -# mkdir -p /var/service/nncp-toss/log -# chmod 755 /var/service/nncp-toss/log /var/service/nncp-toss -# cd /var/service/nncp-toss +# mkdir -p /var/service/.nncp-toss/log +# cd /var/service/.nncp-toss -# cat > run_ < run <&1 exec setuidgid uucp /usr/local/bin/nncp-toss -cycle 10 EOF -# chmod 755 run_ -# cat > log/run_ < log/run < run <&1 +EOF + +# cat > log/run <