LAE

Note: This was originally posted by an inactive account. Content was preserved by moving under an admin account.

Originally posted by: Brad Brezinski

We installed Lavastorm on new servers and now all our outputs files from publishing nodes are set to a permission of 640 which prevents us from moving the files. The owner is also listed as the account in which Lavastorm is installed. The users save outputs to their own directory on the Linux server. How do we ensure that files get output and saved with permissions of 777 or as owned by the destination directory? Thanks, Brad

Note: This was originally posted by an inactive account. Content was preserved by moving under an admin account.

Originally posted by: stonysmith

Set the "umask" for the application account in its ".profile" script (or in the LAE server startup script).
You'll have to make the change, and then log out/back in before restarting the server.

https://en.wikipedia.org/wiki/Umask

Note: This was originally posted by an inactive account. Content was preserved by moving under an admin account.

Originally posted by: Brad Brezinski

Hi, thanks Stony. To clarify, do we need a hardware restart or just restart the Lavastorm server? I made the umask update with "umask a+rw" to give me (u=rwx,g=rwx,o=rw) .... Hi5. Thanks, Brad

Note: This was originally posted by an inactive account. Content was preserved by moving under an admin account.

Originally posted by: Brad Brezinski

Actually, I may have done that wrong. I just went to /opt/app/p1lae1c1/Lavastorm/LAE6.1.4, used "umask -S" and got this status "u=rwx,g=rx,o=", I used "umask a+rw" to update and get the status of "u=rwx,g=rwx,o=rw". But, you mentioned that I was need to update umask in the LAE server startup script. To clariy, which file is the LAE start up script? To clarify, I'm not finding a umask in the .profile.lavastorm file. Thanks, Brad

Note: This was originally posted by an inactive account. Content was preserved by moving under an admin account.

Originally posted by: stonysmith

Add the umask command to .profile.lavastorm

Any time you change .profile.lavastorm, you need to stop the LAE server, sign off, and sign back in (to make sure the changes were kept) before you start the LAE server task.
I don't mean reboot the hardware.. you just need the LAE server task to see the change.

Note: This was originally posted by an inactive account. Content was preserved by moving under an admin account.

Originally posted by: Brad Brezinski

Thanks, to clarify, I can just update the last two rows of the .profile.lavastorm file to something like:

export INSTALL4J_ADD_VM_PARAMS="-Xmx1024M -XX:MaxPermSize=1024M"
umask 011
~
~

Note: This was originally posted by an inactive account. Content was preserved by moving under an admin account.

Originally posted by: Brad Brezinski

That work! Thanks, Brad