djhoese
commented
2 years ago @jpnIII As mentioned in my email, the installation process for Geo2Grid requires the "installing" account to perform some operation (ex. run geo2grid.sh -h) at least once before any other user can execute any commands. The one-time install process (potentially) requires write permission to the entire extracted directory. It may not need it in the current revision, but may in the future depending on what packages are installed in the bundle. It at least needs permission to create a file in one specific location inside the directory. Lastly, in my own tests even though it complains about conda-unpack it seems to still continue executing.
Could you please remove the extracted directory for 1.1beta, re-extract it, run geo2grid.sh -h, and then have Tim try executing code. In general Geo2Grid was not designed/tested to be used by multiple users, but besides this one-time installation step of running any command, it shouldn't not be possible.
As for the files you've listed that you think should have changed permissions, none of those have executable permissions (except conda-unpack) because they aren't meant to be called directly. Conda-unpack does have execute permissions for all (user, group, other) but not read permissions for group/other, but it doesn't need read permissions. It is executed directly by my initialization scripts. So what I'm saying is I think the permissions are fine the way they are, we (the Geo2Grid team) just need to document that geo2grid.sh -h should be run by the installing user before any other users try to work with the scripts.
jpnIII
Hi all -- Dave is already familiar with this problem, but I had not filed an issue on it, as Dave had requested. Sorry Dave. So for accounting purposes, here is my issue:
After unpacking and setting up Geo2Grid release 1.1.beta as user "gops" on imaginator.ssec.wisc.edu, another user on imaginator ("tims") tried to execute geo2grid.sh (Tim just adjusted his $PATH via a ksh alias to have the proper Geo2Grid bin file included). Tim then ran into the following problem:
python: can't open file '/home/shared/bin/geo2grid_v_1_1_b/geo2grid-swbundle-20220308-201316/libexec/python_runtime/bin/conda-un pack': [Errno 13] Permission denied
I thought that this was a very strange set of permissions for a file to have, so I ran: chmod 755 conda-unpack
Tim is now able to run the Geo2Grid package.
Truthfully, I do not recall the order of steps taken to allow Tim to execute the 1.1.beta Geo2Grid. I have reason to believe though that changing permissions for activate, deactivate and ksu had no effect on the situation. I guess I would say that the bottom line would be that all of the files in the bin directory (especially conda-unpack, activate, deactivate and ksu) should have the same permissions as all of the other files (rwxr-xr-x). I think that would be cleaner.