ttdt_Xt_input_handler()

[prashanth_14]

Hi Admins,

On my 9000/800/N4000-55 running B.11.00 everyday messages are logged related to ttsession not running. I don't have any idea of this error message, could someone kindly help.

syslog: libtt[12308]: ttdt_Xt_input_handler(): tttk_message_receive(): TT_ERR_NOMP^INo ttsession process is running, probably because tt_open() has not been called yet. If this code is returned from tt_open() it means ttsession could not be started, which generally means ToolTalk is not installed on this system.

Regards
Prashanth

[Abdul Ahad.H]

Hi Prasanth,

You can ignore this error.


ToolTalk is a SunSoft product for network data interchange. In 1992, several companies formed a consortium to develop what has become the Common Desktop Environment (CDE).

CDE uses ToolTalk as a messaging system. ToolTalk authorization is an authentication mechanism that was implemented in response to CERT advisory CA- 99-11. ToolTalk authorization is a scheme where ToolTalk clients and servers can communicate securely using a "cookie", per the MIT-MAGIC-COOKIE-1 scheme (as used in "xauth"). Upon initialization, the ToolTalk session server (/usr/dt/bin/ttsession) generates a cookie and clients that wish to communicate with that server must use the same cookie.

Since CDE on an HP-UX 10.20 system uses a form of socket communication, it does not REQUIRE that the ToolTalk daemon be running for proper functionality.

RESOLVING THE "TT_ERR_NOMP^INo ttsession process" ERROR MESSAGE

This error message occurs when ttsession exits before other CDE processes, which expect to communicate with ttsession when the user logs out.

Each process exits successfully; therefore, these error messages can be ignored. However, it is possible to re-route these error messages to a separate log file (i.e., /var/adm/syslog/userlog.log), while continuing to log all other messages of greater severity or priority to the standard syslog file.

To reroute these messages, edit the /etc/syslog.conf file on your system and add the following line after the "*.info" entry:



user.info /var/adm/syslog/userlog.log
NOTE: More specific entries must come last.

NOTE: Ensure that you have a tab, NOT just a space, between user.info and /var/adm/syslog/userlog.log.

To make syslogd, re-read its configuration file, send it a HANGUP signal:

kill -HUP `cat /var/run/syslog.pid`

Please refer to the man pages for syslog and syslogd for more information.

From man syslog:

The level signifies the urgency of the message, and facility
signifies the subsystem generating the message.

LOG_USER Messages generated by random user processes. This
is the default facility identifier if none is
specified.

LOG_INFO Informational messages.




Regards,

A Ahad