Unable to write to /tmp OSX, unable to correct permissions Operation not permitted

OSX (10.11 El Capitan) is unable to install any software updates or install any software because the /tmp and the /private/tmp folders don't seem to be writeable.

Running sudo /usr/libexec/repair_packages --repair --standard-pkgs --volume /

gives
unable to set owner and group on "tmp" Error 1 Operation not permitted
unable to set permissions on "tmp" Error 1 Operation not permitted

Is there a way to manually delete the tmp folders and recreate them?
When I tried renaming or deleting /tmp or /private/tmp I kept getting operation not permitted. sudo chmod 1777 also failed in the same way on both /tmp and /private/tmp folders

Disk-Utility says the disk is healthy, no issues detected during first aid.

Is there any way to redirect the tmp location to another writeable folder?

asked Oct 9 '16 at 16:45

Ali

1,0611711

1

Did you disable SIP first? From Recovery; Terminal csrutil disable

– Tetsujin
Oct 10 '16 at 4:50

2

I have the same problem. Followed Tetsujin's advice, restarted in recovery mode, and ran csrutil disable. After that, I was able to execute repair_packages with success and was able to access /tmp as usual. However, after going back to recovery mode and executing csrutil enable, my system is having the same problem. It seems the only way I can gain access to /tmp is by disabling System Integrity Protection.

– Andrew Ferk
Oct 17 '16 at 21:15

3

I ended up going back to recovery mode and executing csrutil disable. After a restart, I removed tmp folder: sudo rm /tmp; sudo rm /private/tmp, created tmp folder sudo mkdir /private/tmp; sudo chown root:wheel /private/tmp; sudo chmod 1777 /private/tmp, created the symlink: sudo ln -s /private/tmp /tmp, and ran repair_pacakges again. After going back to recovery mode and running csrutil enable, all is working again! However, the permissions of /private/tmp used to be drwxrwxrwt@ and now they are drwxrwxrwt. I'm unsure what the @ is and if this will cause me problems.

– Andrew Ferk
Oct 17 '16 at 21:34

1

@AndrewFerk: see these posts apple.stackexchange.com/questions/42177/… unix.stackexchange.com/questions/10/what-does-the-mean-in-ls-l for explanation of the @ extended permissions marker

– Adam Michalik
Oct 18 '16 at 7:25

add a comment |

OSX (10.11 El Capitan) is unable to install any software updates or install any software because the /tmp and the /private/tmp folders don't seem to be writeable.

Running sudo /usr/libexec/repair_packages --repair --standard-pkgs --volume /

gives
unable to set owner and group on "tmp" Error 1 Operation not permitted
unable to set permissions on "tmp" Error 1 Operation not permitted

Disk-Utility says the disk is healthy, no issues detected during first aid.

Is there any way to redirect the tmp location to another writeable folder?

asked Oct 9 '16 at 16:45

Ali

1,0611711

1

Did you disable SIP first? From Recovery; Terminal csrutil disable

– Tetsujin
Oct 10 '16 at 4:50

2

I have the same problem. Followed Tetsujin's advice, restarted in recovery mode, and ran csrutil disable. After that, I was able to execute repair_packages with success and was able to access /tmp as usual. However, after going back to recovery mode and executing csrutil enable, my system is having the same problem. It seems the only way I can gain access to /tmp is by disabling System Integrity Protection.

– Andrew Ferk
Oct 17 '16 at 21:15

3

I ended up going back to recovery mode and executing csrutil disable. After a restart, I removed tmp folder: sudo rm /tmp; sudo rm /private/tmp, created tmp folder sudo mkdir /private/tmp; sudo chown root:wheel /private/tmp; sudo chmod 1777 /private/tmp, created the symlink: sudo ln -s /private/tmp /tmp, and ran repair_pacakges again. After going back to recovery mode and running csrutil enable, all is working again! However, the permissions of /private/tmp used to be drwxrwxrwt@ and now they are drwxrwxrwt. I'm unsure what the @ is and if this will cause me problems.

– Andrew Ferk
Oct 17 '16 at 21:34

1

@AndrewFerk: see these posts apple.stackexchange.com/questions/42177/… unix.stackexchange.com/questions/10/what-does-the-mean-in-ls-l for explanation of the @ extended permissions marker

