Databases
StackOverflow2013
Postsdbo
PO
 

Note that there are some explanatory texts on larger screens.

plurals
  1. PO
    primarykey
    data
    text
    <p>from libevent's source code (v2.0.19-stable)</p> <blockquote> <p>/* signal.c</p> <p>This is the signal-handling implementation we use for backends that don't have a better way to do signal handling. It uses sigaction() or signal() to set a signal handler, and a socket pair to tell the event base when</p> <p>Note that I said "the event base" : only one event base can be set up to use this at a time. For historical reasons and backward compatibility, if you add an event for a signal to event_base A, then add an event for a signal (any signal!) to event_base B, event_base B will get informed about the signal, but event_base A won't.</p> <p>It would be neat to change this behavior in some future version of Libevent. kqueue already does something far more sensible. <strong>We can make all backends on Linux do a reasonable thing using signalfd.</strong> */</p> </blockquote> <p>so right now libevent uses sigaction() if it's available, and, failing that, signal().</p> <p>if you use signalfd() you usually block the signal using sigprocmask so that the signals won't cause the default handlers to execute. then, you can monitor the returned file handle using libevent and handle the signal from normal synchronous code safely, without having to worry about memory safety or blocking or interrupting other syscalls.</p> <p>there are restrictions on what you can safely do inside classic asynchronous signal handlers (i.e. those registered using sigaction). See the "Async-signal-safe functions" in man signal. Using the signalfd approach, these restrictions are greatly lessened.</p> <p>the warning about registering a timer callback was likely put there as a concern because libevent supports so many platforms, and at least one person reported problems. note that if you are selecting/polling a file handle registered by signalfd then you don't have to worry about this restriction anyways.</p> <p>EDIT: i re-read your question and realized I hadn't really answered it properly. the benefit of registering a signalfd and then using that in libevent is because it's faster at the expense of portability. there were plans (http://archives.seul.org/libevent/users/Mar-2010/msg00046.html) to include signalfd into libevent but AFAIK it hasn't happened yet.</p> <p>also, once you've been notified of the SIGCHLD you should always call waitpid in a loop until you get ENOCHLD because both methods will collapse multiple occurences of the signal.</p>
    singulars
    1. This table or related slice is empty.
    1. POlibevent & signal handling (SIGCHLD specifically)
      singulars
      1. PTQuestion
    1. PTAnswer
    1. USMax DeLiso
    1. USMax DeLiso
    plurals
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. POlibevent & signal handling (SIGCHLD specifically)
      singulars
      1. PTQuestion
    1. This table or related slice is empty.
    1. VO
      singulars
      1. PO
      1. This table or related slice is empty.
      1. VTAcceptedByOriginator
    2. VO
      singulars
      1. PO
      1. This table or related slice is empty.
      1. VTUpMod
    3. VO
      singulars
      1. PO
      1. This table or related slice is empty.
      1. VTUpMod
    1. COFully agree/understand about the collapse/`waitpid` loop, and the single event base can receive signal events and thus the benefit of `signalfd`. But I still think that if there are platforms, environments where signal events cannot run in the dispatcher loop, and/or other events cannot be scheduled/added that signal events should be disabled those platforms (can you tell I didn't like the warning? :) ). Thanks!
      singulars
      1. PO
      1. USnhed
 

Querying!

 
Guidance
A row detail

Detail views are divided into sections. All the information in the data section comes from columns in the selected row. The other sections display data from other, related rows.

Related data can be related in a to-one or a to-many fashion. Captions of data related in a to-many fashion link to a list view showing a filtered view of the table.

Try moving around until you find a non-empty to-many entry and click on the label to get to one. You can move back to the root by clicking on the database name in the header.

SQuiL has stopped working due to an internal error.

If you are curious you may find further information in the browser console, which is accessible through the devtools (F12).

Reload