Sponsored Content
Top Forums Programming open() system call in c++???? Post 302622735 by neutronscott on Thursday 12th of April 2012 02:10:32 PM
Old 04-12-2012
NAME
open, creat - open and possibly create a file or device

SYNOPSIS
#include <sys/types.h>
#include <sys/stat.h>
#include <fcntl.h>


From the manual, it seems you'd need to include some more headers. open() is the low-level call. fopen() is part of stdio.h. If you'd like to use fopen() you'd use fread(). It's a little different.

Last edited by neutronscott; 04-12-2012 at 03:17 PM.. Reason: info about fread()
This User Gave Thanks to neutronscott For This Post:
 

9 More Discussions You Might Find Interesting

1. UNIX for Advanced & Expert Users

how to differentiate system call from library call

Hi, Ho do I differentiate system call from library call? for example if I am using chmod , how do I find out if it is a system call or library call? Thanks Muru (2 Replies)
Discussion started by: muru
2 Replies

2. Programming

c system call

How the c compiler differentiates the system calls and function calls? (1 Reply)
Discussion started by: rangaswamy
1 Replies

3. Shell Programming and Scripting

system call

Hi, How to write a system calls in a script ? > cd $HOME > ls -ltr thanks in advance.. (10 Replies)
Discussion started by: hegdeshashi
10 Replies

4. Programming

C:system call

Hi I'm studing the system call. I've written a small program that return the time spent in doing some operations. Now I'd like to write one that return the time spent in user mode of a process. I'm reading that i should use the tms struct: clock_t times(struct tms *buf); struct tms {... (2 Replies)
Discussion started by: Dedalus
2 Replies

5. UNIX for Advanced & Expert Users

System Call Wrapper of 'open'

When the programmer use 'open' function, the process is like below. "open -> system call wrapper of open in Glibc -> syscall_open in kernel" I found the wrapper of open, but there is no implementation like 'int $80'. int __open (file, oflag) const char *file; int oflag; { ... (3 Replies)
Discussion started by: yuno96
3 Replies

6. Programming

Is there a system call other than 'open' for opening very large files?

Dear all, Inside a C program, I want to open a very big file (about 12 GB) in order to read its content. Here is the code: /* argv contains the path to the file. */ inputFileDescriptor = open(argv, O_RDONLY); if (inputFileDescriptor < 0) { ... (6 Replies)
Discussion started by: dariyoosh
6 Replies

7. Programming

system call

I have a cgi script which is called after certain time interval, which has this: system ("ls -l /tmp/cgic* | grep -v \"cgicsave.env\" | awk '{print $5}'"); During the execution of this script,the output is 0 sometimes. But due to this the system call is not working at all and doesnt o/p... (2 Replies)
Discussion started by: xs2punit
2 Replies

8. Programming

need help with system call

hi everyone i wrote a system call and compiled the kernel succesfully... my system call is in a file in the kernel folder named my_syscall1.c (kernel/my_syscall1.c) the header file for this system call i added it in the folder include like this include/my_syscall1/my_syscall1.h my problem is... (2 Replies)
Discussion started by: demis87
2 Replies

9. Shell Programming and Scripting

system call

Trying to figure out a load issue with a webserver. I have traced a php script and noticed the following connect(4, {sa_family=AF_INET, sin_port=htons(3306), sin_addr=inet_addr("XX.XX.XX.XX")}, 16) = -1 EINPROGRESS (Operation now in progress) <0.000035> poll(, 1, 2000) = 1 () <0.000120>... (5 Replies)
Discussion started by: rajan007
5 Replies
fopen(3s)																 fopen(3s)

Name
       fopen, freopen, fdopen - open a stream

Syntax
       #include <stdio.h>

       FILE *fopen (filename, type)
       char *filename, *type;

       FILE *freopen (filename, type, stream)
       char *filename, *type;
       FILE *stream;

       FILE *fdopen (fildes, type)
       int fildes;
       char *type;

Description
       The  routine opens the file named by filename and associates a stream with it.  The routine returns a pointer to the FILE structure associ-
       ated with the stream.

       The filename points to a character string that contains the name of the file to be opened.

       The type is a character string having one of the following values:

	  "r"	    Open for reading

	  "w"	    Truncate or create for writing

	  "a"	    Append; open for writing at end of file, or create for writing

	  "A"	    Append with no overwrite; open for writing at end-of-file, or create for writing

	  "r+"	    Open for reading and writing

	  "w+"	    Truncate or create for reading and writing

	  "a+"	    Append; open or create for reading and writing at end-of-file

	  "A+"	    Append with no overwrite, open or create for update at end-of-file

       The letter "b" can also follow r, w, or a. In some C implementations, the "b" is needed to indicate a  binary  file,  however,  it  is  not
       needed in ULTRIX.  If "+" is used, the "b" may occur on either side, as in "rb+" or "w+b".

       The  routine  substitutes  the named file in place of the open stream.  The original stream is closed, regardless of whether the open ulti-
       mately succeeds.  The routine returns a pointer to the FILE structure associated with stream.

       The routine is typically used to attach the preopened streams associated with stdin, stdout and stderr to other files.

       The routine associates a stream with a file descriptor.	File descriptors are obtained from or which open files but do not return  pointers
       to  a  FILE structure stream.  Streams are necessary input for many of the Section 3s library routines.	The type of stream must agree with
       the mode of the open file.

       When a file is opened for update, both input and output may be done on the resulting stream.  However, output may not be directly  followed
       by  input  without  an  intervening  or and input may not be directly followed by output without an intervening or an input operation which
       encounters end-of-file.

       When a file is opened for append with no overwrite (that is when type is "A" or "A+"), it is impossible to overwrite information already in
       the  file.  The routine may be used to reposition the file pointer to any position in the file, but when output is written to the file, the
       current file pointer is disregarded.  All output is written at the end of the file and causes the file pointer to be  repositioned  at  the
       end  of	the  output.   If  two separate processes open the same file for append, each process may write freely to the file without fear of
       destroying output being written by the other.  The output from the two processes will be intermixed in the file in the order in which it is
       written.

Return Values
       The and routines return a NULL pointer on failure.

Environment
   SYSTEM_V
       When  your  program is compiled using the System V environment, append with no overwrite is specified by using the "a" or "a+" type string,
       and the "A" and "A+" type strings are not allowed.

   POSIX
       In the POSIX environment, the "a" and "a+" strings, and the "A" and "A+" strings specify append with no overwrite.

See Also
       creat(2), dup(2), open(2), pipe(2), fclose(3s), fseek(3s).

																	 fopen(3s)
All times are GMT -4. The time now is 01:26 AM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy