#include <iostream.h>
class test
{
private:
int i;
public:
inline test(int m)
{
i = m;
}
inline int get_i()
{
return i;
}
};
int main()
{
test * a = new test(2); (3 Replies)
Hello folks,
I am facing a problem with the following korn shell script snippet:
ftp -n -i -v <<EOF
print -p open $CURR_HOST
print -p user $USER $PASSWD
print -p binary
print -p cd /mydir/subdir/datadir
print -p get $FILENAME
print -p bye
EOF
exit
It gives me the following... (3 Replies)
Could anyone tell me whats wrong whit this piping? the commands that they execute are correct. the command I am trying is ls|wc. Both processes go to the right if statement.
for(i=0;i<argc;i++){
if(i==0&&argc>1){//first command
if(pipe(pipa1)==-1)
... (2 Replies)
I have a string of commands I am piping some data through and I want to allow command line switches to select which commands are used. I want to do something like this: OPTION="| command3"
command1 -a -b c.txt | command2 -d -e $OPTION >result.txt
I want to do it that way because OPTION may be... (1 Reply)
I get the following error
./get_NE05: line 42:
while
do
echo ${STRING_NAME}
J=1
if ; then
EXT=0$I
else
EXT=$I
fi
while
do
echo $I-$J
#calculating last occurrence
OCCURRENCE=`grep -io "${STRING_NAME}"... (3 Replies)
Hi,guys:
I want to use c to implement a pipe. For example:
ps auxwww | grep fred | more
I forked three child processes. Each is responsible for each command, and pipe to next one.
for(i=0;i<2;i++)
pipe(fd)
if(child==1) // child 1
{
close(1)
dup2(fd,1)
close(fd)
}... (3 Replies)
Hello everyone,
on the man page of "magic(5)"
There is explanation
"&, to specify that the value from the file must have set all of the bits that are set in the specified value" .
My question is that what is the difference between '&' and equal operator '=' ? I tested it with file... (6 Replies)
Hi,
I have this following code which gives me error when compiling. The problem is happening at the point where I create a const_iterator inside the overloaded insertion operator (i.e) operator << () function. The template argument version of set is not correct I guess. Could anyone please pitch... (3 Replies)
Hi,
I've tried searching through the forum but I've drawn a blank so i'm going to post here. I'm developing a number of checks on a CSV file, trying to find if any are greater than a max limit. I'm testing it by running it from a command line.
The file I'm testing has 8 records. When I... (3 Replies)
Hello all, I have two files which are cmd and disk.
`$cat cmd
lsdev | grep -iw`
`$cat disk
hdisk2`
Now I want to use the contents of both the files in a way such that `lsdev | grep -iw` command works for hdisk2 when I write the following script:
`!#/bin/sh
cmd1="$( sed -n... (4 Replies)
Discussion started by: ravi.trivedi
4 Replies
LEARN ABOUT BSD
pipe
PIPE(2) System Calls Manual PIPE(2)NAME
pipe - create an interprocess communication channel
SYNOPSIS
pipe(fildes)
int fildes[2];
DESCRIPTION
The pipe system call creates an I/O mechanism called a pipe. The file descriptors returned can be used in read and write operations. When
the pipe is written using the descriptor fildes[1] up to 4096 bytes of data are buffered before the writing process is suspended. A read
using the descriptor fildes[0] will pick up the data.
It is assumed that after the pipe has been set up, two (or more) cooperating processes (created by subsequent fork calls) will pass data
through the pipe with read and write calls.
The shell has a syntax to set up a linear array of processes connected by pipes.
Read calls on an empty pipe (no buffered data) with only one end (all write file descriptors closed) returns an end-of-file.
Pipes are really a special case of the socketpair(2) call and, in fact, are implemented as such in the system.
A signal is generated if a write on a pipe with only one end is attempted.
RETURN VALUE
The function value zero is returned if the pipe was created; -1 if an error occurred.
ERRORS
The pipe call will fail if:
[EMFILE] Too many descriptors are active.
[ENFILE] The system file table is full.
[EFAULT] The fildes buffer is in an invalid area of the process's address space.
SEE ALSO sh(1), read(2), write(2), fork(2), socketpair(2)BUGS
Should more than 4096 bytes be necessary in any pipe among a loop of processes, deadlock will occur.
4th Berkeley Distribution August 26, 1985 PIPE(2)