Sponsored Content
Top Forums UNIX for Dummies Questions & Answers int open(const char *pathname, int flags, mode_t mode) doubt... Post 302145817 by csnmgeek on Thursday 15th of November 2007 09:31:19 AM
Old 11-15-2007
int open(const char *pathname, int flags, mode_t mode) doubt...

hello everybody!

I want to create a file with permissions for read, write, and execute to everybody using C, so I write this code:

Code:
#include <stdio.h>
#include <sys/types.h>
#include <sys/stat.h>
#include <fcntl.h>

int main(){
   int fileDescriptor;
   fileDescriptor = open("./NewFile", O_CREAT, S_IRWXU|S_IRWXG|S_IRWXO );
   printf("File Descriptor: %d\n", fileDescriptor);
   close(fileDescriptor);

   return 0;
}

I expected to have the following result:

$ ls -l NewFile
-rwxrwxrwx 1 csnmgeek csnmgeek 0 2007-11-15 09:23 NewFile

but instead I got this:

$ ls -l NewFile
-rwxr-xr-x 1 csnmgeek csnmgeek 0 2007-11-15 09:23 NewFile

Can you tell me where is the problem?
regards
jorge
 

10 More Discussions You Might Find Interesting

1. Programming

difference between int ** func() and int *& func()

What is the difference between int** func() and int*& func(). Can you please explain it with suitable example. Thanks, Devesh. (1 Reply)
Discussion started by: devesh
1 Replies

2. Red Hat

cast from const void* to unsigned int loses precision

Hello everey one, here i am attempting to compile a c++ project .it's throughing the following errors. my machine details are as follows: Linux chmclozr0119 2.6.18-53.el5 #1 SMP Wed Oct 10 16:34:19 EDT 2007 x86_64 x86_64 x86_64 GNU/Linux errors: ===== Generating... (0 Replies)
Discussion started by: mannam srinivas
0 Replies

3. Programming

How to read flags from mode_t type?

Hello, After, I stat() a file, how can I read the various permissions flags from the st_mode variable which is of type mode_t? I would like to do something like: struct stat *perms; int res = stat(filename, perms); if(perms->st.mode == S_IROTH) do something; but I know that is the wrong... (2 Replies)
Discussion started by: pallak7
2 Replies

4. Programming

concat const char * with char *

hello everybody! i have aproblem! i dont know how to concatenate const char* with char const char *buffer; char *b; sprintf(b,"result.txt"); strcat(buffer,b); thanx in advance (4 Replies)
Discussion started by: nicos
4 Replies

5. Programming

conversion to 'char' from 'int' warning

Hi, I wrote a simple code in C++ converting from UpperToLower case characters. However, my compiler gives me a warning: "warning: conversion to 'char' from 'int' may alter its value". Any tips? I would like to stress, I don't want to load my string into char array. int ToLower(string... (4 Replies)
Discussion started by: kajolo
4 Replies

6. Programming

Handle int listen(int sockfd, int backlog) in TCP

Hi, from the manual listen(2): listen for connections on socket - Linux man page It has a parameter called backlog and it limits the maximum length of queue of pending list. If I set backlog to 128, is it means no more than 128 packets can be handled by server? If I have three... (3 Replies)
Discussion started by: sehang
3 Replies

7. Programming

C++ program is crashing on re-assigning const static member variable using an int pointer

Hi, Can any one tell me why my following program is crashing? #include <iostream> using namespace std; class CA { public: const static int i; }; const int CA::i = 10; int main() { int* pi = const_cast<int*>(&CA::i); *pi = 9; cout << CA::i << endl; } (6 Replies)
Discussion started by: royalibrahim
6 Replies

8. Programming

error: invalid conversion from ‘const char*’ to ‘char*’

Compiling xpp (The X Printing Panel) on SL6 (RHEL6 essentially): xpp.cxx: In constructor ‘printFiles::printFiles(int, char**, int&)’: xpp.cxx:200: error: invalid conversion from ‘const char*’ to ‘char*’ The same error with all c++ constructors - gcc 4.4.4. If anyone can throw any light on... (8 Replies)
Discussion started by: GSO
8 Replies

9. Programming

