Custom Query (196 matches)
Results (124 - 126 of 196)
Ticket
|
Resolution
|
Summary
|
Owner
|
Reporter
|
#22 |
fixed
|
NFS-mounted /tmp is a bad idea
|
|
andersk
|
Description |
(Imported from help.mit.edu #432614.)
andersk:
While upgrading packages on scripts4, I received strange errors that I think can be attributed to our shared /tmp directory. We need to find a better solution. (This has made me uncomfortable for a long time, I'm just adding this to our todo list.)
andersk:
This is now one of ghudson's selling points for cobwebs:
http://scripts.mit.edu/~ghudson/blog/?p=13
so we should fix it as soon as possible. :-)
Here are some options I see:
- Keep the NFS solution and try to hack something to solve the failover problem.
- Unshare /tmp and stop pretending we only have one server.
- Unshare /tmp, but move PHP sessions and other similar data to some other shared directory (involving one of the other solutions).
- Put /tmp in AFS somewhere.
- Experiment with Coda, which I believe is supposed to support what we need.
Thoughts?
I think I'm happiest with either 2 or 3+5. Did we ever find specific examples of popular scripts that depend on a shared /tmp?
jbarnold:
I think that we previously found that some scripts cache data in /tmp, and they expect this data to be either not-there or entirely-up-to-date; they do not expect it to be in an old state.
I think that #2 might hard to get right.
I've considered putting /tmp into AFS, and that option might be the best one.
|
#25 |
fixed
|
document LVS so as not to confuse users and their code
|
|
andersk
|
Description |
(Imported from help.mit.edu #433591.)
|
#32 |
fixed
|
check for .htaccess files only inside ~/web_scripts
|
|
andersk
|
Description |
(Imported from help.mit.edu #546828.)
geofft:
You seem to have a .htaccess file in your home directory. This is unreadable by the scripts servers due to AFS permissions, and so Apache fails safe and denies all access to directories inside your home directory.
|
Note: See
TracQuery
for help on using queries.