Hi,
Program A: uses pipe()
I am able to read the stdout of PROGAM B (stdout got through system() command) into PROGRAM A using:
* child
-> dup2(fd, STDOUT_FILENO);
-> execl("/path/PROGRAM B", "PROGRAM B", NULL);
* parent
-> char line;
-> read(fd, line, 100);
Question:
---------... (1 Reply)
Hi,
Program A: uses pipe()
I am able to read the stdout of PROGAM B (stdout got through system() command) into PROGRAM A using:
* child
-> dup2(fd, STDOUT_FILENO);
-> execl("/path/PROGRAM B", "PROGRAM B", NULL);
* parent
-> char line;
-> read(fd, line, 100);
Question:... (2 Replies)
Hello,
I have a script that monitors files uploaded via ftp. After a successful upload, the file name is written to the pipe.
There is another program that reads this pipe and allows automatically run any program or script ( say test.sh ) to process the newly uploaded file.
cat test.sh... (2 Replies)
Hi,
Program A: uses pipe()
I am able to read the stdout of PROGAM B (stdout got through system() command) into PROGRAM A using:
* child
-> dup2(fd, STDOUT_FILENO);
-> execl("/path/PROGRAM B", "PROGRAM B", NULL);
* parent
-> char line;
-> read(fd, line, 100);
Question:
---------... (3 Replies)
I have the following code which works on AIX 4.3 but fails at times on AIX 5.3
with:
cat: 0652-054 cannot write to output. There is no process to read data written to a pipe.
validator="${validator_exe} ${validator_parms}"
cmd_line="${CAT} ${data_file} | ${validator}... (6 Replies)
Hi Everyone,
The machine I'm working on is an AIX 5.3 LPAR running on a P650. oslevel -r shows 5300-08. I'm trying to take a backup to a SCSI tape drive, which has been working up until this point. I know of nothing that has changed recently to cause this problem. But when I try to take a... (0 Replies)
We use SAP application cluster on AIX. Communication between 2 of its instances is failing randomly with the following error:
java.net.SocketException: There is no process to read data written to a pipe.
The above error causes a cluster restart if an important communication fails.
Can... (0 Replies)
Hi,
Hopefully someone can help.
We have a process that writes a file using Connect Direct to our local Solaris server and then our C++ program will pick up the file and process it. Unfortunately, because of the size of the file, the C++ program is processing the file before it has finished... (7 Replies)
Subject: Debugging a program written in two languages
Platform: Linux (Kubuntu)
I am trying to debug a C application with bindings to some simple functions written in Ada using the GNAT Programming Studio IDE (GPS). The main entry point is in C. The debugger is gdb.
I managed to compile... (0 Replies)
Hello friends! i am writing a code in which i take inputs (numbers) from user and count the total number of positive, negative and zeros entered. I need to clear my standard input buffer before scanf() command. My compiler is completely ignoring the fflush(stdin) command. its not even showing any... (1 Reply)
Discussion started by: Abhishek_kumar
1 Replies
LEARN ABOUT OSX
t_error
t_error(3NSL) Networking Services Library Functions t_error(3NSL)NAME
t_error - produce error message
SYNOPSIS
#include <xti.h>
int t_error(const char *errmsg);
DESCRIPTION
This routine is part of the XTI interfaces which evolved from the TLI interfaces. XTI represents the future evolution of these interfaces.
However, TLI interfaces are supported for compatibility. When using a TLI routine that has the same name as an XTI routine, the tiuser.h
header file must be used. Refer to the TLI COMPATIBILITY section for a description of differences between the two interfaces.
The t_error() function produces a message on the standard error output which describes the last error encountered during a call to a trans-
port function. The argument string errmsg is a user-supplied error message that gives context to the error.
The error message is written as follows: first (if errmsg is not a null pointer and the character pointed to be errmsg is not the null
character) the string pointed to by errmsg followed by a colon and a space; then a standard error message string for the current error
defined in t_errno. If t_errno has a value different from TSYSERR, the standard error message string is followed by a newline character.
If, however, t_errno is equal to TSYSERR, the t_errno string is followed by the standard error message string for the current error defined
in errno followed by a newline.
The language for error message strings written by t_error() is that of the current locale. If it is English, the error message string
describing the value in t_errno may be derived from the comments following the t_errno codes defined in xti.h. The contents of the error
message strings describing the value in errno are the same as those returned by the strerror(3C) function with an argument of errno.
The error number, t_errno, is only set when an error occurs and it is not cleared on successful calls.
EXAMPLES
If a t_connect(3NSL) function fails on transport endpoint fd2 because a bad address was given, the following call might follow the failure:
t_error("t_connect failed on fd2");
The diagnostic message to be printed would look like:
t_connect failed on fd2: incorrect addr format
where incorrect addr format identifies the specific error that occurred, and t_connect failed on fd2 tells the user which function failed
on which transport endpoint.
RETURN VALUES
Upon completion, a value of 0 is returned.
VALID STATES
All - apart from T_UNINIT
ERRORS
No errors are defined for the t_error() function.
TLI COMPATIBILITY
The XTI and TLI interface definitions have common names but use different header files. This, and other semantic differences between the
two interfaces are described in the subsections below.
Interface Header
The XTI interfaces use the header file, xti.h. TLI interfaces should not use this header. They should use the header:
#include <tiuser.h>
Error Description Values
The t_errno value that can be set by the XTI interface and cannot be set by the TLI interface is:
TPROTO
ATTRIBUTES
See attributes(5) for descriptions of the following attributes:
+-----------------------------+-----------------------------+
| ATTRIBUTE TYPE | ATTRIBUTE VALUE |
+-----------------------------+-----------------------------+
|MT Level |Safe |
+-----------------------------+-----------------------------+
SEE ALSO t_errno(3NSL)strerror(3C), attributes(5)SunOS 5.10 7 May 1998 t_error(3NSL)