Closed Bug 407302 Opened 18 years ago Closed 18 years ago

Sisyphus - buildbot slave should use umask 002

Categories

(Testing Graveyard :: Sisyphus, defect)

Product:
Testing Graveyard
Component:
Sisyphus
Platform:
x86
Linux
Type:
defect
Priority:
Not set
Severity:
normal

Tracking

(Not tracked)

Status:
RESOLVED FIXED

People

(Reporter: bc, Assigned: rcampbell)

References

(
URL
)

Details

On qm-jstest01, new files are created with mode 600 since twistd forces umask to be 077. This cause problems for new files created by the slave since they are unreadable by the apache webserver. It appears we should use buildbot create-slave --umask=022 ... when creating the slave.
do we need to recreate the existing slave on jstest01?
I would assume so. Can you wait until the current shell run is completed to recreate it?
FWIW, you don't have to recreate it. Just change the 'umask' in buildbot.tac to 022
good catch. And easy! think a reconfig will be sufficient after that or do we need a restart? I'm betting on a restart...
Not sure, I'd do a restart though :)
I went ahead and edited the file on jstest01 and restarted the slave.
Status: NEW → RESOLVED
Closed: 18 years ago
Resolution: --- → FIXED
Mass move of Sisyphus bugs to Testing : Sisyphus. Filter on SisyphusMassMove to ignore.
Component: Testing → Sisyphus
Product: Core → Testing
QA Contact: testing → sisyphus
Product: Testing → Testing Graveyard
You need to log in before you can comment on or make changes to this bug.