...
| Info |
|---|
A good check that PAR is working as envisaged is when a normal user can execute OMK PAR exe scripts (other than those scripts that explicitly require execution by sudo with elevated permissions) and when there aren't any directories found of pattern /tmp/par-*/. (Assuming that environment variable "$PAR_GLOBAL_TMPDIR" points to an existing and user accessible directory). |
After the above changes, below is the PAR directory structure after executing ./omk/bin/patch_config.exe command as nmis, root then omkadmin. Each user gets their own accessible PAR directory structure:
| Code Block |
|---|
ls -lAth /usr/local/omk/var/lib/common/
drwx--S---. 3 omkadmin omkadmin 4.0K Jan 22 08:54 par-6f6d6b61646d696e
drwx--S---. 9 root omkadmin 4.0K Jan 22 08:52 par-726f6f74
drwx--S---. 3 nmis omkadmin 4.0K Jan 22 08:50 par-6e6d6973
# and /tmp/ is okay too:
sudo ls -lAth /tmp/par-*
ls: cannot access /tmp/par-*: No such file or directory |