I’m very critical of most things ADSK does, and just look at my posts in the other forum to see that. But to completely ignore the most minimal of best practices in a multi-user, multi-machine environment like you are and then blame that on ADSK is wrong. There is NO logical defense for not have User Management in a studio environment where you have Macs, Windows and Linux workstations, and file servers like Qnap that are running non-standard, quasi-blackbox OS. I think you are starting from a shaky foundation, and then Flame nonsense certainly doesn’t help on top of that.
I’m pissed at ADSK. They do really lame things, often. If you want to use Flame with a Project Server, I’ll help you, and it’s what we do. But you need to start from scratch, in a sandboxed environment. Get it working. Then figure out how to customized that to the deployment you want. But something is very wrong in what you’ve been doing so far.
I have no experience with macOS and Flame… so I will be of little help there. But if you can at least get a linux workflow successful, it gives you a starting off point that is more valid than what you have currently. I’m going to send you my FreeIPA notes that might be helpful.
To be fair, and this should be taken as an impartial comment, common UID/GID’s across systems is very much of a ‘given’. This isn’t flame causing these issues but rather two OS’ competing. This will happen irrespective of what software is trying to write/read across two systems.
news to me, been running all of this stuff without any of this for years with no problems, never had a issue with this, but also never had to run NFS and all that fancy shmanzy stuff, that i really dont need to have in my life
However trying to make any of this work on macs is pain,… joining linux machines == piece of cake, installing freeIPA in a VM and all = easy
Yes. I have once joined a Mac to IPA, but mostly just as a test. I didn’t do anything NFS related. We run all our Macs as standalone machines with local users, and they are just internet side machines anyway.
Although I have no experience with Active Directory, macOS does have that compatibility built in, so in theory it would be the best choice if you are trying to run tri-OS centralized user stuff.
I don’t even think Apple uses macOS Flame internally. It’s for undies guys.
But at the very least, you should be able to manually create a user with a specific NOT 501 UID on macOS, and a matching UID on linux, and NFS should see that and not care about anything else.
On linux, I think everything under 1000 is reserved for systems accounts.
yea ive gotten that far.. just cant get it to really work
i made a new user as uid 1001 on the macs still same errors.
wouldnt these permission issues show up if I do any kind of test with my terminal? i tested hardlinks, softlinks, making directories as root and as my user and all of that - no errors , no matter whay uid i have
That’s what we did after moving from Linux to MacOS….used Active Directory with the Macs, TrueNAS, Hitachi BlueArc and Windows via SMB, and once we figured out a few bumps along the way, it was pretty bullet-proof for years. I can count on one hand the number of times we had a permission problem.
For us, the sacrifice of some potential bandwidth in using SMB over NFS was worth it for less dinking around on the multiple OSes, just as you was suggesting.
yea been having no issues with SMB and AD and all the macs.
My problem remains that
A) when running the projectserver , if I use the default hosts//… as “project home” everytime I save a project it takes ~5s . But everything at least works , saves take 5s on mac OR linux, same behaviour in 2025, no matter what server. (as in: saving a empty project)
B) when i use a external directory , no matter if qnap , another directory on the projectserver, a ubuntu server or a synology - the saves are fast and everything works fine on my linux client - however all the macs are completely freaking out.
even if I just mount the original exposed project somewhere else except the automatic “hosts” folder using the same nfs options, saves are suddenly fast but the macs freak out.
So i wonder whats so special about /hosts//.. mount is that some abstraction layer? how is this different from a direct NFS mount ?
I can not use SMB for this mount, at all. only NFS supported for project homes (as in it refuses with a big error message)
I am running out of smart ideas with these macs, “i need identity management” apparently also isnt by default “matching UIDs and GIDs” .
also obviously only AD is properly supported by macOS, macOS is a supported OS by Adsk….
and matching UID/GID manually also fixed nothing, i really think thats a red hering.
If I export my NFS share as chmod 777 for example - everyone can do anything on that folder , no matter what ID someone has?
How can all my write/hard/softlink/etc stuff succeed while just flame fails? (ive gottenmanye different fails now, from unable to create projects to timeline resizes not beign saved to corrupted projects and everything in between) .
Goes back to the early 90s and before. Back then we had to manually sync the passwd and group files to make sure we used matching numbers. Generally common sense from a system design perspective.
Haven’t followed all the detail in the conversation. But manually mounting filesystems in the right place rather than relying on automount and path resolution is also an easy way to remove weirdness from the equation.
It’s kind of like driving manual transmission vs. automatic.
And I do think it might be one of the ‘shortcuts’ that may be causing you problems. All of these mechanism require some lookup of sorts, and they may be timing out on something they’re looking for (an orphaned hostname that no longer exists), and that timeout is causing your delays.
So the more you can eliminate lookups and runtime resolution if you have a relatively static environment, the better.
Right now my Flame startup has a long pause because it’s trying to find some project info from a Flame that’s no longer on the network. 20s pause. Can see the attempts in the logs. Haven’t chased it down, but is annoying me. Not blaming Flame, it’s just stale data I haven’t scrubbed yet.
the problem with “matching uids” really boils down to that macs do not support that concept
→ I have Active Directory , it doesnt change a thing , i get random UIDs between OS without some kind of yet other workarounds, and the point here is “workarounds”.
→ No built in ways to change UIDs for local users on a mac either (as in create user→ set UID, you have to create a random uid user then change it and the permissions afterwards.. wtf)
→ openLDAP pretty much dead , freeIPA setup is completely unsupported mess(on macOS)
Flame needs to stop beign a special child that needs all this old linux stuff to be a thing. honestly.
Resolve collab works with random laptop users across the world…. thats just the reality of it.
slow saves i still cant explain that at all -.- there is nothing left over , i have a sandbox network between 2 completely fresh machines
yes as I said you have to create a random uid user then change it and the permissions afterwards.
which breaks a bunch of macOS things. like the user then doesnt show up in the login window anymore
so its not something that macOS really supports and might break with a OS update down the line.
also red hering, the uids dont seem to matter at all. i can make a random uid user and it still works fine, the kicker was mounting in auto_direct using the hostname, otherwise it starts going nuts apparently… (which is highly.. weird)
i am not this thikk i hope, but if permissions are permissive enough, matching UID/GIDs should not matter
but yea…
like the user then doesnt show up in the login window anymore