Re: signal vs. sigaction and SIGCHLD

[vilibald wanca]

Doesn't wait call suspend the calling process until the child is terminated?
From man page for wait:

 The wait() function suspends execution of its calling process until
 status information is available for a terminated child process

But in your case the child process is not terminated. If you use the same
pid = waitpid(-1, tstat, WUNTRACED); in case of  signal you'll get
the same result as with sigaction, or that's what I suspect to happen,
haven't had a chance test it.

Vilda


2013/5/21 Polytropon free...@edvax.de

 On Tue, 21 May 2013 15:24:26 +1000, Noel Hunt wrote:
  If I recompile with `#undef SIGACTION', waithandler is not
  called.
 
  I should add that even with the sigaction(2) interface, without
  the `sigprocmask' call, it still doesn't work, which suggests
  that SIGCHLD is being blocked.
 
  Can anyone explain why?

 From reading man 3 signal, I get the following impression:

  NoName Default Action   Description
  20SIGCHLD  discard signal   child status has changed

 The default action is to discard the signal, so the following
 paragraph could make sense:

  The sig argument specifies which signal was received.  The func procedure
  allows a user to choose the action upon receipt of a signal.  To set the
  default action of the signal to occur as listed above, func should be
  SIG_DFL.  A SIG_DFL resets the default action.  To ignore the signal func
  should be SIG_IGN.  This will cause subsequent instances of the signal to
  be ignored and pending instances to be discarded.  If SIG_IGN is not
  used, further occurrences of the signal are automatically blocked and
  func is called.

 From my limited understanding, maybe this could help you find
 an explanation of the observed behaviour?

 Also compare /usr/include/sys/signal.h for the definition of
 the involved typedef's.


 --
 Polytropon
 Magdeburg, Germany
 Happy FreeBSD user since 4.0
 Andra moi ennepe, Mousa, ...
 ___
 freebsd-questions@freebsd.org mailing list
 http://lists.freebsd.org/mailman/listinfo/freebsd-questions
 To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org

drivers for BMC43142 and/or AR8162 chips

[vilibald wanca]

Hi,
I've installed pc-bsd 9.1 and FreeBSD 9.1 on my new laptop ASUS X201E,
which was
originally running ubuntu, after a little struggle to get it booting I
am up and running although I have no network access whatsoever as the
Ethernet device is Atheros AR8162 and the wifi is hybrid
(wifi/bluetooth) Broadcom's
BMC43142. After looking around I'm not sure if there are any bsd drivers
available or any other way to get it running, at least one of them,
preferably the wifi as I can live without wired connection. I've been
thinking about going the ndisgen way but there are no winXP drivers for
these chips. Does ndisgen support ndis 6.2, can I use win7 drivers? Any
ideas what to try or even just a general approach what way to go.
Thanks.

vw.
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org