Recently bumped once again into "misc/58117: installworld /tmp/ problem". Would it be better to solve it at "once and for all" basis? This is a good choice for securing servers to make /tmp noexec. But when you did that - you'll have to face this bug again. Yes, it can be solved by specifying TMPDIR. But: - UPDATING says nothing about that; - nor documentation do; - the message is kindda cryptic and it takes time to understand whats going on. Why not document the issue or prevent it by using custom catalog? -- Sphinx of black quartz judge my vow!Received on Wed Jun 13 2007 - 20:05:39 UTC
This archive was generated by hypermail 2.4.0 : Wed May 19 2021 - 11:39:12 UTC