![]() On an unprivileged deployment, it changes to be the user account that runs Splunk Phantom. This is the default Splunk Phantom 'root' directory. If you have changed file permissions, you will need to restart Splunk Phantom. You can check to see if an access control list has been applied using the Linux getfacl command, clear any access control list which is incorrectly being applied using the setfacl -b command, or apply correct permissions to a file with the chmod command. Changing the file permissions can cause errors, or prevent Splunk Phantom from working. In general, you should not modify file permissions for Splunk Phantom. Applying a different umask may lead to unexpected behavior. Splunk Phantom expects a umask of 0022 during installation. On an unprivileged deployment - the home directory of the user account that will run Splunk Phantom, also called.On an unprivileged OVA or AMI deployment - /opt/phantom, also called.On a privileged deployment - /opt/phantom.Required directories for an installation as an unprivileged user: /opt/phantom/bin (spawn and spawn3 daemons).Required directories for a standard installation: If your organization requires a different file system for your Splunk Phantom cluster, make sure that the user account running Splunk Phantom has write permissions to the required directories. In a clustered environment, Splunk Phantom implements GlusterFS for its file shares. Splunk Phantom supports any file system where the user account running the application can be given write permissions. Supported file systems and required directories ![]() Use the latest, fully patched version of one of the following browsers: Splunk Phantom requires a web browser that supports HTML 5, SVG graphics, and TLS.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |