05-26-2011
Yes I have , I have created new user, as per my understanding every user has right to create file in his home directory,
I have checked with same permission on another server also , it is working,
dont know why ti?
any idea?
Regards
Manoj
10 More Discussions You Might Find Interesting
1. AIX
Hello, this is my first post.
I have a user who cannot create a file over 2 GB's in size eventhough the FS is large file enabled and I added a special stanza in /etc/security/limits to allow an unlimited file size for this particular user (user1 - see below).
ibm:/home/root (4062)#cat... (7 Replies)
Discussion started by: AIXtexas
7 Replies
2. UNIX for Dummies Questions & Answers
Hi ,
We are running Oracle 8.1.7 on HP-UX B.11.00. Recently we have upgraded Oracle from 8.0.6. to 8.1.7. Almost all the shell script we use has the Sqlplus as sqlplus -s @/apps/prod/sql/xxxx.sql > /apps/prod/log/xxxx.out .
However we receive the error
SP2-0310: unable to open file... (2 Replies)
Discussion started by: guru_2007
2 Replies
3. UNIX for Dummies Questions & Answers
Hi ,
I am running Oracle 8.1.7 on HP-UX B.11.00. Recently I have upgraded Oracle from 8.0.6. to 8.1.7. Almost all the shell script has the Sqlplus as sqlplus -s @/apps/prod/sql/xxxx.sql > /apps/prod/log/xxxx.out .
However I receive the error
SP2-0310: unable to open file... (2 Replies)
Discussion started by: Ananth.p
2 Replies
4. Solaris
am unable to open a .log file which is 4MB size. (18 Replies)
Discussion started by: venkatramana
18 Replies
5. UNIX for Advanced & Expert Users
I am working on a unix server.
I killed all the processes with my id on the machine.
After that I tried to delete a file, I got an error:-
file not removed.Text File busy.
Deletion of directory prompted:-
Directory not empty.
Can anyone help me regarding this...???
Thanks,
Vikas (11 Replies)
Discussion started by: vikasrout
11 Replies
6. Shell Programming and Scripting
Hi,
I was compiling few C programs in the unix server and getting the following error message
rm: /home/a0xxx28/AVT/SEEDLIBRARYDB/LIB/*.a non-existent
proc MODE=ANSI CODE=ANSI_C INCLUDE=/home/a0xxx28/PVT/SEEDLIBRARYDB/INCLUDE
INCLUDE=/home/a0xxx28/PVT/SEEDLIBRARY/INCLUDE ... (1 Reply)
Discussion started by: kavithakuttyk
1 Replies
7. Shell Programming and Scripting
Hey all,
I'm brand new to script writing, I'm wanting to make a script that will ask for a file and then retrieve that file if it exists, and if it doesn't exist, create the file with the desired name, and I'm completely stuck.. so far..
#! bin/bash
echo "Enter desired file"
read "$file"
if ... (5 Replies)
Discussion started by: Byrang
5 Replies
8. Shell Programming and Scripting
Not able to open a file using this code
why not?
use strict;
use warnings;
my $file = "verInfo.txt";
unless(open FILE, $file) {
# Die with error message
# if we can't open it.
die "\nUnable to open $file\n";
}
my $line = <FILE>;
print $line;
close FILE; (7 Replies)
Discussion started by: srijith
7 Replies
9. Solaris
Hi
I have the following cenario:
I have requested a LUN from the NetApp to create a file system, and the netapp admin provide me with one as you can see below, but after following all the steps, I could not create a file system on the device:
# format
Searching for disks...done
... (11 Replies)
Discussion started by: fretagi
11 Replies
10. UNIX for Beginners Questions & Answers
Hi,
Getting the below error while installing from ks.cfg unable to open input kickstart file curl#37 Couldn't open file /tmp/swappart
Here am trying to include /tmp/swappart file from pre section under disks and partition section. Dont know where exactly am doing wrong
My kickstart file... (3 Replies)
Discussion started by: Sumanthsv
3 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)