– Adam Michalik
Oct 18 '16 at 7:25

add a comment |

OSX (10.11 El Capitan) is unable to install any software updates or install any software because the /tmp and the /private/tmp folders don't seem to be writeable.

Running sudo /usr/libexec/repair_packages --repair --standard-pkgs --volume /

gives
unable to set owner and group on "tmp" Error 1 Operation not permitted
unable to set permissions on "tmp" Error 1 Operation not permitted

Disk-Utility says the disk is healthy, no issues detected during first aid.

Is there any way to redirect the tmp location to another writeable folder?

asked Oct 9 '16 at 16:45

Ali

1,0611711

OSX (10.11 El Capitan) is unable to install any software updates or install any software because the /tmp and the /private/tmp folders don't seem to be writeable.

Running sudo /usr/libexec/repair_packages --repair --standard-pkgs --volume /

gives
unable to set owner and group on "tmp" Error 1 Operation not permitted
unable to set permissions on "tmp" Error 1 Operation not permitted

Disk-Utility says the disk is healthy, no issues detected during first aid.

Is there any way to redirect the tmp location to another writeable folder?

macos permissions chmod osx-el-capitan

asked Oct 9 '16 at 16:45

Ali

1,0611711

asked Oct 9 '16 at 16:45

Ali

1,0611711

asked Oct 9 '16 at 16:45

Ali

1,0611711

asked Oct 9 '16 at 16:45

Ali

1,0611711

asked Oct 9 '16 at 16:45

Ali

1,0611711

1

Did you disable SIP first? From Recovery; Terminal csrutil disable

– Tetsujin
Oct 10 '16 at 4:50

2

I have the same problem. Followed Tetsujin's advice, restarted in recovery mode, and ran csrutil disable. After that, I was able to execute repair_packages with success and was able to access /tmp as usual. However, after going back to recovery mode and executing csrutil enable, my system is having the same problem. It seems the only way I can gain access to /tmp is by disabling System Integrity Protection.

– Andrew Ferk
Oct 17 '16 at 21:15

3

I ended up going back to recovery mode and executing csrutil disable. After a restart, I removed tmp folder: sudo rm /tmp; sudo rm /private/tmp, created tmp folder sudo mkdir /private/tmp; sudo chown root:wheel /private/tmp; sudo chmod 1777 /private/tmp, created the symlink: sudo ln -s /private/tmp /tmp, and ran repair_pacakges again. After going back to recovery mode and running csrutil enable, all is working again! However, the permissions of /private/tmp used to be drwxrwxrwt@ and now they are drwxrwxrwt. I'm unsure what the @ is and if this will cause me problems.

– Andrew Ferk
Oct 17 '16 at 21:34

1

@AndrewFerk: see these posts apple.stackexchange.com/questions/42177/… unix.stackexchange.com/questions/10/what-does-the-mean-in-ls-l for explanation of the @ extended permissions marker

– Adam Michalik
Oct 18 '16 at 7:25

add a comment |

1

Did you disable SIP first? From Recovery; Terminal csrutil disable

– Tetsujin
Oct 10 '16 at 4:50

2

I have the same problem. Followed Tetsujin's advice, restarted in recovery mode, and ran csrutil disable. After that, I was able to execute repair_packages with success and was able to access /tmp as usual. However, after going back to recovery mode and executing csrutil enable, my system is having the same problem. It seems the only way I can gain access to /tmp is by disabling System Integrity Protection.

– Andrew Ferk
Oct 17 '16 at 21:15

3

I ended up going back to recovery mode and executing csrutil disable. After a restart, I removed tmp folder: sudo rm /tmp; sudo rm /private/tmp, created tmp folder sudo mkdir /private/tmp; sudo chown root:wheel /private/tmp; sudo chmod 1777 /private/tmp, created the symlink: sudo ln -s /private/tmp /tmp, and ran repair_pacakges again. After going back to recovery mode and running csrutil enable, all is working again! However, the permissions of /private/tmp used to be drwxrwxrwt@ and now they are drwxrwxrwt. I'm unsure what the @ is and if this will cause me problems.

