HPE GreenLake Administration
- Community Home
- >
- Servers and Operating Systems
- >
- Operating Systems
- >
- Operating System - Linux
- >
- Unexpected SIGCHLD
Operating System - Linux
1828490
Members
2724
Online
109978
Solutions
Forums
Categories
Company
Local Language
back
Forums
Discussions
Forums
- Data Protection and Retention
- Entry Storage Systems
- Legacy
- Midrange and Enterprise Storage
- Storage Networking
- HPE Nimble Storage
Discussions
Forums
Discussions
Discussions
Discussions
Forums
Discussions
back
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
- BladeSystem Infrastructure and Application Solutions
- Appliance Servers
- Alpha Servers
- BackOffice Products
- Internet Products
- HPE 9000 and HPE e3000 Servers
- Networking
- Netservers
- Secure OS Software for Linux
- Server Management (Insight Manager 7)
- Windows Server 2003
- Operating System - Tru64 Unix
- ProLiant Deployment and Provisioning
- Linux-Based Community / Regional
- Microsoft System Center Integration
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Blogs
Information
Community
Resources
Community Language
Language
Forums
Blogs
Topic Options
- Subscribe to RSS Feed
- Mark Topic as New
- Mark Topic as Read
- Float this Topic for Current User
- Bookmark
- Subscribe
- Printer Friendly Page
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
06-07-2007 01:08 AM
06-07-2007 01:08 AM
Unexpected SIGCHLD
Hi,
A program I wrote is started through inetd and handles input/output through stdin/stdout. It runs fine on my HP-UX 9000/800 single CPU box.
When moving towards another 9000/800 with 4 CPU the program unexpectedly crashes and does so after receiving a SIGCHLD. Can it be that the difference is in the multiprocessor arrangement? The program on the first machine does not receive the SIGCHLD...
I do not create children myself (in C that is...) but I have linked some BEA Tuxedo 8.1 libraries that may create threads that I am not aware of.
Any hints on where to start looking for this behaviour?
Thanks,
Joost
A program I wrote is started through inetd and handles input/output through stdin/stdout. It runs fine on my HP-UX 9000/800 single CPU box.
When moving towards another 9000/800 with 4 CPU the program unexpectedly crashes and does so after receiving a SIGCHLD. Can it be that the difference is in the multiprocessor arrangement? The program on the first machine does not receive the SIGCHLD...
I do not create children myself (in C that is...) but I have linked some BEA Tuxedo 8.1 libraries that may create threads that I am not aware of.
Any hints on where to start looking for this behaviour?
Thanks,
Joost
- Tags:
- SIGCHLD
2 REPLIES 2
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
06-07-2007 02:04 AM
06-07-2007 02:04 AM
Re: Unexpected SIGCHLD
I suspect that your single CPU box was working more or less by accident in that the real problem is timing related. Of course, without a stack trace or at least some tusc output, it's not possible to know what is wrong. The fix may be as simple as adding a signal handler for SIGCHLD.
If it ain't broke, I can fix that.
- Tags:
- tusc
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
06-10-2007 06:05 PM
06-10-2007 06:05 PM
Re: Unexpected SIGCHLD
The tusc trace provided me with exactly what I needed. I turned out that I hit the maxfiles kernel limit somewhere so I changed my piece of code that was the cause.
What I still do not know why this causes a SIGCHLD. nice to find out but I'm happy already :-)
What I still do not know why this causes a SIGCHLD. nice to find out but I'm happy already :-)
The opinions expressed above are the personal opinions of the authors, not of Hewlett Packard Enterprise. By using this site, you accept the Terms of Use and Rules of Participation.
Company
Support
Events and news
Customer resources
© Copyright 2025 Hewlett Packard Enterprise Development LP