Welcome to Linux Knowledge Base and Tutorial
"The place where you learn linux"
Bread for the World

 Create an AccountHome | Submit News | Your Account  

Tutorial Menu
Linux Tutorial Home
Table of Contents

· Introduction to Operating Systems
· Linux Basics
· Working with the System
· Shells and Utilities
· Editing Files
· Basic Administration
· The Operating System
· The X Windowing System
· The Computer Itself
· Networking
· System Monitoring
· Solving Problems
· Security
· Installing and Upgrading
· Linux and Windows

Man Pages
Linux Topics
Test Your Knowledge

Site Menu
Site Map
Copyright Info
Terms of Use
Privacy Info
Masthead / Impressum
Your Account

Private Messages

News Archive
Submit News
User Articles
Web Links


The Web

Who's Online
There are currently, 79 guest(s) and 0 member(s) that are online.

You are an Anonymous user. You can register for free by clicking here




       distccd --daemon [OPTIONS]


       distccd  is  the server for the distcc(1) distributed com­
       piler.  It accepts and runs compilation jobs  for  network

       distcc  can  run  over  either TCP or a connection command
       such as ssh(1).  TCP connections are fast  but  relatively
       insecure.  SSH connections are secure but slower.

       For SSH connections, distccd must be installed on the vol­
       unteer but should not run  as  a  daemon  --  it  will  be
       started  over SSH as needed.  SSH connections have several
       advantages: neither the client nor server listens  on  any
       new  ports;  compilations  run  with the privileges of the
       user that requested them; unauthorized users cannot access
       the server; and source and output is protected in transit.

       For TCP connections, distccd can run either from an inetd-
       style program, or as a standalone server.  Standalone mode
       is recommended because it is slightly more  efficient  and
       allows  distccd  to  regulate the number of incoming jobs.
       The --listen and --allow options can be  used  for  simple
       IP-based access control.

       distcc  may  be  started either by root or any other user.
       If run by root, it gives away privileges  and  changes  to
       the  user  specified  by  the  --user  option, or the user
       called "distcc", or the user called "nobody".

       distccd does not have a configuration file; it's behaviour
       is  controlled  only  by command-line options and requests
       from clients.


       The recommended method for running distccd is as  a  stan­
       dalone  server.   distccd  will listen for network connec­
       tions and fork several child processes to serve them.

       If you installed distcc using a packaged version  you  may
       be  able  to start the server using the standard mechanism
       for your operating system, such as

              # service distcc start

       To start distccd as a standalone service,  run  a  command
       like this either as root or an ordinary user:

              # distccd --daemon

              --no-detach --daemon


       distccd may be started from a network super-server such as
       inetd  or  xinetd.  In this case inetd listens for network
       connections and invokes distccd when one arrives.

       This is slightly less efficient than running a  standalone
       distccd  daemon.  distccd is not able to regulate the num­
       ber of concurrent jobs  accepted,  but  there  may  be  an
       option in your inetd configuration to do so.

       For  traditional Unix inetd, a line like this can be added
       to /etc/inetd.conf:

              distcc     stream     tcp     nowait.6000      root
              /usr/local/bin/distccd distccd --inetd

       inetd imposes a limit on the rate of connections to a ser­
       vice to protect against accidental or intentional overuse.
       The  default in Linux NetKit inetd is 40 per minute, which
       is far  too low for distccd.  The .6000 option raises  the
       limit to 6000 per minute.


       To shut down a standalone server, send a SIGTERM signal to
       the parent process.  The most reliable way to do this from
       a  script  is  to  use the --pid-file option to record its
       process ID.  Shutting down the server in this  way  should
       allow any jobs currently in progress to complete.


       --help Display summary usage information.

              Shows the daemon version and exits.

       -j, --jobs JOBS
              Sets  a  limit  on  the  number of jobs that can be
              accepted at any time.  By default this  is  set  to
              two greater than the number of CPUs on the machine,
              to allow for some processes being blocked  on  net­
              work IO.  (Daemon mode only.)

       -N, --nice NICENESS
              Makes  the daemon more nice about giving up the CPU
              to other tasks on  the  machine.   NICENESS  is  an
              increment  to  the current priority of the process.
              The range of priorities depends  on  the  operating
              system  but  is  typically 0 to 20.  By default the
              niceness is increased by 5.

              If distccd gets executed as root,  change  to  user

       -a, --allow IPADDR[/MASK]
              Instructs  distccd to only accepts connections from
              the IP address IPADDR.  A CIDR mask length  can  be
              supplied  optionally  after  a trailing slash, e.g.

              Include debug messages in log.

              Do not detach from the shell that started the  dae­

              Don't  fork  children for each connection, to allow
              attaching gdb.  Don't use this if you don't  under­
              stand it!

       --log-file FILE
              Send messages to file FILE instead of syslog.  Log­
              ging directly to a  file  is  significantly  faster
              than going via syslog and is recommended.

              Send  log messages to stderr, rather than to a file
              or syslog.  This is  mainly  intended  for  use  in
              debugging.  Do not use in inetd mode.

              Turn   on  all  options  appropriate  for  starting
              distccd under gdb: run as a daemon,  log  verbosely
              to  stderr, and do not detach or fork.  For wizards

              Serve a client connected to stdin/stdout.   As  the
              name  suggests,  this  option  should  be used when
              distccd is run  from  within  a  super-server  like
              inetd.   distccd assumes inetd mode when stdin is a

              Bind and listen on a socket,  rather  than  running
              from  inetd.   This  is  used  for standalone mode.
              distccd assumes daemon mode at startup if stdin  is
              a  tty,  so --daemon should be explicitly specified
              when starting distccd from a script or  in  a  non-
              interactive ssh connection.

              most people want to use ccache before distcc.

              If set to 1, temporary files are not deleted  after

       Note  that  DISTCC_LOG does not affect the log destination
       for the server.


       distcc(1),        ccache(1),        gcc(1),        make(1)


       IP-based  access  control  is not secure against attackers
       able to spoof TCP  connections,  and  cannot  discriminate
       different users on a client.

       TCP  connections  are not secure against attackers able to
       observe or modify network traffic.


       You are free to use distcc.  It may be copied, modified or
       distributed only under the terms of the GNU General Public
       Licence version 2 or later.  A copy of the GPL is included
       in the file COPYING.


       distcc  was  written  by Martin Pool <mbp@sourcefrog.net>,
       with the co-operation of  many  scholars  including  Wayne
       Davison,  Frerich  Raabe,  Dimitri Papadopoulos and others
       noted  in  the  NEWS  file.    Please   report   bugs   to

                           21 July 2003                distccd(1)