– Andrew Ferk
Oct 17 '16 at 21:34

1

@AndrewFerk: see these posts apple.stackexchange.com/questions/42177/… unix.stackexchange.com/questions/10/what-does-the-mean-in-ls-l for explanation of the @ extended permissions marker

– Adam Michalik
Oct 18 '16 at 7:25

Did you disable SIP first? From Recovery; Terminal csrutil disable

– Tetsujin
Oct 10 '16 at 4:50

I have the same problem. Followed Tetsujin's advice, restarted in recovery mode, and ran csrutil disable. After that, I was able to execute repair_packages with success and was able to access /tmp as usual. However, after going back to recovery mode and executing csrutil enable, my system is having the same problem. It seems the only way I can gain access to /tmp is by disabling System Integrity Protection.

– Andrew Ferk
Oct 17 '16 at 21:15

I ended up going back to recovery mode and executing csrutil disable. After a restart, I removed tmp folder: sudo rm /tmp; sudo rm /private/tmp, created tmp folder sudo mkdir /private/tmp; sudo chown root:wheel /private/tmp; sudo chmod 1777 /private/tmp, created the symlink: sudo ln -s /private/tmp /tmp, and ran repair_pacakges again. After going back to recovery mode and running csrutil enable, all is working again! However, the permissions of /private/tmp used to be drwxrwxrwt@ and now they are drwxrwxrwt. I'm unsure what the @ is and if this will cause me problems.

– Andrew Ferk
Oct 17 '16 at 21:34

@AndrewFerk: see these posts apple.stackexchange.com/questions/42177/… unix.stackexchange.com/questions/10/what-does-the-mean-in-ls-l for explanation of the @ extended permissions marker

– Adam Michalik
Oct 18 '16 at 7:25

add a comment |

5 Answers
5

active

oldest

votes

Reboot your Mac into recovery mode

Open Utilities menu in the top bar > open Terminal
```
csrutil disable
```

Reboot

Remove the tmp folder

sudo rm -i /tmp

sudo rm -i /private/tmp

Create tmp folder

sudo mkdir /private/tmp

sudo chown root:wheel /private/tmp

sudo chmod 1777 /private/tmp

Create the symlink
```
sudo ln -s /private/tmp /tmp
```

Run repair_packages (you may not need to do this)

sudo /usr/libexec/repair_packages --repair --standard-pkgs --volume /

Reboot back to recovery mode and run
```
csrutil enable
```

Reboot

Props to Andrew Ferk for figuring out a fix; pulling out your comment as a community wiki answer so it's more readable.

edited Oct 22 '16 at 7:34

community wiki

3 revs, 2 users 97%
ento

2

Thank you!!! I had spent 3 days pulling my hair out over this. No idea how the permissions got so screwed in the first place, but one day I turned on the mac to a selection of warnings, programs not working and an inability to install anything. This fixed that problem.

– johngeorgewright
Oct 20 '16 at 10:10

Why did you make this CW?

– Revetahw
Oct 24 '16 at 13:31

Because I didn't want to get credit for an answer which I merely converted from someone else's comment

– ento
Oct 24 '16 at 14:47

Alright, cool. BTW, I did not see your comment until now since there was no @Fiksdal.

– Revetahw
Nov 3 '16 at 18:03

10.13: sudo: /usr/libexec/repair_packages: command not found

– Даниил Пронин
Feb 27 '18 at 5:16

add a comment |

I fixed this by restoring my system from a Time Machine Backup. But the other suggestions in the comments are worth trying too.

answered Oct 19 '16 at 10:03

Ali

1,0611711

add a comment |

Try to create and modify permissions on /private/tmp folder without running csrutil disable. This worked for me, after trying unsuccessfully to delete and the error message on boot is gone.

edited Oct 21 '16 at 10:35

kenorb

11.1k1578116

answered Oct 21 '16 at 8:28

user69083

Welcome to Super User. Please don't post an answer to confirm that another answer worked. The site's Q&A format reserves answers for solutions to the question, and each answer should contribute another solution. The way to indicate that an answer was useful is to invest a little time in the site and you will gain sufficient privileges to upvote answers you like.

