Hi,
I need to retrieve the exit status of 4 moves running as background processes. The wait command will not work since it can only give me the exit status of the last of the background processes.
Here's a sample of what I need
!#/bin/ksh
mv /dir1/subdir1/*.Z /dir6/subdir6/ &
mv... (2 Replies)
Hi,
I have an application with a bug in it that keeps sockets in CLOSE_WAIT, which eventually freezes the server because the user account it runs under runs out of file handles. We have the bug fixed but can only release the fix with the next release.
Does anyone know how I can clear the... (3 Replies)
There is a server and a client,when client send a message to server,server can send a reply to client. The status of server and client is ESTABLISHED.Then I halt the client,I find the server status is CLOSE_WAIT and the client status is FIN_WAIT_2. Many minutes passed,I find the the server status... (1 Reply)
Hi,
I want to kill TCP connections which have status as TIME_WAIT & no PID
(as per the output of the "netstat - p" command).
Is there any command/utility available to kill connections to a specific port or IP address.
The problem is that these connections don't have process ID (see... (4 Replies)
Does anyone know if there is a C API call to get the status of a TCP port? As opposed to running netstat and parsing the results. At the moment I have to attempt to bind() and pick up on the address in use error which isn't very elegant
Thanks
---------- Post updated at 10:42 AM ----------... (0 Replies)
Hello Friends,
Hope you are doing well.
I just need a help in executing multiple processes.
I've written a shell script which calls another scritps. But the problem is there are too many processes to run, and each process takes about a min to finish its execution.
So, I want to just... (3 Replies)
Hi
The clients connect to my server -using port 9130. But no client could connect to my server at this time. I've checked already and this is the result
netstat -Aan|grep -v 127.0.0.1|grep 9130|pg
f10006000abcb398 tcp4 10313 0 10.0.89.81.9130 10.158.70.24.1705 CLOSE_WAIT... (8 Replies)
Discussion started by: bobochacha29
8 Replies
LEARN ABOUT DEBIAN
ipc::open2
IPC::Open2(3perl) Perl Programmers Reference Guide IPC::Open2(3perl)NAME
IPC::Open2 - open a process for both reading and writing using open2()
SYNOPSIS
use IPC::Open2;
$pid = open2(*CHLD_OUT, *CHLD_IN, 'some cmd and args');
# or without using the shell
$pid = open2(*CHLD_OUT, *CHLD_IN, 'some', 'cmd', 'and', 'args');
# or with handle autovivification
my($chld_out, $chld_in);
$pid = open2($chld_out, $chld_in, 'some cmd and args');
# or without using the shell
$pid = open2($chld_out, $chld_in, 'some', 'cmd', 'and', 'args');
waitpid( $pid, 0 );
my $child_exit_status = $? >> 8;
DESCRIPTION
The open2() function runs the given $cmd and connects $chld_out for reading and $chld_in for writing. It's what you think should work when
you try
$pid = open(HANDLE, "|cmd args|");
The write filehandle will have autoflush turned on.
If $chld_out is a string (that is, a bareword filehandle rather than a glob or a reference) and it begins with ">&", then the child will
send output directly to that file handle. If $chld_in is a string that begins with "<&", then $chld_in will be closed in the parent, and
the child will read from it directly. In both cases, there will be a dup(2) instead of a pipe(2) made.
If either reader or writer is the null string, this will be replaced by an autogenerated filehandle. If so, you must pass a valid lvalue
in the parameter slot so it can be overwritten in the caller, or an exception will be raised.
open2() returns the process ID of the child process. It doesn't return on failure: it just raises an exception matching "/^open2:/".
However, "exec" failures in the child are not detected. You'll have to trap SIGPIPE yourself.
open2() does not wait for and reap the child process after it exits. Except for short programs where it's acceptable to let the operating
system take care of this, you need to do this yourself. This is normally as simple as calling "waitpid $pid, 0" when you're done with the
process. Failing to do this can result in an accumulation of defunct or "zombie" processes. See "waitpid" in perlfunc for more
information.
This whole affair is quite dangerous, as you may block forever. It assumes it's going to talk to something like bc, both writing to it and
reading from it. This is presumably safe because you "know" that commands like bc will read a line at a time and output a line at a time.
Programs like sort that read their entire input stream first, however, are quite apt to cause deadlock.
The big problem with this approach is that if you don't have control over source code being run in the child process, you can't control
what it does with pipe buffering. Thus you can't just open a pipe to "cat -v" and continually read and write a line from it.
The IO::Pty and Expect modules from CPAN can help with this, as they provide a real tty (well, a pseudo-tty, actually), which gets you back
to line buffering in the invoked command again.
WARNING
The order of arguments differs from that of open3().
SEE ALSO
See IPC::Open3 for an alternative that handles STDERR as well. This function is really just a wrapper around open3().
perl v5.14.2 2011-09-26 IPC::Open2(3perl)