aboutsummaryrefslogtreecommitdiff
path: root/tex/delete-me.tex
diff options
context:
space:
mode:
authorBoud Roukema <boud@cosmo.torun.pl>2021-06-24 21:19:38 +0200
committerMohammad Akhlaghi <mohammad@akhlaghi.org>2021-06-25 19:20:02 +0100
commit016d938cec703a6d0062377ae8001c8bc7532073 (patch)
treea341c9b2fbb184035834ed3b6ea7b1c3b099e6e2 /tex/delete-me.tex
parentb97c1ff34c8ad62719cf0eb41c3dfa4d7c76ab26 (diff)
Configuration: New check to see if /dev/shm allows execution
On systems that allow it (like GNU/Linux systems), Maneage will build the necessary software in shared memory (a directory that is actually in the RAM, not on an SSD/HDD, on GNU/Linux systems, it is '/dev/shm'). This allows Maneage to operate faster and not harm the HDD/SSD with all the temporary writing of many small files. Until now, we would only check that this directory exists and that it has enough space. However, some systems also set the 'noexec' flag on shared memory for security reasons [1]. This causes Maneage to crash upon building of the software in later phases. With this commit, at the very start of the configuration step, and after all other shared-memory checks are done, a dummy executable script file is created there and its execution is tested. If it doesn't work, shared memory will not be used at all. In the process, the steps dealing with the software building directory in the configure script have been brought in one place and comments were added to further clarify every step. This commit was initially done by Boud Roukema and later edited by Mohammad Akhlaghi. [1] https://web.archive.org/web/20210624192819/https://serverfault.com/questions/72356/how-useful-is-mounting-tmp-noexec
Diffstat (limited to 'tex/delete-me.tex')
0 files changed, 0 insertions, 0 deletions