Permission Denied Error 13 Sco Unix
FORUMSFOR COMPUTER PROFESSIONALS Log In Come Join Us! Are you aComputer / IT professional?Join Tek-Tips Forums! Talk With Other Members Be Notified Of ResponsesTo Your Posts Keyword Search One-Click Access To YourFavorite Forums Automated SignaturesOn Your Posts Best Of All, It's Free! Join Us! *Tek-Tips's functionality depends on members receiving e-mail. By joining you are opting in to receive e-mail. Posting Guidelines Promoting, selling, recruiting, coursework and thesis posting is forbidden.Tek-Tips Posting Policies Jobs Jobs from Indeed What: Where: jobs by Link To This Forum! Add Stickiness To Your Site By Linking To This Professionally Managed Technical Forum.Just copy and paste the BBCode HTML Markdown MediaWiki reStructuredText code below into your site. SCO: SCO Unix Forum at Tek-Tips HomeForumsMIS/ITOperating Systems - UNIX basedSCO: SCO Unix Forum unable to move Permission denied (error 13) thread58-1037737 Forum Search FAQs Links MVPs unable to move Permission denied (error 13) unable to move Permission denied (error 13) dodge20 (MIS) (OP) 5 Apr 05 15:39 I am on Unix Sco 5.05 and I am getting this error when I try to move a file to another directory.I have CHMOD 777 and changed the owner to myself, but I still get this error.Any ideas? Dodge20 RE: unable to move Permission denied (error 13) PHV (MIS) 5 Apr 05 15:42 What are the permissions of the source and target directories ? Hope This Helps, PH.Want to get great answers to your Tek-Tips questions? Have a look at FAQ219-2884 or FAQ222-2244 RE: unable to move Permission denied (error 13) dodge20 (MIS) (OP) 5 Apr 05 17:15 source drwxrwxrwxtarget drwxrwxrwx Dodge20 RE: unable to move Permission denied (error 13) apeasecpc (IS/IT--Management) 5 Apr 05 17:38 What is the command you are using to move the file?What kind of file is it? RE: unable to move Permission denied (error 13) dodge20 (MIS) (OP) 5 Apr 05 22:56 mv filename.txt /user/jay2 Dodge20 RE: unable to move Permission denied (error 13) motoslide (MIS) 6 Apr 05 11:31 Is the source and destination directories on the same filesystem?Are you able to do this as root? RE: unable to move Permission denied (er
lucky to get that: sometimes all you get is an error return that you have to examine yourself with "echo $?". You can't even depend on that being the actual Unix error, but even if it is, what does it mean? Well, every Unix/Linux system includes various ".h" files that describe the numeric errors returned by kernel system calls. Unfortunately, those files are only a little bit more illuminating than the numeric errors themselves. For example, here's a couple of lines from a Linux system: #define EPERM 1 /* Operation not permitted */ ... #define EACCES 13 /* Permission denied */ What's the difference? When would http://www.tek-tips.com/viewthread.cfm?qid=1037737 you get one versus the other? This article attempts to more fully explain what these errors mean and to give examples of what might cause them. I'm only going to look at the first 32 of these; there are many more, but these are the more common. Understand that the numeric codes can vary from Unix to Unix- you really need to look in the /usr/include files to find the symbolic names, and http://aplawrence.com/Unixart/errors.html even those are used in slightly different ways- certain system calls on a BSD system, for example, will return a different error result than they will on a SysV Unix. However, most of that kind of thing is esoteric detail of concern only to programmers working on multiple platforms.Even where the error numbers and the symbolic constants are the same, the comments may vary. For example, while SCO Unix and Linux systems would look almost exactly alike for the first 30 or 40 errors, some of the comments are markedly different, and higher numbered errors are defined completely differently. So, the thing to keep in mind is that just because you've seen a particular error on a particular platform doesn't mean it is the same somewhere else. There's also nothing that prevents a programmer from misusing these constants in their own error returns, either through ignorance or simple misunderstanding of the historical use of these. And it also means that the descriptions of what might cause a specific error are heavily dependent on that word "might". Please keep that in mind as you read this.On a Linux system with source installed, you can cd to /usr/src/linux*/kernel and do a grep -l for the symbolic constant you are interested in. For example, here's the places where EPERM is refer
InformationDocumentation Current VersionUpdatesPrevious VersionCHM TroubleshootingEPCs LatestVisual LANSAVisual LANSA FrameworkLANSA for iLANSA for the WebLANSA IntegratorLANSA OpenLANSA http://www.lansa.com/support/tips/e0012.htm ClientEPC FAQsIssues LatestVisual LANSALANSA for iLANSA for the WebLANSA IntegratorLANSA ComposerLANSA OpenLANSA ClientTips LatestGeneralVisual LANSALANSA for iLANSA for the WebLANSA IntegratorLANSA ComposerLANSA OpenLANSA ClientThird Party SoftwareHelp Desk Help Desk Contact DetailsRequest Support OnlineImprove Resolution Times Support Tips and TechniquesOperating permission denied System Error 13 (Permission denied) in UNIX Operating System Error 13 (Permission denied) in UNIXDate:19 November 2001Product/Release:Visual LANSA Abstract:Operating System Error 13 (Permission denied)Submitted By:LANSA Technical SupportExternal(s):UNIXThis error code indicates that the current user did not have permission to access permission denied error an operating system file. This error usually occurs if the user does not have read or write permission on a file (e.g. PERSON.RRN) or a directory (e.g. the directory containing .RRN files). It may also occur if the user doesn't have execute permission on a program, script, library.For example, to create a .RRN file, the user needs to have read, write and execute permission on the directory where the file will be created. To update a file, the user needs to have read and write permission on the file. If .RRN files are not being created with permissions that allow all users access, refer to the man page for umask(1).© 2016 LANSA. All rights reserved.Terms of UsePrivacyCookiesSitemap