--- title: "Enable Chrome Flags for Linux Enterprise nodes" slug: "enable-chrome-flags-for-linux-enterprise-nodes" updated: 2023-02-06T18:21:18Z published: 2023-02-06T18:21:18Z canonical: "docs.catchpoint.com/enable-chrome-flags-for-linux-enterprise-nodes" --- > ## Documentation Index > Fetch the complete documentation index at: https://docs.catchpoint.com/llms.txt > Use this file to discover all available pages before exploring further. # Enable Chrome Flags for Linux Enterprise nodes ## Prerequisites: - Access to the Enterprise Node (with permission to edit and configure files) - Ability to log into node using the Admin account - Ability to log into node using elevated right to edit/create files for Linux ## Overview: This article shows how certain flags can be enabled for testing on Enterprise Nodes. This is useful if you have a certain application that performs better with certain Chrome flags enabled such as GPU Acceleration, for example. Note: once this flag is enabled, all tests that use this particular node, will then use this config change. ## How to enable Chrome Flags for Linux enterprise node: 1. Connect to the Linux box running the Catchpoint enterprise services. ***Note you must have rights to edit/create a file.*** 2. Once successfully connected, navigate to /etc/catchpoint.d `cd /etc/catchpoint.d` ![blobid3.jpg](https://cdn.document360.io/cb4af8f9-6751-4fd2-b39c-07aae832badb/Images/Documentation/11827112225435-blobid3.jpg) 3. Create a file using your desired text editor and enter the chrome flags you desire (A sample of the flags can be viewed by running the command `#catchpoint view-chrome-switches` For example, taking vi as the editor, you can use the below command: `[root@e3cos7-cp Chrome]# vi chrome_custom_launch_switches.config` After your changes are complete, press: `Esc` `:wq!` `Enter` 4. After saving your config file, you must change the permissions and ownership of the file to Read Only for the  catchpoint installed user and group (typically \`serveruser\` and \`cp\`) `chown serveruser:cp /etc/catchpoint.d/chrome_custom_launch_switches.config` `chmod 0400 /etc/catchpoint.d/chrome_custom_launch_switches.config` ![blobid5.png](https://cdn.document360.io/cb4af8f9-6751-4fd2-b39c-07aae832badb/Images/Documentation/11827703297179-blobid5.png) 5. After your flags have been updated in the file and the ownership has been updated, you must restart the agent. To do this, run the command: `[root@e3cos7-cp Chrome]# catchpoint restart`