Skip to main content
Known Participant
June 3, 2011
Question

FMS 4 log permissions defaults

  • June 3, 2011
  • 1 reply
  • 626 views

We had an issue today with a new installation of FMS4, where we have developers in the group "fms" which allows them to view logs.   It turns out, FMS is creating logs in mode 0666, but it's also applying those permissions to the *directory* which prevents our model from working.   I added the g+x flag to the directories and it worked.  From Server.xml:

                <!-- This key controls who has read/write access to the shared object   -->

                <!-- files and stream files in the server. The Mask is used by umask    -->

                <!-- to set file creation mask.  By default, the mask is set to 017     -->

                <!-- and the files are created with permission 0666.                    -->

                <!-- 0666 & ~017 = 0660 = r w - r w - - - -, that means the owner of    -->

                <!-- the server and all the users belonging to the same group as the    -->

                <!-- owner will have read/write access to the files. This mask must be  -->

                <!-- a 3 digit octal format                                             -->

                <!-- This config node is for unix only.                                 -->

                <Mask>017</Mask>

Is there a way to get it not to apply 0666 to the directories?

Thanks.

    This topic has been closed for replies.

    1 reply

    Nikhil_Kalyan
    Participating Frequently
    June 3, 2011

    Hi,

    Thanks for trying FMS 4.

    I am not sure of my suggestion, but i can give a try.

    I guess you made a default installation of FMS, isn't it ? What you can do instead is to create a user with the previleges that you want to have, and while the installation prompts to provide the user to be used/run as, give this new account that you created. FMS will now run under those privileges. Try and let us know if that helped your case.

    Thank you !

    forrieAuthor
    Known Participant
    June 3, 2011

    The problem isn't the user FMS runs as.   We run it as fms:fms.   The problem is that FMS, per the posted config snippet, is creating *directories* with mode 0666 which prevents anyone in group "fms" from reading logs.   I have to manually add g+x for that to work.   This is probably a bug or a misfeature, in that an assumption was made about the mode of files without regard to the directory.   Can anyone else confirm this.

    forrieAuthor
    Known Participant
    June 11, 2011

    Well, I guess our organization is going to have to file a bug report with Adobe to get this resolved.