|
|
Sponsored Content
Operating Systems
HP-UX
Inter Process File Handling Problem
Post 71569 by Perderabo on Thursday 12th of May 2005 10:10:33 AM
05-12-2005
|
|
9 More Discussions You Might Find Interesting
1. Programming
unix IPC
i would like to know the method of usage of semaphores on shared memory segments the topic seems very difficult to understand mainly when difrent proceses communicate instantly and how do i avaoid deadlock situation (2 Replies)
Discussion started by: kamathanil
2 Replies
2. UNIX for Dummies Questions & Answers
Hi,
I am opening a file......then i am wrting some data into it......and i am reopening the file again but ......i get a error cannot open file.......
$::file= "\adder\testfile.txt"
open(TEST1,$::file);
some write operation
close(TEST1)
open(TEST1,$::file) 'I GET A ERROR CAN OPEN... (2 Replies)
Discussion started by: vivekshankar
2 Replies
3. Programming
hi
i m writin a program in which i keep track of all the child processes the program has generated and if a child process has an abnormal termination i need to do certain task related to that child process.
for handlin child process i used waitpid:
temp_cpid=waitpid(-1,&stat,WUNTRACED);
... (4 Replies)
Discussion started by: mridula
4 Replies
4. UNIX for Advanced & Expert Users
Hi,
I am thinking about writing a log daemon for a multi-processed ksh application (yes - I know that high-level language would be a better option).
My question is as follows:
If many processes (many scripts) will try writing to a single log file:
print "message" > common.log
Will it work or... (2 Replies)
Discussion started by: adderek
2 Replies
5. Programming
For a program I am designing, which involves handling the keyboard input Ctrl^c (SIGINT), it is taking ages for the program to actually recognise and perform the corresponding action whenever I run it and hit Ctrl^C at the CL. I have to do at least 3 Ctrl^Cs before the program will actually... (3 Replies)
Discussion started by: JamesGoh
3 Replies
6. Programming
i want to write a C chat program that communicates over IPC(inter process communication), that could be run using 2 seperate terminal windows within the same computer. so that wat u type in one terminal window , should appear on the other and vice versa...
could some one please help me with the... (2 Replies)
Discussion started by: localp
2 Replies
7. Programming
i wrote handler for sigsegv such that i can allocate memory for a variable to which
sigsegv generated for illlegal acces of memory.
my code is
#include <signal.h>
#include<stdio.h>
#include<stdlib.h>
#include<string.h>
char *j;
void segv_handler(int dummy)
{
j=(char *)malloc(10);
... (4 Replies)
Discussion started by: pavan6754
4 Replies
8. Programming
I need help!Many Thanks!
Now,I try to manage the shared memory inter-process .
Inevitably,I have to deal with the synchronous.
I know the pthread_rwlock in posix,and I compile ,then run successfully in Red Hat Enterprise 4.
I have a doubt about whether the Posix supports the system such as... (1 Reply)
Discussion started by: weizh
1 Replies
9. UNIX for Beginners Questions & Answers
In solaris, orphan process is put to sleep mode and does not consume any CPU resources. In Linux, orphan process is kept in running state consuming all CPU and Ram resources. Is it the case? Is there a difference on how these operating systems will handle orphan processes?
The route cause of... (10 Replies)
Discussion started by: Belure Pooja B
10 Replies
LEARN ABOUT ULTRIX
nfslogsum
nfslogsum(8) Unsupported nfslogsum(8) Name nfslogsum - summarize nfswatch log file Syntax /usr/etc/nfslogsum [ -n ] [ -v ] [ logfile ] Description The command summarizes log files produced by the program. By default the log file is summarized; an alternate log file can be specified on the command line. Each log file can contain one or more log sessions, each indicated by a header which is printed when logging is turned on. For each log session, tallies up the interval packet totals and prints out a one-page summary of the log session. Total packets and percentages are tabulated for each category and displayed. Options -n Tells to read only the first n entries in the log file. This is useful for summarizing log files in cumulative ``chunks''. -v Produces a ``verbose'' summary of the log file. In addition to the summary information printed as described above, a summary of how many calls to each NFS procedure were made on each file system and individual file is printed. This summary information is divided into three sections of six columns each. The columns are headed by the names of the NFS procedures; these are described briefly below: NULLPROC Do nothing. This procedure is provided to allow server response testing and timing. GETATTR Get file attributes (for example, type, mode, number of links, owner's uid, owner's gid, size, access, modification and change times). This procedure is used by the system call, as well as several others. SETATTR Set file attributes (mode, owner's uid, owner's gid, size in bytes, access and modification times). This procedure is used by sys- tem calls such as GETROOT Get file system root. This procedure is obsolete, and has been replaced by a MOUNT Protocol procedure. LOOKUP Look up file name. This procedure is used to obtain an initial file handle for use in current and future requests on that file, and is used by many different system calls. READLINK Read from symbolic link. This procedure is used by the readlink system call, and by the kernel. READ Read data from file. This procedure is used by the system call. WCACHE Write to cache. Unused in the current NFS protocol revision. WRITE Write data to file. This procedure is used by the system call. CREATE Create file. This procedure is used by the and system calls. REMOVE Remove file. This procedure is used by the system call. RENAME Rename file. This procedure is used by the rename system call. LINK Create link to file. This procedure is used by the system call. SYMLINK Create symbolic link to file. This procedure is used by the system call. MKDIR Create directory. This procedure is used by the system call. RMDIR Remove directory. This procedure is used by the system call. READDIR Read entries from directory. Generally only one READDIR call is needed per directory, since a variable number of entries can be returned. STATFS Get file system attributes (transfer size, block size, blocks in use, blocks free). Restrictions The nfslogsum command is extremely sensitive to the format of the log file produced by The log file should not be edited or changed before feeding it to See Also nfswatch(8) nfslogsum(8)