Help with understanding ( int, char, long, short, signed, unsigned etc.... )

My question is simple: When should I use a long, int, char, unsigned/signed variables?? When I declare a variable "unsigned;" what did I do it??? Why would I delcare an integer "long" or "short" ( unsigned or signed)?? Any examples of when things like "unsigned", "long", "short" etc...... (6 Replies)
Discussion started by: cpp_beginner
6 Replies

10. Programming

Small query regarding function "char * strerror(int errnum)"

As this function returns the address of the string corressponding to the errno value provided to it. Can someone please let me know where, in the memory, it could be (on freeBSD). The MAN page tells under the BUG section that "For unknown error numbers, the strerror() function will return its... (5 Replies)
Discussion started by: Praveen_218
5 Replies
OPEN(2) 							System Calls Manual							   OPEN(2)

NAME
open - open a file for reading or writing, or create a new file SYNOPSIS
#include <sys/types.h> #include <fcntl.h> int open(const char *path, int flags [, mode_t mode]) DESCRIPTION
Open opens the file path for reading and/or writing, as specified by the flags argument and returns a descriptor for that file. The flags argument may indicate the file is to be created if it does not already exist (by specifying the O_CREAT flag), in which case the file is created with mode mode as described in chmod(2) and modified by the process' umask value (see umask(2)). Path is the address of a string of ASCII characters representing a path name, terminated by a null character. The flags specified are formed by or'ing the following values O_RDONLY open for reading only O_WRONLY open for writing only O_RDWR open for reading and writing O_NONBLOCK do not block on open O_APPEND append on each write O_CREAT create file if it does not exist O_TRUNC truncate size to 0 O_EXCL error if create and file exists Opening a file with O_APPEND set causes each write on the file to be appended to the end. If O_TRUNC is specified and the file exists, the file is truncated to zero length. If O_EXCL is set with O_CREAT, then if the file already exists, the open returns an error. This can be used to implement a simple exclusive access locking mechanism. If O_EXCL is set and the last component of the pathname is a symbolic link, the open will fail even if the symbolic link points to a non-existent name. If the O_NONBLOCK flag is specified and the open call would result in the process being blocked for some reason, the open returns immediately. Upon successful completion a non-negative integer termed a file descriptor is returned. The file pointer used to mark the current position within the file is set to the beginning of the file. The new descriptor is set to remain open across execve system calls; see close(2). The system imposes a limit on the number of descriptors open simultaneously by one process. ERRORS
The named file is opened unless one or more of the following are true: [ENOTDIR] A component of the path prefix is not a directory. [ENAMETOOLONG] The path name exceeds PATH_MAX characters. [ENOENT] O_CREAT is not set and the named file does not exist. [ENOENT] A component of the path name that must exist does not exist. [EACCES] Search permission is denied for a component of the path prefix. [EACCES] The required permissions (for reading and/or writing) are denied for the named file. [EACCES] O_CREAT is specified, the file does not exist, and the directory in which it is to be created does not permit writing. [EACCES] A device to be opened for writing is physically write protected. [ELOOP] Too many symbolic links were encountered in translating the pathname. (Minix-vmd) [EISDIR] The named file is a directory, and the arguments specify it is to be opened for writing. [EROFS] The named file resides on a read-only file system, and the file is to be modified. [EMFILE] The system limit for open file descriptors per process has already been reached. [ENFILE] The system file table is full. [ENXIO] The named file is a character special or block special file, and the device associated with this special file does not exist. [ENOSPC] O_CREAT is specified, the file does not exist, and the directory in which the entry for the new file is being placed cannot be extended because there is no space left on the file system containing the directory. [ENOSPC] O_CREAT is specified, the file does not exist, and there are no free inodes on the file system on which the file is being created. [EIO] An I/O error occurred while making the directory entry or allocating the inode for O_CREAT. [EFAULT] Path points outside the process's allocated address space. [EEXIST] O_CREAT and O_EXCL were specified and the file exists. SEE ALSO
chmod(2), close(2), dup(2), fcntl(2), lseek(2), read(2), write(2), umask(2). 4th Berkeley Distribution May 14, 1986 OPEN(2)
All times are GMT -4. The time now is 09:48 AM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy