| Rev | Author | # | Line |
|---|---|---|---|
| 1 | PerryLorier | 1 | !!!Operation Not Permitted |
| 2 | |||
| 3 | This appears to be regularly confused with [EACCES]. To quote from SUSv3: | ||
| 4 | |||
| 5 | ;:''Operation not permitted. An attempt was made to perform an operation limited to processes with appropriate privileges or to the owner of a file or other resource.'' | ||
| 2 | JohnMcPherson | 6 | |
| 7 | Examples include: | ||
| 8 | * Trying to unlink(2) a file on a read-only filesystem. | ||
| 9 | * 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!) | ||
| 10 | * Trying to use the setpriority(2) call on a process that does not belong to you. | ||
| 11 | |||
| 3 | PerryLorier | 12 | 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. |
| 13 | |||
| 14 | actually, EACCES for permissions based things (different owners, file permissions, etc) while EPERM covers things where you are trying to break the rules. | ||
| 4 | JohnButtery | 15 | |
| 16 | Your powers are great; limits exist however. This is one of them. |
lib/plugin/WlugLicense.php (In template 'html'):99: Warning: Invalid argument supplied for foreach()
lib/plugin/WlugLicense.php (In template 'html'):111: Warning: in_array() [<a href='function.in-array'>function.in-array</a>]: Wrong datatype for second argument