|
|
Sponsored Content
Top Forums
Programming
open() system call in c++????
Post 302623293 by Corona688 on Friday 13th of April 2012 11:25:23 AM
04-13-2012
|
|
9 More Discussions You Might Find Interesting
1. UNIX for Advanced & Expert Users
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
How the c compiler differentiates the system calls and function calls? (1 Reply)
Discussion started by: rangaswamy
1 Replies
3. Shell Programming and Scripting
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
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
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
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
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
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
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
LEARN ABOUT OSF1
expand_dump
expand_dump(8) System Manager's Manual expand_dump(8) NAME
expand_dump - Produces a non-compressed kernel crash dump file SYNOPSIS
/usr/sbin/expand_dump input-file output-file DESCRIPTION
By default, kernel crash dump files (vmzcore.#) are compressed during the crash dump. Compressed core files can be examined by the latest versions of debugging tools that have been recompiled to support compressed crash dump files. However, not all debugging tools may be upgraded on a given system, or you may want to examine a crash dump from a remote system using an older version of a tool. The expand_dump utility produces a file that can be read by tools that have not been upgraded to support compressed crash dump files. This non-compressed version can also be read by any upgraded tool. This utility can only be used with compressed crash dump files, and does not support any other form of compressed file. You cannot use other decompression tools such as compress, gzip, or zip on a compressed crash dump file. Note that the non-compressed file will require significantly more disk storage space as it is possible to achieve compression ratios of up to 60:1. Check the available disk space before running expand_dump and estimate the size of the non-compressed file as follows: Run tests by halting your system and forcing a crash as described in the Kernel Debugging manual. Use an upgraded debugger to determine the value of the variable dumpsize. Multiply this vale by the 8Kb page size to approximate the required disk space of the non-compressed crash-dump. Run expand_dump and pipe the output file to /dev/null, noting the size of the file that is printed when expand_dump completes its task. RETURN VALUES
Successful completion of the decompression. The user did not supply the correct number of command line arguments. The input file could not be read. The input file is not a compressed dump, or is corrupted. The output file could not be created or opened for writing and truncated. There was some problem writing to the output file (probably a full disk). The input file is not formated consistantly. It is probably corrupted. The input file could not be correctly decompressed. It is probably corrupted. EXAMPLES
expand_dump vmzcore.4 vmcore.4 SEE ALSO
Commands: dbx(1), kdbx(8), ladebug(1), savecore(8) Kernel Debugging System Administration expand_dump(8)