jhelfman at e-e.com
Mon Sep 13 12:41:44 EDT 2010
On Sun, Sep 12, 2010 at 03:33:16AM -0400, Joe Marcus Clarke thus spake:
>On 9/10/10 2:34 PM, Jason Helfman wrote:
>> I need some TinderLove!
>> I am getting this error a lot:
>> list of filesystem changes from before and after all port
>> permissions expected 0644 found 0640
>> and this one too:
>> ===> Warning: your umask is "0027".
>> If this is not desired, set it to an appropriate value
>> and install this port again by ``make reinstall''.
>> The first error always results in an 'L' status, or leftover.
>> I believe that both of these can be solved by changing the umask, however I
>> am not sure what it should be, or recommended for tinderbox.
>> Whenever new logs, files/directories are created, they have permissions
>> aren't desirable for regular web access (love the interface!)
>> I was wondering how I may solve this, or how others setups are tackling
>> issue, or something similar.
>The default umask is 022, and that should be fine for TB builds. Run
>``umask'' and check the value as your build user (i.e. root).
If I log in as root and run umask I do get the value of 022 on the
buildhost. Is there something else I can do to diagnose if this value is
0027 is the value if I am on the buildhost and issue:
% sudo umask
The primary way we are submitting builds is via the web interface, and
tinderd is running as root to support this (one line):
root 75460 0.0 0.0 7100 1616 p0- I Thu09AM 0:07.47 /bin/sh
-T /usr/local/tinderbox/scripts/tinderd -nullfs
More information about the tinderbox-list