Very clear explanation, thank you. It started working fine in the background as so0on as I changed those permissions. All systems go. Many thanks.Joe_H wrote:The directory /usr/local/bin is generally reserved for installs of additional software outside the standard items from the OS and those installed by Apple. There are standard policies for using it, Wireshark violated those by creating the directory only for its own usage.
This probably only became an issue with the install of the F@h client. Current security requirements, not sure which version of the OS they start with, keeps the launchd process from starting up background processes like FAHClient from a directory not owned by the system. In addition, the script supplied to have launchd start up that background process runs it under a restricted user account 'nobody' that has minimal privileges. So that user needs execute and lookup access to the directory and the FAHClient executable under the 'o' or other access permissions.
Mac 10.14.6 need to start FAHClient manually
Moderators: Site Moderators, FAHC Science Team
-
- Posts: 10
- Joined: Sat Apr 18, 2020 10:42 am
Re: Mac 10.14.6 need to start FAHClient manually
-
- Site Admin
- Posts: 8001
- Joined: Tue Apr 21, 2009 4:41 pm
- Hardware configuration: Mac Studio M1 Max 32 GB smp6
Mac Hack i7-7700K 48 GB smp4 - Location: W. MA
Re: Mac 10.14.6 need to start FAHClient manually
Good to hear. I have been dusting off old skills from my days doing computer support on a variety of OS's including Linux and BSD based Unix OS's. I personally do not have any systems running on Mojave or Catalina, so sometimes need to ask questions of the developer who can guide through the differences,
-
- Posts: 10
- Joined: Sat Apr 18, 2020 10:42 am
Re: Mac 10.14.6 need to start FAHClient manually
I used to support IBM AIX and later Linux systems about 20 years ago but even though I can remember the basics, I'm very rusty on problem solving on the OS level!