– fixer1234
Oct 21 '16 at 8:55

add a comment |

sudo chmod 1777 /private/tmp

Did it for me.

answered Oct 17 '18 at 16:13

Renetik

1012

add a comment |

If you got this message in terminal (or iTerm) using maxOS Mojave

Operation not permitted

It turned out I needed to add my terminal app to the Settings.app "Security & Privacy" > "Full Disk Access"

(I added both terminal.app and iTerm.app)

answered Nov 7 '18 at 11:49

Aiden Moon

add a comment |

Your Answer

StackExchange.ready(function() {
var channelOptions = {
tags: "".split(" "),
id: "3"
};
initTagRenderer("".split(" "), "".split(" "), channelOptions);

StackExchange.using("externalEditor", function() {
// Have to fire editor after snippets, if snippets enabled
if (StackExchange.settings.snippets.snippetsEnabled) {
StackExchange.using("snippets", function() {
createEditor();
});
}
else {
createEditor();
}
});

function createEditor() {
StackExchange.prepareEditor({
heartbeatType: 'answer',
autoActivateHeartbeat: false,
convertImagesToLinks: true,
noModals: true,
showLowRepImageUploadWarning: true,
reputationToPostImages: 10,
bindNavPrevention: true,
postfix: "",
imageUploader: {
brandingHtml: "Powered by u003ca class="icon-imgur-white" href="https://imgur.com/"u003eu003c/au003e",
contentPolicyHtml: "User contributions licensed under u003ca href="https://creativecommons.org/licenses/by-sa/3.0/"u003ecc by-sa 3.0 with attribution requiredu003c/au003e u003ca href="https://stackoverflow.com/legal/content-policy"u003e(content policy)u003c/au003e",
allowUrls: true
},
onDemand: true,
discardSelector: ".discard-answer"
,immediatelyShowMarkdownHelp:true
});

}
});

draft saved

draft discarded

Sign up or log in

StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});

Post as a guest

Name

Required, but never shown

StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fsuperuser.com%2fquestions%2f1133065%2funable-to-write-to-tmp-osx-unable-to-correct-permissions-operation-not-permitt%23new-answer', 'question_page');
}
);

Post as a guest

Name

Required, but never shown

5 Answers
5

active

oldest

votes

5 Answers
5

active

oldest

votes

Reboot your Mac into recovery mode

Open Utilities menu in the top bar > open Terminal
```
csrutil disable
```

Reboot

Remove the tmp folder

sudo rm -i /tmp

sudo rm -i /private/tmp

Create tmp folder

sudo mkdir /private/tmp

sudo chown root:wheel /private/tmp

sudo chmod 1777 /private/tmp

Create the symlink
```
sudo ln -s /private/tmp /tmp
```

Run repair_packages (you may not need to do this)

sudo /usr/libexec/repair_packages --repair --standard-pkgs --volume /

Reboot back to recovery mode and run
```
csrutil enable
```

Reboot

Props to Andrew Ferk for figuring out a fix; pulling out your comment as a community wiki answer so it's more readable.

edited Oct 22 '16 at 7:34

community wiki

3 revs, 2 users 97%
ento

2

Thank you!!! I had spent 3 days pulling my hair out over this. No idea how the permissions got so screwed in the first place, but one day I turned on the mac to a selection of warnings, programs not working and an inability to install anything. This fixed that problem.

– johngeorgewright
Oct 20 '16 at 10:10

Why did you make this CW?

– Revetahw
Oct 24 '16 at 13:31

Because I didn't want to get credit for an answer which I merely converted from someone else's comment

– ento
Oct 24 '16 at 14:47

Alright, cool. BTW, I did not see your comment until now since there was no @Fiksdal.

– Revetahw
Nov 3 '16 at 18:03

10.13: sudo: /usr/libexec/repair_packages: command not found

– Даниил Пронин
Feb 27 '18 at 5:16

add a comment |

Reboot your Mac into recovery mode

Open Utilities menu in the top bar > open Terminal
```
csrutil disable
```

Reboot

Remove the tmp folder

sudo rm -i /tmp

sudo rm -i /private/tmp

Create tmp folder

sudo mkdir /private/tmp

