public inbox for gentoo-user@lists.gentoo.org
 help / color / mirror / Atom feed
From: Jorge Almeida <jjalmeida@gmail.com>
To: gentoo-user@lists.gentoo.org
Subject: [gentoo-user] distccd offspring
Date: Mon, 16 Dec 2024 17:11:24 +0000	[thread overview]
Message-ID: <CAKpSnpLH_8inuUqosiOG0G_iObV-siuL=oLoziLxNPuMTDMBSw@mail.gmail.com> (raw)

[-- Attachment #1: Type: text/plain, Size: 1045 bytes --]

I have this in the output of "ps axf"

  532 ?        SN     0:00  \_ /usr/bin/distccd --user distcc --daemon
--no-detach --log-stderr --log-level notice --port 3632 --listen
192.168.1.131 --allow 192.168.1.128
  536 ?        SN     0:00  |   \_ /usr/bin/distccd --user distcc --daemon
--no-detach --log-stderr --log-level notice --port 3632 --listen
192.168.1.131 --allow 192.168.1.128

Process 532 is what it is supposed to be. But why the child 536? Not to
mention 17 more children just like 536, which I didn't paste.
The distccd daemon is alive but not really working, as it has nothing to
do: I use this about once  a week (for world updating, eventually kernel
compiling), and today the 192.168.1.128 client is not even on. I checked
the distccd log, nothing there. The connection is by ethernet cable.
distccd works just fine when required to.

So, what could lead it to spawn so many useless children? I couldn't find
anything in the manual, and googling doesn't seem to help.


Any distcc user in the same boat?

Thanks

Jorge Almeida

[-- Attachment #2: Type: text/html, Size: 1281 bytes --]

             reply	other threads:[~2024-12-16 17:11 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-12-16 17:11 Jorge Almeida [this message]
2024-12-17  8:18 ` [gentoo-user] distccd offspring netfab
2024-12-17 10:02   ` Jorge Almeida
2024-12-17 10:16     ` netfab
2024-12-17 10:46       ` Jorge Almeida
2024-12-17  8:26 ` William Kenworthy
2024-12-17  8:34   ` Alexandru N. Barloiu
2024-12-17 10:08     ` Jorge Almeida

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to='CAKpSnpLH_8inuUqosiOG0G_iObV-siuL=oLoziLxNPuMTDMBSw@mail.gmail.com' \
    --to=jjalmeida@gmail.com \
    --cc=gentoo-user@lists.gentoo.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox