- Community Home
- >
- Servers and Operating Systems
- >
- Operating Systems
- >
- Operating System - HP-UX
- >
- SIG_IGN does not work
Operating System - HP-UX
1753807
Members
7985
Online
108805
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
Discussions
Discussions
Forums
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
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
тАО10-10-2009 12:09 AM
тАО10-10-2009 12:09 AM
Re: SIG_IGN does not work
>We can not daemonize our child process, since have option in parent process to kill child process in case of timeout.
Just hunt down the demon and kill it?
Of course if you can do this, you can also hunt down your zombies and kill them too. :-)
Back to your original problem. You could call waitpid with WNOHANG to do a poll of your child processes every hour or so.
>2. how to subvert the calls to sigprocmask?
Set a breakpoint there and analyze the mask and then change it to not block signal 11.
Or write function called sigprocmask, analyze and change the parms and then call _sigprocmask to do the work.
>3. Yes we have one thread in parent process.
You have created one additional thread?
Just hunt down the demon and kill it?
Of course if you can do this, you can also hunt down your zombies and kill them too. :-)
Back to your original problem. You could call waitpid with WNOHANG to do a poll of your child processes every hour or so.
>2. how to subvert the calls to sigprocmask?
Set a breakpoint there and analyze the mask and then change it to not block signal 11.
Or write function called sigprocmask, analyze and change the parms and then call _sigprocmask to do the work.
>3. Yes we have one thread in parent process.
You have created one additional thread?
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО12-15-2009 10:54 PM
тАО12-15-2009 10:54 PM
Re: SIG_IGN does not work
1.Yes we have one more thread in our parent process.
2.I read on article, in that they mentioned that sigprocmask() will have undesired results in multithreaded application. So i think we can't use sigprocmask() in our application.
Is there any other way to resolve this problem?
2.I read on article, in that they mentioned that sigprocmask() will have undesired results in multithreaded application. So i think we can't use sigprocmask() in our application.
Is there any other way to resolve this problem?
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО12-16-2009 03:58 AM
тАО12-16-2009 03:58 AM
Re: SIG_IGN does not work
>1. Yes we have one more thread in our parent process.
So you are multithreaded.
>2. in that they mentioned that sigprocmask will have undesired results in multithreaded application. So I think we can't use sigprocmask in our application.
The purpose of fiddling with sigprocmask(2) is to prevent the blocking of signal 11 so you can debug.
After 4 months and no points, it's probably time to contact the Response Center.
So you are multithreaded.
>2. in that they mentioned that sigprocmask will have undesired results in multithreaded application. So I think we can't use sigprocmask in our application.
The purpose of fiddling with sigprocmask(2) is to prevent the blocking of signal 11 so you can debug.
After 4 months and no points, it's probably time to contact the Response Center.
- « Previous
-
- 1
- 2
- Next »
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.
News and Events
Support
© Copyright 2024 Hewlett Packard Enterprise Development LP