sudo chown root:wheel /private/tmp

sudo chmod 1777 /private/tmp

Create the symlink
```
sudo ln -s /private/tmp /tmp
```

Run repair_packages (you may not need to do this)

sudo /usr/libexec/repair_packages --repair --standard-pkgs --volume /

Reboot back to recovery mode and run
```
csrutil enable
```

Reboot

Props to Andrew Ferk for figuring out a fix; pulling out your comment as a community wiki answer so it's more readable.

edited Oct 22 '16 at 7:34

community wiki

3 revs, 2 users 97%
ento

2

Thank you!!! I had spent 3 days pulling my hair out over this. No idea how the permissions got so screwed in the first place, but one day I turned on the mac to a selection of warnings, programs not working and an inability to install anything. This fixed that problem.

– johngeorgewright
Oct 20 '16 at 10:10

Why did you make this CW?

– Revetahw
Oct 24 '16 at 13:31

Because I didn't want to get credit for an answer which I merely converted from someone else's comment

– ento
Oct 24 '16 at 14:47

Alright, cool. BTW, I did not see your comment until now since there was no @Fiksdal.

– Revetahw
Nov 3 '16 at 18:03

10.13: sudo: /usr/libexec/repair_packages: command not found

– Даниил Пронин
Feb 27 '18 at 5:16

add a comment |

Reboot your Mac into recovery mode

Open Utilities menu in the top bar > open Terminal
```
csrutil disable
```

Reboot

Remove the tmp folder

sudo rm -i /tmp

sudo rm -i /private/tmp

Create tmp folder

sudo mkdir /private/tmp

sudo chown root:wheel /private/tmp

sudo chmod 1777 /private/tmp

Create the symlink
```
sudo ln -s /private/tmp /tmp
```

Run repair_packages (you may not need to do this)

sudo /usr/libexec/repair_packages --repair --standard-pkgs --volume /

Reboot back to recovery mode and run
```
csrutil enable
```

Reboot

Props to Andrew Ferk for figuring out a fix; pulling out your comment as a community wiki answer so it's more readable.

edited Oct 22 '16 at 7:34

community wiki

3 revs, 2 users 97%
ento

Reboot your Mac into recovery mode

Open Utilities menu in the top bar > open Terminal
```
csrutil disable
```

Reboot

Remove the tmp folder

sudo rm -i /tmp

sudo rm -i /private/tmp

Create tmp folder

sudo mkdir /private/tmp

sudo chown root:wheel /private/tmp

sudo chmod 1777 /private/tmp

Create the symlink
```
sudo ln -s /private/tmp /tmp
```

Run repair_packages (you may not need to do this)

sudo /usr/libexec/repair_packages --repair --standard-pkgs --volume /

Reboot back to recovery mode and run
```
csrutil enable
```

Reboot

Props to Andrew Ferk for figuring out a fix; pulling out your comment as a community wiki answer so it's more readable.

edited Oct 22 '16 at 7:34

community wiki

3 revs, 2 users 97%
ento

edited Oct 22 '16 at 7:34

community wiki

3 revs, 2 users 97%
ento

community wiki

3 revs, 2 users 97%
ento

community wiki

3 revs, 2 users 97%
ento

2

Thank you!!! I had spent 3 days pulling my hair out over this. No idea how the permissions got so screwed in the first place, but one day I turned on the mac to a selection of warnings, programs not working and an inability to install anything. This fixed that problem.

– johngeorgewright
Oct 20 '16 at 10:10

Why did you make this CW?

– Revetahw
Oct 24 '16 at 13:31

Because I didn't want to get credit for an answer which I merely converted from someone else's comment

– ento
Oct 24 '16 at 14:47

Alright, cool. BTW, I did not see your comment until now since there was no @Fiksdal.

– Revetahw
Nov 3 '16 at 18:03

10.13: sudo: /usr/libexec/repair_packages: command not found

– Даниил Пронин
Feb 27 '18 at 5:16

add a comment |

2

Thank you!!! I had spent 3 days pulling my hair out over this. No idea how the permissions got so screwed in the first place, but one day I turned on the mac to a selection of warnings, programs not working and an inability to install anything. This fixed that problem.

– johngeorgewright
Oct 20 '16 at 10:10

Why did you make this CW?

– Revetahw
Oct 24 '16 at 13:31

Because I didn't want to get credit for an answer which I merely converted from someone else's comment

– ento
Oct 24 '16 at 14:47

Alright, cool. BTW, I did not see your comment until now since there was no @Fiksdal.

– Revetahw
Nov 3 '16 at 18:03

10.13: sudo: /usr/libexec/repair_packages: command not found

– Даниил Пронин
Feb 27 '18 at 5:16

Thank you!!! I had spent 3 days pulling my hair out over this. No idea how the permissions got so screwed in the first place, but one day I turned on the mac to a selection of warnings, programs not working and an inability to install anything. This fixed that problem.

– johngeorgewright
Oct 20 '16 at 10:10

Why did you make this CW?

– Revetahw
Oct 24 '16 at 13:31

Because I didn't want to get credit for an answer which I merely converted from someone else's comment

– ento
Oct 24 '16 at 14:47

Alright, cool. BTW, I did not see your comment until now since there was no @Fiksdal.

– Revetahw
Nov 3 '16 at 18:03

10.13: sudo: /usr/libexec/repair_packages: command not found

– Даниил Пронин
Feb 27 '18 at 5:16

add a comment |

I fixed this by restoring my system from a Time Machine Backup. But the other suggestions in the comments are worth trying too.

answered Oct 19 '16 at 10:03

Ali

1,0611711

add a comment |

I fixed this by restoring my system from a Time Machine Backup. But the other suggestions in the comments are worth trying too.

answered Oct 19 '16 at 10:03

Ali

1,0611711

add a comment |

I fixed this by restoring my system from a Time Machine Backup. But the other suggestions in the comments are worth trying too.

answered Oct 19 '16 at 10:03

Ali

1,0611711

I fixed this by restoring my system from a Time Machine Backup. But the other suggestions in the comments are worth trying too.

answered Oct 19 '16 at 10:03

Ali

1,0611711

answered Oct 19 '16 at 10:03

Ali

1,0611711

answered Oct 19 '16 at 10:03

Ali

1,0611711

answered Oct 19 '16 at 10:03

Ali

1,0611711

add a comment |

Try to create and modify permissions on /private/tmp folder without running csrutil disable. This worked for me, after trying unsuccessfully to delete and the error message on boot is gone.

edited Oct 21 '16 at 10:35

kenorb

11.1k1578116

answered Oct 21 '16 at 8:28

user69083

Welcome to Super User. Please don't post an answer to confirm that another answer worked. The site's Q&A format reserves answers for solutions to the question, and each answer should contribute another solution. The way to indicate that an answer was useful is to invest a little time in the site and you will gain sufficient privileges to upvote answers you like.

– fixer1234
Oct 21 '16 at 8:55

add a comment |

Try to create and modify permissions on /private/tmp folder without running csrutil disable. This worked for me, after trying unsuccessfully to delete and the error message on boot is gone.

edited Oct 21 '16 at 10:35

kenorb

11.1k1578116

answered Oct 21 '16 at 8:28

user69083

Welcome to Super User. Please don't post an answer to confirm that another answer worked. The site's Q&A format reserves answers for solutions to the question, and each answer should contribute another solution. The way to indicate that an answer was useful is to invest a little time in the site and you will gain sufficient privileges to upvote answers you like.

– fixer1234
Oct 21 '16 at 8:55

add a comment |

Try to create and modify permissions on /private/tmp folder without running csrutil disable. This worked for me, after trying unsuccessfully to delete and the error message on boot is gone.

edited Oct 21 '16 at 10:35

kenorb

11.1k1578116

answered Oct 21 '16 at 8:28

user69083

Try to create and modify permissions on /private/tmp folder without running csrutil disable. This worked for me, after trying unsuccessfully to delete and the error message on boot is gone.

edited Oct 21 '16 at 10:35

kenorb

11.1k1578116

answered Oct 21 '16 at 8:28

user69083

edited Oct 21 '16 at 10:35

kenorb

11.1k1578116

edited Oct 21 '16 at 10:35

kenorb

11.1k1578116

edited Oct 21 '16 at 10:35

kenorb

11.1k1578116

answered Oct 21 '16 at 8:28

user69083

answered Oct 21 '16 at 8:28

user69083

answered Oct 21 '16 at 8:28

user69083

Welcome to Super User. Please don't post an answer to confirm that another answer worked. The site's Q&A format reserves answers for solutions to the question, and each answer should contribute another solution. The way to indicate that an answer was useful is to invest a little time in the site and you will gain sufficient privileges to upvote answers you like.

– fixer1234
Oct 21 '16 at 8:55

add a comment |

Welcome to Super User. Please don't post an answer to confirm that another answer worked. The site's Q&A format reserves answers for solutions to the question, and each answer should contribute another solution. The way to indicate that an answer was useful is to invest a little time in the site and you will gain sufficient privileges to upvote answers you like.

– fixer1234
Oct 21 '16 at 8:55

Welcome to Super User. Please don't post an answer to confirm that another answer worked. The site's Q&A format reserves answers for solutions to the question, and each answer should contribute another solution. The way to indicate that an answer was useful is to invest a little time in the site and you will gain sufficient privileges to upvote answers you like.

– fixer1234
Oct 21 '16 at 8:55

add a comment |

sudo chmod 1777 /private/tmp

Did it for me.

answered Oct 17 '18 at 16:13

Renetik

1012

add a comment |

sudo chmod 1777 /private/tmp

Did it for me.

answered Oct 17 '18 at 16:13

Renetik

1012

add a comment |

sudo chmod 1777 /private/tmp

Did it for me.

answered Oct 17 '18 at 16:13

Renetik

1012

sudo chmod 1777 /private/tmp

Did it for me.

answered Oct 17 '18 at 16:13

Renetik

1012

answered Oct 17 '18 at 16:13

Renetik

1012

answered Oct 17 '18 at 16:13

Renetik

1012

answered Oct 17 '18 at 16:13

Renetik

1012

add a comment |

If you got this message in terminal (or iTerm) using maxOS Mojave

Operation not permitted

It turned out I needed to add my terminal app to the Settings.app "Security & Privacy" > "Full Disk Access"

(I added both terminal.app and iTerm.app)

answered Nov 7 '18 at 11:49

Aiden Moon

add a comment |

If you got this message in terminal (or iTerm) using maxOS Mojave

Operation not permitted

It turned out I needed to add my terminal app to the Settings.app "Security & Privacy" > "Full Disk Access"

(I added both terminal.app and iTerm.app)

answered Nov 7 '18 at 11:49

Aiden Moon

add a comment |

If you got this message in terminal (or iTerm) using maxOS Mojave

Operation not permitted

It turned out I needed to add my terminal app to the Settings.app "Security & Privacy" > "Full Disk Access"

(I added both terminal.app and iTerm.app)

answered Nov 7 '18 at 11:49

Aiden Moon

If you got this message in terminal (or iTerm) using maxOS Mojave

Operation not permitted

It turned out I needed to add my terminal app to the Settings.app "Security & Privacy" > "Full Disk Access"

(I added both terminal.app and iTerm.app)

answered Nov 7 '18 at 11:49

Aiden Moon

answered Nov 7 '18 at 11:49

Aiden Moon

answered Nov 7 '18 at 11:49

Aiden Moon

answered Nov 7 '18 at 11:49

Aiden Moon

add a comment |

draft saved

draft discarded

Thanks for contributing an answer to Super User!

Please be sure to answer the question. Provide details and share your research!

But avoid …

Asking for help, clarification, or responding to other answers.

Making statements based on opinion; back them up with references or personal experience.

To learn more, see our tips on writing great answers.

draft saved

draft discarded

Sign up or log in

StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});

Post as a guest

Name

Required, but never shown

Post as a guest

Name

Required, but never shown

Sign up or log in

StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});

Post as a guest

Name

Required, but never shown

Sign up or log in

StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});

Post as a guest

Name

Required, but never shown

Sign up or log in

StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});

Post as a guest

Name

Required, but never shown

Name

Required, but never shown

Name

Required, but never shown

This page is only for reference, If you need detailed information, please check here

搜尋此網誌

Jtdylktuy