Open iamdamosuzuki opened 1 day ago
I was wrong about this. The files are being properly created and placed where they need to be. However, those mv
errors still appear.
I did a little digging, the error appears to be caused by the fact that the external hard drive's owner:group is set to VideoLabMini:staff instead of root:wheel. However, so far I've been unable to change the ownership to root:wheel, despite disabling SIP and whatnot. I'll see if there's any way to reliably change ownership on the later macOS, I'm currently on Sonoma.
Thanks for double checking! That was the behavior I was able to reproduce on a mac on our end (files are moved, but errors get thrown). I'll poke at it a bit more if I have a chance, but let me know if you find some kind of work around to silence those errors.
Thanks for looking into this! I did a bit of poking around it seems that ownership of any external drives will automatically be set to the user:group of the logged in user. I tried seeing if I could go into the folder options (cmd + i) and give root
read/write access, but that wasn't an option. I tried giving read/write access to Everybody
as well as Administrators
and neither of those seemed to help. There wasn't an option to give root
access or ownership. I think this might be something baked at the OS level with later versions of macOS, so anything you can do to silence the errors would be helpful. I'll continue to ignore them for now, I just swear there was a time a few versions ago that the files actually wouldn't move, which would definitely be a real problem. For now, it's just a nuisance.
For some reason I'm getting errors when auxiliary files are being moved to their final location, but only when using external drives. These errors don't seem to be happening when capturing on the system drive. Here's the output from vrecord, you can see the
mv
errors at the end.