12-09-2011
Check that you have write permissions to /tmp .
If you have $TMPDIR set, check that it points to a directory where you have write permissions.
9 More Discussions You Might Find Interesting
1. UNIX for Advanced & Expert Users
I keep getting the following errors and I don't know where to look to resolve the problem. Any ideas?
bellmail: lockf(/usr/spool/mail/uucp): permission denied
bellmail: lockf(/usr/spool/mail/root): permission denied
bellmail: lockf(/usr/spool/mail/daemon): no such file or directory....
AIX... (1 Reply)
Discussion started by: Docboyeee
1 Replies
2. UNIX for Dummies Questions & Answers
Hi All,
When I execute a command on Unix and it says 'Permission denied'. What could be the reason and how can it be resolved?
Many thanks,
David (2 Replies)
Discussion started by: david_wang
2 Replies
3. Shell Programming and Scripting
Hi
I need help to send mail through mailx command . Currenlt my program is like
#!/bin/ksh -x
echo " " >> path.lst
MAIL_LIST='someone1@gamil.com someone2@gamil.com someone3@gamil.com'
cat path.lst | mailx -s "path loaction" $MAIL_LIST
echo "End"
exit 0
Its work fine . But i... (3 Replies)
Discussion started by: mani_isha
3 Replies
4. UNIX for Dummies Questions & Answers
I have two servers, 82 and 70.
My exports file on 82 reads
/ ...70(rw)
on 70 I have a mountpoint called mnt_for_82
I execute on 70
mount -t nfs -o rw ...82:/ mnt_for_82
I go to server 70 and indeed can read and travers the mounted subdirectories. However, I try... (0 Replies)
Discussion started by: blaine.miller
0 Replies
5. Shell Programming and Scripting
While executing a script, I am not being able to able to create a file as the file with the same name already exists. That existing file is not getting overwritten as I am not the owner of the file. So, Neither am I able to rename the file nor delete the existing file, so as to get my file created.... (2 Replies)
Discussion started by: Haimanti
2 Replies
6. Shell Programming and Scripting
Hi All,
I am trying to send a mail from linux server but could'nt able to send the mail.
I tried the below syntax's so far but no luck.
mail -s “Hello world” abc@xyz.com < /usr/g/txt.log
cat "txt.log" | mailx -s "Hello world" abc@xyz.com
mailx -s “Hello world” abc@xyz.com <... (2 Replies)
Discussion started by: scriptscript
2 Replies
7. UNIX for Dummies Questions & Answers
How would I go about resolving this error
temporary mail message file: No such file or directory
Can anybody tell me where the default location is for the temporary mail message file is for mailx? It appears that it doesn't exist.
Thanks (1 Reply)
Discussion started by: joen
1 Replies
8. Shell Programming and Scripting
Hi,
I am trying to attach a .log file or .txt file to mail command to send an email once my ksh script executed. I am unable to use mutt command as it has been not installed and i am not supposed to install it. I have tried many ways by googling which has not helped me to succeed.
Here is my... (5 Replies)
Discussion started by: Samah
5 Replies
9. Shell Programming and Scripting
I have a script that checks if the script has been ran with sudo.
If the script is not ran as sudo, the current script is being executed with exec sudo bash.
You are asked for a password, you type in the password, success. Everything is perfect - the commands inside the script are ran as sudo.... (1 Reply)
Discussion started by: boqsc
1 Replies
OPEN(5) File Formats Manual OPEN(5)
NAME
open, create - prepare a fid for I/O on an existing or new file
SYNOPSIS
Topen tag[2] fid[2] mode[1]
Ropen tag[2] fid[2] qid[8]
Tcreate tag[2] fid[2] name[28] perm[4] mode[1]
Rcreate tag[2] fid[2] qid[8]
DESCRIPTION
The open request asks the file server to check permissions and prepare a fid for I/O with subsequent read and write messages. The mode
field determines the type of I/O: 0, 1, 2, and 3 mean read access, write access, read and write access, and execute access, to be checked
against the permissions for the file. In addition, if mode has the OTRUNC (0x10) bit set, the file is to be truncated, which requires
write permission (if the file is append-only, and permission is granted, the open succeeds but the file will not be truncated); if the mode
has the ORCLOSE (0x40) bit set, the file is to be removed when the fid is clunked, which requires permission to remove the file from its
directory. If other bits are set in mode they will be ignored. It is illegal to write a directory, truncate it, or attempt to remove it
on close. If the file is marked for exclusive use (see stat(5)), only one client can have the file open at any time. That is, after such
a file has been opened, no other open will succeed until fid has been clunked. All these permissions are checked at the time of the open
request; subsequent changes to the permissions of files do not affect the ability to read, write, or remove an open file.
The create request asks the file server to create a new file with the name supplied, in the directory (dir) represented by fid, and
requires write permission in the directory. The owner of the file is the implied user id of the request, the group of the file is the same
as dir, and the permissions are the value of
(perm&(~0777|0111)) | (dir.perm&perm&0666)
if a regular file is being created and
(perm&~0777) | (dir.perm&perm&0777)
if a directory is being created. This means, for example, that if the create allows read permission to others, but the containing direc-
tory does not, then the created file will not allow others to read the file.
Finally, the newly created file is opened according to mode, and fid will represent the newly opened file. Mode is not checked against the
permissions in perm. The qid for the new file is returned with the create reply message.
Directories are created by setting the CHDIR bit (0x80000000) in the perm.
The names . and .. are special; it is illegal to create files with these names.
It is an error for either of these messages if the fid is already the product of a successful open or create message.
An attempt to create a file in a directory where the given name already exists will be rejected; in this case, the create system call (see
open(2)) uses open with truncation. The algorithm used by create is: first walk to the directory to contain the file. If that fails,
return an error. Next walk to the specified file. If the walk succeeds, send a request to open and truncate the file and return the
result, successful or not. If the walk fails, send a create message. If that fails, it may be because the file was created by another
process after the previous walk failed, so (once) try the walk and open again. For the behavior of create on a union directory, see
bind(2).
ENTRY POINTS
Open and create both generate open messages; only create generates a create message.
OPEN(5)