On Wed, Feb 24, 2010 at 10:37 AM, Joerg Schilling <Joerg.Schilling at fokus.fraunhofer.de> wrote: > ????? ???????????? <olga.kryzhanovska at gmail.com> wrote: > >> It is not possible to implement a compile time flag which defines the >> number of real time signals. RTSIG_MAX is a global property of the >> operating system. >> >> Just think this proposal through: >> What if kill -RTMIN+62 82939 is send to a process which is not >> compiled with this flag? Should it ignore the signal, call abort() or >> panic the system? > > signal()/sigaction()/.... do not accept more than NSIG > >> What if a script uses /bin/getconf RTSIG_MAX to determinate the number >> of real time signals - getconf being compiled with your proposed flag >> - and the shell is not compiled with your proposed compile time flag >> and supports 8 signals only? > > /bin/getconf RTSIG_MAX always returns 8 on Solaris. getconf does not > call sysconf() for this property.
As usual you don't do research before making such claims: /usr/bin/getconf RTSIG_MAX calls sysconfig(_CONFIG_RTSIG_MAX) = 8 > > Please first verify that there is a real need for more RT signals before > looking for a solution. My company does have real need for more RT signals to migrate away from AIX. If Solaris engineering sees itself unable to jump over its conservative shadow, i.e. is unable to bump the value to 64 than its fine for me, there are two alternative operating systems which meet this requirement. > Linux offers 32 RT signals and the only need I see is to support 32 for > Linux compatibility. Linux is not the only operating system which should be used as source of Opensolaris project "copy-innovations". Do some research. Irek
