[Search for users]
[Overall Top Noters]
[List of all Conferences]
[Download this site]
Title: | Proudly built by the engineers of NaC Australia |
|
Moderator: | DELNI::MUGGERIDGE |
|
Created: | Mon Oct 12 1992 |
Last Modified: | Fri Jun 06 1997 |
Last Successful Update: | Fri Jun 06 1997 |
Number of topics: | 908 |
Total number of notes: | 3829 |
889.0. "Question about the 'libx25_r' signal handler" by TAGEIN::AURAND () Sat Apr 19 1997 02:02
Hi,
a customer of us has send us the following question and it would be nice, if
someone can tell us a little bit more about the libx25_r API.
'We are using X.25 and DECss7 APIs in a multi-threaded environment. We
currently experience various problems in DECss7 and the suspicion is
that X.25 might be using signals which DECss7 has reseved for its use.
That's why we urgently need to know, if the X.25 APIs within 'libx25_r'
establish their own signal handler. If yes:
which signals and how are they handled (default, ignore, own handler)'
Many thanks for your help
Andreas
T.R | Title | User | Personal Name | Date | Lines |
---|
889.1 | exit | DELNI::MUGGERIDGE | | Sat Apr 19 1997 04:58 | 8 |
| In numerous modules we use a handler for SIGPIPE which just ignores it.
However the handler is promptly returned to the orginal handler before
exiting.
What signals in particular are you having trouble with?
Matt.
|