Sponsored Content
Top Forums UNIX for Advanced & Expert Users getcwd: permission denied error Post 34146 by Deepa on Friday 7th of February 2003 02:44:09 AM
Old 02-07-2003
getcwd: permission denied error

When I do a 'cd /appl' and issue 'ls -al' command, I get the following error for .. directory.
./..: Permission denied
But still I get a listing of other directories under /appl.

Also, if I give 'man' for any command under this /appl folder, I get the following error:
getcwd: Permission denied

When I issued 'ls -ld /appl', I get the following output.

drwxrwxrwx 19 appmgr dp 1024 Feb 6 00:15 appl/


Is anything screwed up in the appl directory attributes?

Deepa
 

10 More Discussions You Might Find Interesting

1. UNIX for Dummies Questions & Answers

rm Permission Denied error

I am very new to Unix. We have a script that will remove files from a directory. The account removing the files has the same permissions as the directory the files are located. We have logged in as the account and deleted the files from that directory but when we run the script with the account... (7 Replies)
Discussion started by: Cech2002
7 Replies

2. Shell Programming and Scripting

xterm gives me permission denied error

When I try to run xterm at a command prompt in solaris 2.5.1, i'm getting a permission denied error. But the directory and user permissions look ok, they are part of a users group and then also root,sys,adm so what gives? Any ideas? Thanks! (1 Reply)
Discussion started by: kymberm
1 Replies

3. UNIX for Advanced & Expert Users

Need help with Couldn't canonicalise: Permission denied error

Hi People I am getting this error Couldn't canonicalise: Permission denied. Anyone knows what does this error mean ? It all started when my team members were testing Sftp functions on some directories and they were hitting directory no found errors within their scripts. So when we enquired... (8 Replies)
Discussion started by: wilsontan
8 Replies

4. OS X (Apple)

Permission Denied Error with X11

Hello, I am using Tiger 10.4.11 I am trying out the GIMP, so I installed the X11 package from "Optional Installs" on the cd. Whenever I open X11, I get an error: xterm: could not exec /dev/null: Permission denied I have chmodded /dev/null to 777, as well as the /tmp directory. I deleted... (2 Replies)
Discussion started by: Ricardo-san
2 Replies

5. Shell Programming and Scripting

Change: xecho: execute permission denied error

Hello, I am have an issues with one of my scripts. I get the following error when I get to the point in the script where I am making the change. The change does take however. the error is "change: xecho: execute permission denied" Everything was working properly until I start cleaning... (3 Replies)
Discussion started by: simpsonjr
3 Replies

6. UNIX for Dummies Questions & Answers

Getting Error 0403-006 Execute permission denied.

Hi All, Need your help.. I am writing one script in which I am assigning value to one variable but when i am executing it is showing error "0403-006 Execute permission denied" below is the line of that script : INPUT_COUNT=wc $GIF_DIR/input/VID_RIMS.DAT | awk '{print $1}' and access... (2 Replies)
Discussion started by: NirajThakar
2 Replies

7. AIX

SSH Error - Permission denied (publickey,keyboard-interactive)

Hello, I'm trying to setup password less authentication to remote ssh server. I generated the public key and gave it to the vendor and The key is added in the remote machines authorized_keys file. When I try to connect to a remote machine through SFTP username@host I am getting the error... (4 Replies)
Discussion started by: nice_chapp
4 Replies

8. UNIX for Dummies Questions & Answers

Webserver permission denied error

Hello, I was trying a perl-cgi tutorial and saving the data from online form to a file named (guests.txt). I am using the localhost port 80 for practice. My page file "guestbook.html" is working as I saw the online form. After filled out the blanks and submit, I was expecting to see the result... (3 Replies)
Discussion started by: yifangt
3 Replies

9. Red Hat

Permission denied error using chmod on a cifs mount

I have a RHEL 5.7 system with a cifs mount from a Windows 2007 file server that I need to fix the permissions on. Once the share is mounted the permission for the mount are 777. I need to change that to 770 on the top level directory and to 640 on the sub-directory .ssh/. But when I run chmod... (0 Replies)
Discussion started by: westmoreland
0 Replies

10. Shell Programming and Scripting

Pipe, permission denied error

Hello, I am trying to stream lines written into file. When first source is down, I expect the code to swap to second line and run it. Script below works as usual and it prints out each line of the input file (s.txt): #!/bin/bash while read -r line; do echo "$line" done <"$1" exit 0Output... (12 Replies)
Discussion started by: baris35
12 Replies
fmtmsg(1)							   User Commands							 fmtmsg(1)

