Caches and prefers existing .junest/etc/passwd and group files
Before this fix it was possible that concurrent startup (as in multiple junest processes) lead to partial files for some of the junest processes.
This is a quick fix removing the bug and speeding up startup. There are however a couple of issues that more experienced junest members should look into:
[ ] are there other shared files that could cause concurrency issues between multiple junest invocations? I didn't find any, but please check.
[ ] caching always comes at the cost of outdated info... in theory it is possible that the system's passwd and group info change. This will however not happen on each normal junest user startup, which is the rational for my fix. It might however be desirable to allow a user to manually reset such caches. Docs should point out that such calls shouldn't be parallelized though.
Caches and prefers existing .junest/etc/passwd and group files
Before this fix it was possible that concurrent startup (as in multiple junest processes) lead to partial files for some of the junest processes.
This is a quick fix removing the bug and speeding up startup. There are however a couple of issues that more experienced junest members should look into:
passwdandgroupinfo change. This will however not happen on each normal junest user startup, which is the rational for my fix. It might however be desirable to allow a user to manually reset such caches. Docs should point out that such calls shouldn't be parallelized though.