[omniORB] omniNames dropping core

[Srinivasan Renganathan]

I am facing a strange problem. Starting the omniNames in Solaris 10 is not having any problem, but if I start in Solaris 11, I am getting core drop -- it is failing while calling pthread_setschedparam(t->posix_thread, SCHED_OTHER, &sparam) with EPERM error. After debugging found that if we run with sudo access it is working fine. But for security reason we don't want that way.



Any suggestions please?



Regards,

Srini.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://www.omniorb-support.com/pipermail/omniorb-list/attachments/20120831/61b3e3c1/attachment.html>

[Duncan Grisby]

Post by Srinivasan Renganathan
I am facing a strange problem. Starting the omniNames in Solaris 10 is
not having any problem, but if I start in Solaris 11, I am getting
core drop -- it is failing while calling
pthread_setschedparam(t->posix_thread, SCHED_OTHER, &sparam) with
EPERM error. After debugging found that if we run with sudo access
it is working fine. But for security reason we don?t want that way.

I think there has been a change to Solaris to require new permissions to
change thread priorities. Perhaps you are in a position to confirm or
deny that?

omniORB doesn't actually make use of thread priorities, so you can
disable omnithread's support for them. Try the attached patch. You need
to re-run the configure script after this. Does it work?

Cheers,

Duncan.
--
-- Duncan Grisby --
-- duncan at grisby.org --
-- http://www.grisby.org --

-------------- next part --------------
A non-text attachment was scrubbed...
Name: solaris_no_priority.patch
Type: text/x-patch
Size: 556 bytes
Desc: not available
URL: <http://www.omniorb-support.com/pipermail/omniorb-list/attachments/20120831/c56ada58/attachment.bin>