NAME
fmtmsg - display a message on stderr or system console SYNOPSIS
fmtmsg [-c class] [-u subclass] [-l label] [-s severity] [-t tag] [-a action] text DESCRIPTION
Based on a message's classification component, the fmtmsg utility either writes a formatted message to stderr or writes a formatted message to the console. A formatted message consists of up to five standard components (see environment variable MSGVERB in the ENVIRONMENT VARIABLES section of this page). The classification and subclass components are not displayed as part of the standard message, but rather define the source of the message and direct the display of the formatted message. OPTIONS
The following options are supported: -c class Describes the source of the message. Valid keywords are: hard The source of the condition is hardware. soft The source of the condition is software. firm The source of the condition is firmware. -u subclass A list of keywords (separated by commas) that further defines the message and directs the display of the message. Valid keywords are: appl The condition originated in an application. This keyword should not be used in combination with either util or opsys. util The condition originated in a utility. This keyword should not be used in combination with either appl or opsys. opsys The message originated in the kernel. This keyword should not be used in combination with either appl or util. recov The application will recover from the condition. This keyword should not be used in combination with nrecov. nrecov The application will not recover from the condition. This keyword should not be used in combination with recov. print Print the message to the standard error stream stderr. console Write the message to the system console. print, console, or both may be used. -l label Identifies the source of the message. -s severity Indicates the seriousness of the error. The keywords and definitions of the standard levels of severity are: halt The application has encountered a severe fault and is halting. error The application has detected a fault. warn The application has detected a condition that is out of the ordinary and might be a problem. info The application is providing information about a condition that is not in error. -t tag The string containing an identifier for the message. -a action A text string describing the first step in the error recovery process. This string must be written so that the entire action argument is interpreted as a single argument. fmtmsg precedes each action string with the TO FIX: prefix. text A text string describing the condition. Must be written so that the entire text argument is interpreted as a single argu- ment. EXAMPLES
Example 1 Standard message format The following example of fmtmsg produces a complete message in the standard message format and displays it to the standard error stream. example% fmtmsg -c soft -u recov,print,appl -l UX:cat -s error -t UX:cat:001 -a "refer to manual" "invalid syntax" produces: UX:cat: ERROR: invalid syntax TO FIX: refer to manual UX:cat:138 Example 2 Using MSGVERB When the environment variable MSGVERB is set as follows: MSGVERB=severity:text:action and Example 1 is used, fmtmsg produces: ERROR: invalid syntax TO FIX: refer to manual Example 3 Using SEV_LEVEL When the environment variable SEV_LEVEL is set as follows: SEV_LEVEL=note,5,NOTE the following fmtmsg command: example% fmtmsg -c soft -u print -l UX:cat -s note -a "refer to manual" "invalid syntax" produces: NOTE: invalid syntax TO FIX: refer to manual and displays the message on stderr. ENVIRONMENT VARIABLES
The environment variables MSGVERB and SEV_LEVEL control the behavior of fmtmsg. MSGVERB is set by the administrator in the /etc/profile for the system. Users can override the value of MSGVERB set by the system by resetting MSGVERB in their own .profile files or by changing the value in their current shell session. SEV_LEVEL can be used in shell scripts. MSGVERB tells fmtmsg which message components to select when writing messages to stderr. The value of MSGVERB is a colon-separated list of optional keywords. MSGVERB can be set as follows: MSGVERB=[keyword[:keyword[:...]]] export MSGVERB Valid keywords are: label, severity, text, action, and tag. If MSGVERB contains a keyword for a component and the component's value is not the component's null value, fmtmsg includes that component in the message when writing the message to stderr. If MSGVERB does not include a keyword for a message component, that component is not included in the display of the message. The keywords may appear in any order. If MSGVERB is not defined, if its value is the null string, if its value is not of the correct format, or if it contains keywords other than the valid ones listed above, fmtmsg selects all components. MSGVERB affects only which message components are selected for display. All message components are included in console messages. SEV_LEVEL defines severity levels and associates print strings with them for use by fmtmsg. The standard severity levels shown below cannot be modified. Additional severity levels can be defined, redefined, and removed. 0 (no severity is used) 1 HALT 2 ERROR 3 WARNING 4 INFO SEV_LEVEL is set as follows: description is a comma-separated list containing three fields: SEV_LEVEL= [description[:description[:...]]] export SEV_LEVEL description=severity_keyword, level, printstring severity_keyword is a character string used as the keyword with the -s severity option to fmtmsg. level is a character string that evaluates to a positive integer (other than 0, 1, 2, 3, or 4, which are reserved for the standard severity levels). If the keyword severity_keyword is used, level is the severity value passed on to fmtmsg(3C). printstring is the character string used by fmtmsg in the standard message format whenever the severity value level is used. If SEV_LEVEL is not defined, or if its value is null, no severity levels other than the defaults are available. If a description in the colon separated list is not a comma separated list containing three fields, or if the second field of a comma separated list does not eval- uate to a positive integer, that description in the colon separated list is ignored. EXIT STATUS
The following exit values are returned: 0 All the requested functions were executed successfully. 1 The command contains a syntax error, an invalid option, or an invalid argument to an option. 2 The function executed with partial success, however the message was not displayed on stderr. 4 The function executed with partial success; however, the message was not displayed on the system console. 32 No requested functions were executed successfully. ATTRIBUTES
See attributes(5) for descriptions of the following attributes: +-----------------------------+-----------------------------+ | ATTRIBUTE TYPE | ATTRIBUTE VALUE | +-----------------------------+-----------------------------+ |Availability |SUNWcsu | +-----------------------------+-----------------------------+ SEE ALSO
addseverity(3C), fmtmsg(3C), attributes(5) SunOS 5.11 20 Jul 1994 fmtmsg(1)
All times are GMT -4. The time now is 08:43 AM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy