Hi!
I´ve an application that runs in a Digital Tru64, exporting display to a Linux host.
That application blinks a icon (in XPM mode) when the severity mode changes.
When I put a backdrop(XPM, too) in that screen, the icons blink slowly. When I remove it, they turn to blink quickly.
I have... (3 Replies)
hello to begin i sorry for my english because i'am french so:
someone can explain me to do a export DIPLAY with a web page (php)
i have test the php function exec (myscriptshell.sh) but he can't do the export diplay. if someone have a solution .
bye (1 Reply)
I'm trying to open an xwindow on my Sun server. What am I doing wrong?
# echo $SHELL
/sbin/sh
#
# export DISPLAY=localhost:0.0
DISPLAY=localhost:0.0: is not an identifier
Thank you! (1 Reply)
hi
I wanted to export the display of all directories of home with their respective subdirectories and files if any on my local pc.
this home directory is of some remote machine .
using ssh remote login and then using struct direct i can just gate name list of directories .
but not the display... (2 Replies)
Hi Frnds,
i face a peculiar issue.
I am managing 200 Aix workstations and 20 sun boxes.
I am not anle to export the display from aix workstations to sun box,
But vice versa it is working fine.
But if i try to export the display to a sun box from other sun box it works perfectly.
Could... (3 Replies)
HI,
HP-UX B.11.00 A 9000/785 (ta)
I am trying to export a display using Xming & and Telnet (not SSH) but when I try..
$ DISPLAY=192.168.1.75:0.0
$ export DISPLAY
$ xclock
and get..
Xlib: connection to "192.168.1.75:0.0" refused by server
Xlib: No protocol specified
Error:... (4 Replies)
hello frnds,
I want to export display of othe terminal to my terminal and want to post a msg, which should visible at other terminal,
I tried myself, but couldnt get it
plz help me to get solution (1 Reply)
Hi All,
I use "export DISPLAY=same_host:0.0" to set my export DISPLAY and it is working fine for me..
Problem here is I have developed a script for which i should run export DISPLAY prior to running my script....
so my script should check whether export DISPLAY is set or not.. if... (6 Replies)
Discussion started by: smarty86
6 Replies
LEARN ABOUT REDHAT
com_err
COM_ERR(3) Library Functions Manual COM_ERR(3)NAME
com_err - common error display routine
SYNOPSIS
#include <et/com_err.h>
void com_err (whoami, code, format, ...);
const char *whoami;
long code;
const char *format;
proc = set_com_err_hook (proc);
void (* proc ) (const char *, long, const char *, va_list);
proc = reset_com_err_hook ();
void initialize_XXXX_error_table ();
DESCRIPTION
Com_err displays an error message on the standard error stream stderr (see stdio(3S)) composed of the whoami string, which should specify
the program name or some subportion of a program, followed by an error message generated from the code value (derived from compile_et(1)),
and a string produced using the format string and any following arguments, in the same style as fprintf(3).
The behavior of com_err can be modified using set_com_err_hook; this defines a procedure which is called with the arguments passed to
com_err, instead of the default internal procedure which sends the formatted text to error output. Thus the error messages from a program
can all easily be diverted to another form of diagnostic logging, such as syslog(3). Reset_com_err_hook may be used to restore the behav-
ior of com_err to its default form. Both procedures return the previous ``hook'' value. These ``hook'' procedures must have the declara-
tion given for proc above in the synopsis.
The initialize_XXXX_error_table routine is generated mechanically by compile_et(1) from a source file containing names and associated
strings. Each table has a name of up to four characters, which is used in place of the XXXX in the name of the routine. These routines
should be called before any of the corresponding error codes are used, so that the com_err library will recognize error codes from these
tables when they are used.
The com_err.h header file should be included in any source file that uses routines from the com_err library; executable files must be
linked using ``-lcom_err'' in order to cause the com_err library to be included.
SEE ALSO compile_et(1), syslog(3).
Ken Raeburn, "A Common Error Description Library for UNIX".
SIPB 22 Nov 1988 COM_ERR(3)