[distcc] Problem with zeroconf daemonization
Ihar `Philips` Filipau
thephilips at gmail.com
Mon Jan 18 03:29:48 MST 2010
About the magic constant.
What about getdtablesize() <
... but actually SUS advises to use the getrlimit(RLIMIT_NOFILE) in new
On Mon, Jan 18, 2010 at 7:10 AM, Benjamin R. Haskell <distcc at benizi.com>wrote:
> 'paludis' is a package manager for Gentoo Linux (and Exherbo). I sent
> an email to the 'paludis' users list about a problem with waiting for
> the distcc zeroconf daemon to stop.
> I use 'distcc -j' to set up my MAKEOPTS variable. The problem is with a
> wrapper used to prefix output for paludis with a tag indicating its
> origin. When using '+zeroconf' in DISTCC_HOSTS, paludis waits 20
> seconds for distcc unconditionally, because distcc doesn't close the
> extra file descriptors that are open due to this output munging. (So,
> 'paludis' waits on the grandchild daemon process that holds those fd's
> I stated in that message that I feel like this is a problem with the way
> distcc daemonizes (and not with the way paludis wraps output). I'm not
> as certain of that as I felt a couple hours ago, but it still feels
> accurate (that the daemonizing process has the responsibility to close
> any open fd's it's not going to use).
> If so, it seems like a pretty easy fix (to just close more fd's than 0,
> 1, and 2). I can commit the attached patch if 1024 doesn't seem too
> magic-number-y (and I'm not spouting nonsense).
> distcc mailing list http://distcc.samba.org/
> To unsubscribe or change options:
Don't walk behind me, I may not lead.
Don't walk in front of me, I may not follow.
Just walk beside me and be my friend.
-- Albert Camus (attributed to)
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the distcc