Skip to content

Commit 4e3907c

Browse files
committed
Apply valid type to code block
1 parent c3e121f commit 4e3907c

File tree

3 files changed

+14
-11
lines changed

3 files changed

+14
-11
lines changed

defender-endpoint/linux-support-ebpf.md

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -166,11 +166,11 @@ uname -a
166166

167167
If you see increased resource consumption by Microsoft Defender on your endpoints, it's important to identify the process/mount-point/files that are causing most of the CPU/Memory utilization. You can then apply the necessary exclusions. After applying possible antivirus exclusions, if `wdavdaemon` (parent process) is still consuming the resources, use the ebpf-statistics command to get the top system call count:
168168
169-
```Bash
169+
```bash
170170
sudo mdatp diagnostic ebpf-statistics
171171
```
172172
173-
```Output
173+
```console
174174
Output
175175
Monitor 20 seconds
176176
Top file paths:

defender-endpoint/linux-support-events.md

Lines changed: 2 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -78,7 +78,7 @@ Microsoft Defender for Endpoint utilized `audit` framework from linux to track n
7878

7979
if the following line is present, remove it or edit it to enable Microsoft Defender for Endpoint to track specific SYSCALLs.
8080

81-
```output
81+
```console
8282
-a task, never
8383
```
8484

@@ -93,4 +93,5 @@ List the filesystems on the machine with:
9393
```bash
9494
df -Th
9595
```
96+
9697
[!INCLUDE [Microsoft Defender for Endpoint Tech Community](../includes/defender-mde-techcommunity.md)]

defender-endpoint/linux-support-install.md

Lines changed: 10 additions & 8 deletions
Original file line numberDiff line numberDiff line change
@@ -34,15 +34,15 @@ ms.date: 10/11/2024
3434
An error in installation might or might not result in a meaningful error message by the package manager. To verify if the installation succeeded, obtain and check the installation logs using:
3535

3636
```bash
37-
sudo journalctl --no-pager|grep 'microsoft-mdatp' > installation.log
37+
sudo journalctl --no-pager|grep 'microsoft-mdatp' > installation.log
3838
```
3939

4040
```bash
41-
grep 'postinstall end' installation.log
41+
grep 'postinstall end' installation.log
4242
```
4343

44-
```Output
45-
microsoft-mdatp-installer[102243]: postinstall end [2020-03-26 07:04:43OURCE +0000] 102216
44+
```console
45+
microsoft-mdatp-installer[102243]: postinstall end [2020-03-26 07:04:43OURCE +0000] 102216
4646
```
4747

4848
An output from the previous command with correct date and time of installation indicates success.
@@ -93,7 +93,7 @@ Check if the Defender for Endpoint service is running:
9393
service mdatp status
9494
```
9595

96-
```Output
96+
```console
9797
● mdatp.service - Microsoft Defender for Endpoint
9898
Loaded: loaded (/lib/systemd/system/mdatp.service; enabled; vendor preset: enabled)
9999
Active: active (running) since Thu 2020-03-26 10:37:30 IST; 23h ago
@@ -138,7 +138,8 @@ service mdatp status
138138
where `<systemd_path>` is `/lib/systemd/system` for Ubuntu and Debian distributions and /usr/lib/systemd/system` for Rhel, CentOS, Oracle, and SLES. Then rerun step 2.
139139
140140
4. If the above steps don't work, check if SELinux is installed and in enforcing mode. If so, try setting it to permissive (preferably) or disabled mode. It can be done by setting the parameter `SELINUX` to `permissive` or `disabled` in `/etc/selinux/config` file, followed by reboot. Check the man-page of selinux for more details.
141-
Now try restarting the mdatp service using step 2. Revert the configuration change immediately though for security reasons after trying it and reboot.
141+
142+
Now try restarting the mdatp service using step 2. Revert the configuration change immediately though for security reasons after trying it and reboot.
142143
143144
5. If `/opt` directory is a symbolic link, create a bind mount for `/opt/microsoft`.
144145
@@ -148,7 +149,7 @@ Now try restarting the mdatp service using step 2. Revert the configuration chan
148149
ls -l /opt/microsoft/mdatp/sbin/wdavdaemon
149150
```
150151
151-
```Output
152+
```console
152153
-rwxr-xr-x 2 root root 15502160 Mar 3 04:47 /opt/microsoft/mdatp/sbin/wdavdaemon
153154
```
154155
@@ -188,9 +189,10 @@ Now try restarting the mdatp service using step 2. Revert the configuration chan
188189
sudo mdatp diagnostic create
189190
```
190191

191-
```Output
192+
```console
192193
Diagnostic file created: <path to file>
193194
```
194195

195196
Path to a zip file that contains the logs are displayed as an output. Reach out to our customer support with these logs.
197+
196198
[!INCLUDE [Microsoft Defender for Endpoint Tech Community](../includes/defender-mde-techcommunity.md)]

0 commit comments

Comments
 (0)