The Linux Tutorial is always looking for new contributors.



Security Code
Security Code
Type Security Code

Don't have an account yet? You can create one. As a registered user you have some advantages like theme manager, comments configuration and post comments with your name.

Help if you can!

Amazon Wish List

Did You Know?
The Linux Tutorial can use your help.


Tell a Friend About Us

Bookmark and Share

Web site powered by PHP-Nuke

Is this information useful? At the very least you can help by spreading the word to your favorite newsgroups, mailing lists and forums.
All logos and trademarks in this site are property of their respective owner. The comments are property of their posters. Articles are the property of their respective owners. Unless otherwise stated in the body of the article, article content (C) 1994-2013 by James Mohr. All rights reserved. The stylized page/paper, as well as the terms "The Linux Tutorial", "The Linux Server Tutorial", "The Linux Knowledge Base and Tutorial" and "The place where you learn Linux" are service marks of James Mohr. All rights reserved.
The Linux Knowledge Base and Tutorial may contain links to sites on the Internet, which are owned and operated by third parties. The Linux Tutorial is not responsible for the content of any such third-party site. By viewing/utilizing this web site, you have agreed to our disclaimer, terms of use and privacy policy. Use of automated download software ("harvesters") such as wget, httrack, etc. causes the site to quickly exceed its bandwidth limitation and are therefore expressly prohibited. For more details on this, take a look here

PHP-Nuke Copyright © 2004 by Francisco Burzi. This is free software, and you may redistribute it under the GPL. PHP-Nuke comes with absolutely no warranty, for details, see the license.
Page Generation: 0.09 Seconds