Skip to content

Commit 3d5ebf9

Browse files
committed
updated article
1 parent 34eb003 commit 3d5ebf9

File tree

1 file changed

+1
-2
lines changed

1 file changed

+1
-2
lines changed

articles/automation/automation-dsc-onboarding.md

Lines changed: 1 addition & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -46,9 +46,8 @@ This allows you to set (push) configurations through DSC and view reporting deta
4646
The following sections outline how you can onboard each type of machine to Azure Automation State Configuration.
4747

4848
> [!NOTE]
49-
>Deploying DSC to a Linux node uses the `/tmp` folder and modules like **nxAutomation** are temporarily downloaded for verification before installing them in their appropriate location. To ensure the modules install correctly, the Log Analytics agent for Linux needs read/write permission on `/tmp` folder. Instead of the Log Analytics agent for Linux running as a privileged user - `root`, the agent runs as the `omsagent` user. In most cases, explicit permission need be granted to this user in order for certain files to be read. To grant permission to `omsagent` user, run the following commands:
49+
>Deploying DSC to a Linux node uses the `/tmp` folder and modules like **nxAutomation** are temporarily downloaded for verification before installing them in their appropriate location. To ensure the modules install correctly, the Log Analytics agent for Linux needs read/write permission on `/tmp` folder. Instead of the Log Analytics agent for Linux running as a privileged user - `root`, the agent runs as the `omsagent` user. In most cases, explicit permission need be granted to this user in order for certain files to be read. To grant permission to `omsagent` user, run the following command:
5050
>
51-
> - Add the `omsagent` user to specific group `sudo usermod -a -G <GROUPNAME> <USERNAME>`
5251
> - Grant write access to the folder `sudo chmod 1777 /tmp`
5352
>
5453

0 commit comments

Comments
 (0)