×
The internal search function is temporarily non-functional. The current search engine is no longer viable and we are researching alternatives.
As a stop gap measure, we are using Google's custom search engine service.
If you know of an easy to use, open source, search engine ... please contact support@midrange.com.
beppecosta@xxxxxxxxxxx wrote:
I'have a socket server that spawns 10 workers. The server
waits on 'accept' (on a free high port - 52054 - defined
in the Service Table Entry), while the workers wait on a
dtaq.
You might consider changing this to use sendmsg/recvmsg on a socket
pair. That would perform better, and have fewer errors (in my
experience, anyway) than the old data queue technique.
CPC1224 Completion 50 11/09/07 11:53:11,246936
QWTPITP2 QSYS 0601 *EXT
Message . . . . : Job ended abnormally.
Cause . . . . . : A SIGTERM signal was received for the
job. The action for the signal was to terminate the job.
Sounds like they all received the SIGTERM signal. At the same time. Was
the subsystem ended, by chance? That would cause this. It's possible
to manually send SIGTERM to each process using the kill() API, or the
'kill' QShell command, but that would require a program to be written,
or a user to run the command.
By constrast, ending the subsystem, or ending all of the jobs, would
send this signal to all of them automatically.
You can write code (via the sigaction() API) that will catch and ignore
SIGTERM if you like.
This mailing list archive is Copyright 1997-2024 by midrange.com and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available on our policy page. If you have questions about this, please contact
[javascript protected email address].
Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.
midrange.com
