Sign Up

Sign Up to our social questions and Answers Engine to ask questions, answer people’s questions, and connect with other people.

Have an account? Sign In

Have an account? Sign In Now

Sign In

Login to our social questions & Answers Engine to ask questions answer people’s questions & connect with other people.

Sign Up Here

Forgot Password?

Don't have account, Sign Up Here

Forgot Password

Lost your password? Please enter your email address. You will receive a link and will create a new password via email.

Have an account? Sign In Now

You must login to ask a question.

Forgot Password?

Need An Account, Sign Up Here

Please briefly explain why you feel this question should be reported.

Please briefly explain why you feel this answer should be reported.

Please briefly explain why you feel this user should be reported.

Sign InSign Up

The Archive Base

The Archive Base Logo The Archive Base Logo

The Archive Base Navigation

  • SEARCH
  • Home
  • About Us
  • Blog
  • Contact Us
Search
Ask A Question

Mobile menu

Close
Ask a Question
  • Home
  • Add group
  • Groups page
  • Feed
  • User Profile
  • Communities
  • Questions
    • New Questions
    • Trending Questions
    • Must read Questions
    • Hot Questions
  • Polls
  • Tags
  • Badges
  • Buy Points
  • Users
  • Help
  • Buy Theme
  • SEARCH
Home/ Questions/Q 7672231
In Process

The Archive Base Latest Questions

Editorial Team
  • 0
Editorial Team
Asked: May 31, 20262026-05-31T16:14:17+00:00 2026-05-31T16:14:17+00:00

Is ( SIGRTMIN + 1 ) safe for inter-process communication? Will it change in

  • 0
  1. Is (SIGRTMIN + 1) safe for inter-process communication? Will it change in different processes?

  2. Are there any differences to use sigqueue(2) or kill(2) to send standard signals and real time signals?
    If I use sigqueue(2) to send a series of SIGUSR1(standard signals) and handle them slowly, are there mutiple instances of SIGUSR1 in the queue?
    What about using kill(2) to send SIGRTMIN(real time signals)? Will they be queued?

  • 1 1 Answer
  • 0 Views
  • 0 Followers
  • 0
Share
  • Facebook
  • Report

Leave an answer
Cancel reply

You must login to add an answer.

Forgot Password?

Need An Account, Sign Up Here

1 Answer

  • Voted
  • Oldest
  • Recent
  • Random
  1. Editorial Team
    Editorial Team
    2026-05-31T16:14:19+00:00Added an answer on May 31, 2026 at 4:14 pm

    sigqueue() can be used to send only real time signals and kill() can be used to send only standard signals. I haven’t tried sending the wrong signal with either API. But I would expect it to fail with some appropriate errno. Linux doesn’t queue standard signals. Real time signals are queued. The max number of real time signals that can be queued is defined as RLIMIT_SIGPENDING

    You can use any real time signal as long as the receiver has the handler setup for the particular signal sender is sending.

    EDIT

    I was wrong earlier in my answer. It looks like kill() can send real-time signals too. But from the comment in __send_signal() it looks like using kill to send real-time signals might not have the desired effect in some cases, ie: signals may not get queued.

       /*
         * Real-time signals must be queued if sent by sigqueue, or
         * some other real-time mechanism.  It is implementation
         * defined whether kill() does so.  We attempt to do so, on
         * the principle of least surprise, but since kill is not
         * allowed to fail with EAGAIN when low on memory we just
         * make sure at least one signal gets delivered and don't
         * pass on the info struct.
         */
    
    • 0
    • Reply
    • Share
      Share
      • Share on Facebook
      • Share on Twitter
      • Share on LinkedIn
      • Share on WhatsApp
      • Report

Sidebar

Related Questions

I'd like to automatically kill a command after a certain amount of time. I
If we use sigaction to define a signal handler, then why don't we need
After moving my mod_perl site from Linux hosting to FreeBSD, I have this error
i have written a small piece of code. This code first blocks the {SIGSEGV},
Can someone tell me, as to why program1's signal handler is not working? Program1:
I have put a simple signal handler in my code. I have initialised the
Please check the following code #include <stdio.h> #include <string.h> #include <stdlib.h> #include <termios.h> #include
The code I'm working with has a shared signal handler that switches on the

Explore

  • Home
  • Add group
  • Groups page
  • Communities
  • Questions
    • New Questions
    • Trending Questions
    • Must read Questions
    • Hot Questions
  • Polls
  • Tags
  • Badges
  • Users
  • Help
  • SEARCH

Footer

© 2021 The Archive Base. All Rights Reserved
With Love by The Archive Base

Insert/edit link

Enter the destination URL

Or link to existing content

    No search term specified. Showing recent items. Search or use up and down arrow keys to select an item.