This IS the Avid L2: Re: [Avid-L2] Avid Crashes on Open

Wednesday, January 15, 2014

Re: [Avid-L2] Avid Crashes on Open

I can't speak for Avid engineering , but it sounds like there are random permissions bugs affecting MC or the MC installer that they can't quite get locked down, so they are recommending this to bypass the problem entirely...despite the obvious problem it causes with overall system security.

On Wednesday, January 15, 2014, Jeff Hedberg wrote:

Tod,
For some reason the latest troubleshooting from Avid support has been to take your system drive and allow write permissions to 'everyone'.

This was the only thing that fixed us not being able to run the latest patch (5.5.4) of scriptsync on our systems here.

I don't like doing it - but it was the only thing that fixed it. After, there was some a "nexidia.pat" file placed at the root level. (this doesn't happen on our MC 7 machines)

Jeff

------------------
Jeff Hedberg

Director of Operations
Union Editorial
575 Broadway,6th floor
New York, NY 10012

On Jan 15, 2014, at 1:44 PM, T Hopkins <hoplist@hillmanncarr.com> wrote:

Isn't this only required if you intend to use the system drive for media? If you do not create projects on the system drive, you do not need to mess with the system drive security. Personally, I set all media drives to "Ignore permissions on this drive" which solves all kinds of problems with user shared drives. You can't do this for the system drive.

cheers,
tod

On Jan 15, 2014, at 11:16 AM, Jeff Hedberg wrote:

Hello Marianna,
I had a similar problem trying to get scriptsync to work in MC 5.5.4 (on mac OS 10.7.5). (we never had this problem with MC 5.5.3.7 (same OS))

Opening up the hard drive so that anyone can write to it does indeed 'fix' this - but I have always preferred only allowing administrators to write to the root level of the internal hard drive. Near as I can tell the Mac OS has been set up this way since 10.5.x (it's the oldest machine I have the ability to check right now), so I'm not sure it's a 'bug' in Lion, Mt. Lion, or Mavericks.

I don't know if I'm the only one, but opening up the root to all write access ('chmod 777 /') is an idea that goes completely against the little computer security sensibility that I have. Is there any way to convince the coder writers to not require that?

Could they put whatever files they need to modify someplace else on the hard drive rather than the root level?

There are places like ~/Library/Application Support that don't need admin privileges to write to (granted, they only work for that user - but if something needed to go to /Library/Application Support - it could get copied there on the install when done as an admin, no?.

I'll admit that I'm no coder. But if it's possible to change the course of the train requiring the entire hard drive to be writable by anyone, I'd like to encourage it.

Regards,

Jeff

------------------
Jeff Hedberg

Director of Operations
Union Editorial
575 Broadway,6th floor
New York, NY 10012

On Jan 15, 2014, at 9:30 AM, marianna_montague@avid.com wrote:

Zach

Usually this occurs because you are on Lion, Mt Lion or Mavericks and the internal drive is set to read only and should be set to read/write.

Take the following steps to change permissions:

Click on the system (Macintosh HD in most cases) drive to highlight
From the File menu select Get Info (cmd+I)
Click the lock icon in the bottom right to make changes
Click on the "Read only" text in the Privilege column next to Everyone and set the privilege to "Read & Write"

Give that a whirl... and report back if still stuck.

Marianna