[PR #121] [MERGED] Fix MeshCentral installation on macOS (MeshAgent issue #161) #128

New issue

Closed

opened 2026-03-02 02:10:39 +03:00 by kerem · 0 comments

kerem commented

2026-03-02 02:10:39 +03:00

Owner

📋 Pull Request Information

Original PR: https://github.com/amidaware/community-scripts/pull/121
Author: @NiceGuyIT
Created: 2/14/2023
Status: ✅ Merged
Merged: 2/15/2023
Merged by: @silversword411

Base: main ← Head: script-fix-mesh-macos

📝 Commits (3)

2410f75 Fix MeshCentral installation on macOS (MeshAgent issue #161)
a2c515d Spelling
d1236f9 Rename the agent service only if the daemon service exists

📊 Changes

1 file changed (+92 additions, -0 deletions)

View changed files

➕ scripts_staging/macos_fix_mesh_install.sh (+92 -0)

📄 Description

This script fixes MeshAgent issue #161: MacOS Ventura - Not starting meshagent on boot (Maybe Solved)
https://github.com/Ylianst/MeshAgent/issues/161

The following actions are taken:

Add the eXecute bit for directory traversal for the installation directory. This allows regular users access to run the binary inside the directory, fixing the "meshagent" LaunchAgent integration with the user.
Rename the LaunchAgent "meshagent.plist" to prevent conflicts with the LaunchDaemon "meshagent.plist". This may not be needed but is done for good measure.
Rename the service Label inside the plist. Using "defaults" causes the plist to be rewritten in plist format, not ascii.

_{🔄 This issue represents a GitHub Pull Request. It cannot be merged through Gitea due to API limitations.}

## 📋 Pull Request Information **Original PR:** https://github.com/amidaware/community-scripts/pull/121 **Author:** [@NiceGuyIT](https://github.com/NiceGuyIT) **Created:** 2/14/2023 **Status:** ✅ Merged **Merged:** 2/15/2023 **Merged by:** [@silversword411](https://github.com/silversword411) **Base:** `main` ← **Head:** `script-fix-mesh-macos` --- ### 📝 Commits (3) - [`2410f75`](https://github.com/amidaware/community-scripts/commit/2410f75603d8ad6d5279dadbc9902c356d99f3c9) Fix MeshCentral installation on macOS (MeshAgent issue #161) - [`a2c515d`](https://github.com/amidaware/community-scripts/commit/a2c515de3f773d5ff26eb86a4e5880ad0fed9f7f) Spelling - [`d1236f9`](https://github.com/amidaware/community-scripts/commit/d1236f9b1309ba66d5938c8eae48c48cb8482a2c) Rename the agent service only if the daemon service exists ### 📊 Changes **1 file changed** (+92 additions, -0 deletions) <details> <summary>View changed files</summary> ➕ `scripts_staging/macos_fix_mesh_install.sh` (+92 -0) </details> ### 📄 Description This script fixes MeshAgent issue #161: MacOS Ventura - Not starting meshagent on boot (Maybe Solved) <https://github.com/Ylianst/MeshAgent/issues/161> The following actions are taken: 1) Add the eXecute bit for directory traversal for the installation directory. This allows regular users access to run the binary inside the directory, fixing the "meshagent" LaunchAgent integration with the user. 2) Rename the LaunchAgent "meshagent.plist" to prevent conflicts with the LaunchDaemon "meshagent.plist". This may not be needed but is done for good measure. 3) Rename the service Label inside the plist. Using "defaults" causes the plist to be rewritten in plist format, not ascii. --- <sub>🔄 This issue represents a GitHub Pull Request. It cannot be merged through Gitea due to API limitations.</sub>