View Issue Details
| ID | Project | Category | View Status | Date Submitted | Last Update |
|---|---|---|---|---|---|
| 0001191 | OpenFOAM | Bug | public | 2014-02-26 09:44 | 2015-01-18 19:34 |
| Reporter | wyldckat | Assigned To | henry | ||
| Priority | low | Severity | minor | Reproducibility | N/A |
| Status | resolved | Resolution | fixed | ||
| Summary | 0001191: Somewhat dangerous symbolic link based infinite loop in tutorial "mesh/foamyHexMesh/mixerVessel" | ||||
| Description | There is a somewhat dangerous infinite loop in "tutorials/mesh/foamyHexMesh/mixerVessel/system/", where the sub-folders "backgroundMeshDecomposition" and "cellShapeControlMesh" are pointing to the local "system" folder. Although this may work just fine for "foamyHexMesh" and any other OpenFOAM applications, this could nonetheless break any other application that needs to check all folder contents and not take into account that such an occurrence can happen, namely that an infinite loop can exist in the file system. | ||||
| Tags | No tags attached. | ||||
|
|
It's unclear why "system/cellShapeControlMesh" is necessary. I could not find any evidence in the source code that anything is needed from this folder. If anything, it might be needed from the time folders, but not from the "system" folder. Therefore, the proposed fix for this report is to run the following commands from within the tutorial folder "mesh/foamyHexMesh/mixerVessel": unlink system/backgroundMeshDecomposition unlink system/cellShapeControlMesh mkdir system/backgroundMeshDecomposition ln -s ../decomposeParDict system/backgroundMeshDecomposition/decomposeParDict ln -s ../fvSchemes system/backgroundMeshDecomposition/fvSchemes ln -s ../fvSolution system/backgroundMeshDecomposition/fvSolution In addition, I tried to run "Allrun-pre" tutorial a few times to diagnose if this fix is all that is needed, but I was not able to get the same "log.foamyHexMesh" file for two runs for the original tutorial case folder, apparently because the meshing strategy depends enough on random numbers to not be able to reproduce the same output in two consecutive runs. |
|
|
Resolved by commit f7a485069c778495cc39b308580289f6c2d47163 |
