Custom Query (196 matches)

Every few hours, a server gets stuck in a state where certain users receive ENOENT from getcwd(), resulting in errors like

shell-init: error retrieving current directory: getcwd: cannot access parent directories: No such file or directory
job-working-directory: error retrieving current directory: getcwd: cannot access parent directories: No such file or directory
job-working-directory: error retrieving current directory: getcwd: cannot access parent directories: No such file or directory

Sometimes the problem goes away on its own, but usually the server needs to be rebooted.

I attempted to debug this with upstream on ​2013-06-11 and ​2013-06-16. Using crash, I found that we’re ending up with two dentries referring to the same directory inode, which is ​bad. We’re all confused.

This is complicated by the requirement to keep SSLSessionTicketKeyFile out of persistent storage, rotate it frequently, and synchronize it across servers. It would also be nice to remember the last N old keys so that each rotation doesn’t force every user to establish a new SSL session. We’ll probably need to do some Apache development.

​https://www.imperialviolet.org/2013/06/27/botchingpfs.html ​https://blog.twitter.com/2013/forward-secrecy-at-twitter-0

See ​http://b-m.mit.edu/__scripts/icons/ vs. ​http://b-b.mit.edu/__scripts/icons/ (for Apache directory indexes).