07-31-2012
It means what it says: You don't have permission to create 'outfile' in the current directory.
sudo won't help you here since it tries to create the file before running the program.
10 More Discussions You Might Find Interesting
1. Shell Programming and Scripting
I have a file that comes in as 20081002_invoices.txt and needs to go out as
invoices(20081002).xls When ran this file should have three seperate fields as follows:
column1 column2 column3
data1 data2 data3
when i run the script it produces the invoices(20081002).xls but moves... (1 Reply)
Discussion started by: Pablo_beezo
1 Replies
2. AIX
Hello:
NOOB here. I attempted to use smit mkcd. Failed on first attempt, not enough space. 2nd attempt tried to place iso on /usr, not enough space there. Cleanup ran for about 5 minutes after aborting. Now AIX won't boot. LCD display on 7029-6E3 says: 0517 MOUNT /USR. Attempted to boot from CD... (11 Replies)
Discussion started by: bbird
11 Replies
3. UNIX for Dummies Questions & Answers
I`m having output file which contain following no which changes every time i run script.The number given below are there in file and i have to fatch them from file.
12
15
56
158
365
165
598
568
265
256
258
now i want to use above number from output to input as $j
r=`/omp/bin/ICIC... (1 Reply)
Discussion started by: nitin_aaa27
1 Replies
4. Shell Programming and Scripting
I'd like to do an if / else if condition and print to different files.
Something like:
awk '{
if ($1 == "yes") print $2, $4 < infile > outfile1 ;
else if ($1 == "No") print $2, $4 < infile > outfile2
}'
Obviously I don't know the syntax.
Thanks so much. (5 Replies)
Discussion started by: dcfargo
5 Replies
5. Slackware
OS: Slackwar 13.37
Printer: hpDeskjet 1000 j110
Printer Drivers/Software: HPLIP 3.11.3a (min was 3.10.9) and Cups
The printer will print the first of n-pages but from page 2 on it prints the page (or part of it) backs up and starts again down about 0.8 lines and does this repeatedly till the... (2 Replies)
Discussion started by: slak0
2 Replies
6. UNIX for Dummies Questions & Answers
Hi guys!
So I have a program that allows the user to enter a file, change some characters (for example, a changes to t, etc.) and then save the new file under a new name. However, I need to press carriage return twice for the program to end. I was just wondering if anyone knew of a way for the... (2 Replies)
Discussion started by: PerlNutt
2 Replies
7. Shell Programming and Scripting
done. (1 Reply)
Discussion started by: myaa02
1 Replies
8. Shell Programming and Scripting
I am using xls2csv to convert a xls file into a regular .csv file. However, while using the command as
xls2csv fromfile.xls > tofile.csv
I am getting the following error.
fromfile.xls is not OLE file or Error
I also tried to specify the comma as delimiter but did not help...
xls2csv -c\,... (7 Replies)
Discussion started by: dhruuv369
7 Replies
9. UNIX for Beginners Questions & Answers
Good day, I am trying to run the following command but it does not seem to work.
# mysql -pPassword asteriskcdrdb -s -b -e "select 'Account ID','Destination','Operator','Provider','Date','BillSec','Rate id','Cost' UNION select accountcode,dst,'PBX',route_name,date_format(calldate,'%Y/%c/%e... (8 Replies)
Discussion started by: esgaroth32
8 Replies
10. UNIX for Beginners Questions & Answers
Can anyone offer any advice on how to modify the script below to work on a new system we have, that has no graphics capability? We admin the system through a serial RAS device. I've tried running the below script through the RAS and through an ssh -X session. It failed with something like "GTK... (3 Replies)
Discussion started by: yelirt5
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)