DISTRIBUTED-NET(1)
πΈ dnetc β distributed.net distributed computing client for Linux πΈ
okay bestie, sit down, hydrate, because we're about to talk about dnetc β the distributed computing client from distributed.net, living its best life on Linux. this is the DNETC(1) page, aka the distributed-net manpage, and it's genuinely iconic. let's go π
β¨ SYNOPSIS β¨
dnetc [-config] [-flush] [-fetch] [-update] [-benchmark [prj]]
[-benchmark2 [prj]] [-bench [prj [cn]]] [-test [prj [cn]]]
[-stress [prj [cn]]] [-cpuinfo] [-restart] [-shutdown] [-pause]
[-unpause] [-install [...]] [-uninstall] [-import <filename>]
[-forceunlock <fn>] [-help] [-version] [-ini <filename>] [-e
<address>] [-nodisk] [-n <count>] [-runbuffers] [-frequent]
[-inbase <fname>] [-outbase <fname>] [-ckpoint <fname>] [-bin
<prj> <n>] [-btime [prj] <n>] [-runoffline] [-runonline]
[-nettimeout <secs>] [-a <address>] [-p <port>] [-nofallback] [-u
<method>] [-ha <address>] [-hp <port>] [-lurk] [-lurkonly]
[-interfaces <list>] [-c [prj] <n>] [-numcpu <n>] [-devicenum <n>]
[-priority <0-9>] [-l <filename>] [-smtplen <len>] [-smtpsrvr
<host>] [-smtpport <port>] [-smtpfrom <id>] [-smtpdest <id>] [-h
<hours[:min]>] [-until <HH:MM>] [-noexitfilecheck] [-pausefile
<fn>] [-exitfile <fn>] [-multiok[=|:][0|1]] [-percentoff]
[-quiet/-hide] [-noquiet]
like, look at that. a whole buffet of flags. we love a client with range π
π¦ DESCRIPTION π¦
dnetc is a distributed computing client that coordinates with servers operated by distributed.net so that it can team up with other network-connected computers and grind on a common task together. it talks over public networks and processes work that the distributed.net keyservers hand out. it's built to run in idle time, so it does not impact the normal operation of your computer. it's giving polite houseguest. it's giving "i'll just use the leftovers of your CPU, no biggie." π
π INSTALLATION π
since you're already reading this, the author assumes you know how to unpack an archive into a directory of your choice. :) and honestly? yeah. you got this.
now, simply fire up the client...
if you've never run the client before, it will kick off the menu-driven configuration. save and quit when you're done, and the configuration file gets saved in the same directory as the client. then just restart the client. from that point on it uses the saved config. set it and forget it, queen. β¨
the configuration options are fairly self-explanatory and can be run at any time by starting the client with the -config option. a list of command line options is listed below. (spoiler: it's a lot. and we're covering every single one. no skips.) π«Ά
π OPTIONS π
in addition to the conventional command line passed to the client from a shell, options may also be passed to the client using either or both of the following methods:
- using the
dnetc_opt=environment variable. if set, this is parsed before the normal command line. - using the
//etc/distributed-net.confcommand files. if found, these are parsed after the normal command line.
okay important!! "Mode commands" (see below) cannot be executed using these methods, and there is no run-time display of modified settings β unless the settings are also modified using the conventional command line, in which case the last effective change is displayed. so like, don't @ me when your mode command silently does nothing through the config file. it's not a bug, it's a boundary. π
β Mode commands: (the client will execute the option and then exit)
-configβ start the configuration menu-flushβ flush all output buffers-fetchβ fill all input buffers-updateβ fetch + flush-benchmark [prj]β 16-20 sec speed check [optional: only project prj]-benchmark2 [prj]β half (8-10 sec) and slightly inaccurate-benchmark-bench [prj [cn]β-benchmarkall cores [optional: only project prj] [optional: only core cn, must be used with prj]-test [prj [cn]β tests for core errors [optional: only project prj] [optional: only core cn, must be used with prj]-stress [prj [cn]]β more thorough and longer running variant of-test-cpuinfoβ print information about the detected cpu(s)-restartβ restart all active clients-shutdownβ gracefully shut down all active clients-pauseβ pause all active clients-unpauseβ unpause all active clients-install [...]β install the client in/etc[/rc.d]/init.d/. all[...options...]that follow-installserve as parameters for the installed client.-uninstallβ remove the client from/etc[/rc.d]/init.d/-import <filename>β import packets from file <filename> into client buffers-forceunlock <fn>β unlock buffer file <fn>-helpβ display this text-versionβ print version information
π Project and buffer related options:
-ini <filename>β override default name of INI file-e <address>β the email id by which you are known to distributed.net-nodiskβ don't use disk buffer files-n <count>β packets to complete.-1forces exit when buffer is empty.-runbuffersβ set-n == -1(exit when buffers are empty)-frequentβ frequently check if buffers need topping-up-inbase <fname>β input buffer basename (ie without 'extension'/suffix)-outbase <fname>β output buffer basename (ie without 'extension'/suffix)-ckpoint <fname>β set the name of the checkpoint file-bin <prj> <n>β set fetch buffer threshold to <n> work units-btime [prj <n>]β set fetch time threshold to <n> hours. if not specified, project name <prj> defaults toRC5
π¦ Network update related options:
-runofflineβ disable network access-runonlineβ enable network access-nettimeout <secs>β set the network timeout. use-1to force blocking mode-a <address>β keyserver name or IP address-p <port>β keyserver port number-nofallbackβ don't fallback to a distributed.net keyserver-u <method>β use this UUE/HTTP encoding method (see-config)-ha <address>β http/socks proxy name or IP address-hp <port>β http/socks proxy port-lurkβ automatically detect modem connections-lurkonlyβ perform buffer updates only when a connection is detected-interfaces <list>β limit the interfaces to monitor for online/offline status
π₯ Performance related options:
-c [prj <n>]β core number (run-configfor a list of valid core numbers). project name 'prj' defaults toRC5-numcpu <n>β run <n> threads/run on <n> cpus.0forces single-threading.-devicenum <n>β run on device <n> only.-priority <0-9>β scheduling priority from0(lowest/idle) to9(normal/user)
π Logging options:
-l <filename>β name of the log file-smtplen <len>β max size (in bytes) of a mail message (0means no mail)-smtpsrvr <host>β name or IP address of mail (SMTP) server-smtpport <port>β mail (SMTP) server port number-smtpfrom <id>β who the client should say is sending the message-smtpdest <id>β who the client should send mail to
π§ Miscellaneous runtime options:
-h <hours[:min]>β time limit in hours-until <HH:MM>β quit atHH:MM(eg07:30)-noexitfilecheckβ override.iniexit flagfile setting-pausefile <fn>β name of file that causes the client to pause-exitfile <fn>β name of file that causes the client to exit-multiok[=|:][0|1]β allow/disallow multiple instances of the client to run. the default is'allow'for all platforms but Windows.-percentoffβ don't display work completion as a running percentage-quiet/-hideβ suppress screen output (== detach for some clients)-noquietβ don't suppress screen output (override ini quiet setting)
π BUGS π
distributed.net maintains a database to assist with the tracking and resolution of bugs in dnetc and related software.
if you believe you have found a bug, please submit it to the distributed.net bug tracking database at http://bugs.distributed.net/
bestie, pls pls pls β when you do that, provide the entire version descriptor as displayed on client start. for example, the client version this manpage was generated for was "dnetc v2.9112-521-CFR-16020313 for Linux". they need it. it's the receipts. π§Ύ
πΈ ENVIRONMENT πΈ
dnetc_opt(or the upper-case version thereof) β additional source of command line options (parsed first)
π FILES π
/etc/distributed-net.confβ additional sources of command line options (parsed last)
π SEE ALSO π
Client documentation: dnetc.txt and http://faq.distributed.net/
β AUTHOR β
distributed.net http://www.distributed.net/
aaaand that's the whole page, no cap. this version of the manpage dropped Wed Feb 3 16:09:14 2016 and it's filed under DNETC(1) from the distributed.net crew. go forth and crunch some work units, you gorgeous little CPU whisperer π«Άπβ¨
π¦ where this page comes from
- debian bookworm: distributed-net 2.9112.521+arm64-3
- debian trixie: distributed-net 2.9112.521+arm64-3
- ubuntu jammy: distributed-net 2.9112.521+arm64-2
- ubuntu noble: distributed-net 2.9112.521+arm64-3
- ubuntu questing: distributed-net 2.9112.521+arm64-3
- ubuntu resolute: distributed-net 2.9112.521+arm64-3build1
- Copyright (c) 1996-2016 distributed.net. All rights reserved
- π girlified by deepseek-ai/DeepSeek-V4.1-Flash on : a language model's rewrite of the original, under its terms