[omniORB] Using signals with omniORB

[Bjørn Wennberg]

Helmut Swaczinna <Helmut.Swaczinna@wmd.de> writes:

> Hi,
> 
> I've recognized, that some signals are used internaly by omniORB, e.g.
> SIGUSR1 and SIGUSR2. Which other signals are forbidden for application =
use?

Isn't this just for gdb? I beleave that gdb uses these two signals to
switch/catch switching between threads. I'm not sure if they are used
when you run your application outside of gdb. You may want to try that.
Anyway - I had a look through gdb's source the other month - and I think
that gdb ONLY uses sigusr1+2. Thus the rest should be free for you to use.

> 
> But my problem using signals is another one. I'm not shure, if it's a o=
mniORB
> problem or a genarel problem mit multithreaded applications. I can't re=
set my
> signal handler after the first arrival of the signal (Linux!). The seco=
nd
> arrival
> of the signal has no effect, that means my signal handler is not called=
 and
> the application is not terminated. The background is, I want my server =
to
> reload 
> its config data on a signal.

This might be the case where gdb uses sigusr1+2? 

> 
> Any hint for me?
> 
> Thanks
> 
> Helmut
> 
> 
> 

bjornw> cheers
-- 
-------------------------------------------------------
Bjørn Wennberg       email: bjornw@colargol.idb.hist.no 
                        ms: +47 959 92 657