Slow workspace startup caused by chmod
See original GitHub issuePlease could someone kindly explain what the purpose of this chmod line in the ws-agent startup is?
find /projects -type d -exec ${SUDO} chmod 755 {} \;
We run on EBS so IO is not as good as local and with our very large projects, this can take some time to complete making WS startup slow.
Why do all workspace sub directories need to be 755 and have that done to them on every startup?
Issue Analytics
- State:
- Created 6 years ago
- Comments:10 (4 by maintainers)
Top Results From Across the Web
How can you speed up Eclipse? - Stack Overflow
Go to Windows -> Preferences -> Validation and uncheck any validators you don't want or need. For Eclipse 3.7, you use Windows ->...
Read more >Slow startup opening a large workspace over the network
My workspace directory sits on a server in the network, which I access using a mapped network drive. It has about 470,000 files...
Read more >Docker extremely slow, on linux and windows
Hi guys, I was working with Docker on a Win11 machine and the application run very very slow, around 30 seconds or even...
Read more >- chmod()
The chmod() function changes S_ISUID, S_ISGID, S_ISVTX and the file permission bits of the file specified by the pathname pointed to by path...
Read more >Troubleshooting SSH errors - Compute Engine - Google Cloud
Use the SSH troubleshooting tool to help determine why an SSH connection failed. The troubleshooting tool performs the following tests to check for...
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
chmod removed
@adoukkali I think I’ll issue a pr that will add a check to run chown only if there’s a real need to do so