![]() ![]() Presuming you would want to automount your nfs mounts on-demand, you can just tell automount to do the heavy lifting. That will handle mapping /Volumes/mnt to /mnt for where you need it to be for parity with the linux shares. ![]() In /etc/ make a file called nf (if it doesn’t already exist) and then edit it to add the following line: If you want to mount your nfs shares on a Mac at /mnt then… I’ve also made sure there are several processes with full disk access enabled in the system preferences that relate to flame (although a definitive list of what should be there to make Flame work is something I couldn’t find).Īny ideas? The connection between my Flames has been solid for years under Mojave and I’d hate to have to go back when this seems like some sort of simple-ish config issue. I’ve tried reinstalling Flame and that didn’t help. I can ping the 10.0.1.209 address just fine and no other network changes have been made during the upgrade. I’m thinking this is NFS related and something changed in NFS from Mojave to Catalina (I had a couple of NFS automounts at /mnt on the Mac that were forcibly relocated to /Volumes after the upgrade). The log shows this line a few times when that happens: When selecting the Linux Flame, the Mac shell outputs this:Įrror scanning for projects: No such file or directory I clicked New for the hell of it and Flame immediately crashes. The Linux Flame shows up in the Host Computer menu, like it always has, but when I select it, the project list is empty with the message about clicking the New button to create a project. ![]() Flame 2022.1 launches and works OK except it is unable to see projects on my Linux Flame on the same network. Just updated my Mac to Catalina from Mojave. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |