Differences between version 3 and previous revision of EPERM.
Other diffs: Previous Major Revision, Previous Author, or view the Annotated Edit History
| Newer page: | version 3 | Last edited on Sunday, February 23, 2003 2:56:23 am | by PerryLorier | Revert |
| Older page: | version 2 | Last edited on Tuesday, November 5, 2002 3:23:53 pm | by JohnMcPherson | Revert |
@@ -8,5 +8,7 @@
* Trying to unlink(2) a file on a read-only filesystem.
* Trying to increase a process's priority by giving the nice(2) call a negative value when not the superuser (note that this is different to the setpriority(2) call!)
* Trying to use the setpriority(2) call on a process that does not belong to you.
-In general, EACCES seems morely
to be used for file permission conflicts, while EPERM seems more likely to be used for process-related permission conflicts. But you can see that even system calls use them differently.
+In general, EACCES seems more
to be used for file permission conflicts, while EPERM seems more likely to be used for process-related permission conflicts. But you can see that even system calls use them differently.
+
+actually, EACCES for permissions based things (different owners, file permissions, etc) while EPERM covers things where you are trying to break the rules
.
