On Thu, Sep 14, 2000 at 09:17:16PM +0530, Santosh Dawara wrote:
> I would like to add some more info ...
>
> I finally came around to writing the threads for each session that
> the Pop Server will handle, I tested it and despite 'x' sessions
> spawned, 'ps' would show just one process in the list. But this was
> when I used the green option. However, when I used -native,
> not only did ps indicate that some threads with differant PIDS
> spawned by JVM were running as root, also everytime I opened a
> Pop Session this list would grow larger with the new threads
> spawned, and they too were having root privileges.
Do they actually have root privileges (can you actually do something
from those threads you could not otherwise do), or is it just the
reporting that is broken?
Nathan
>
> I hope the fix comes around quick, because running as -green
> is not really a solution.
>
> Thank you,
> Santosh Dawara.
>
> Nathan Meyers wrote:
> >
> > On Thu, Sep 14, 2000 at 04:31:19PM +0200, Juergen Kreileder wrote:
> > > >>>>> "Nathan" == Nathan Meyers <[EMAIL PROTECTED]> writes:
> > >
> > > Nathan> If using green threads solves the problem, then you
> > > Nathan> probably didn't really have a problem. All those
> > > Nathan> "processes" are really threads, and they should all share
> > > Nathan> the same privileges, despite what ps reported. If they do
> > > Nathan> not (you might try a test to see), then there is a bug in
> > > Nathan> Linux threads.
> > >
> > > It's a known limitation in the current pthreads implementation. It
> > > should get fixed with the improved threads stuff in Linux 2.4/2.5 and
> > > the planned reimplementation of the LinuxThreads library.
> >
> > What is the limitation - that some threads have privileges they shouldn't,
> > or that privileges are not reported properly?
> >
> > Nathan
> >
> > >
> > >
> > > Juergen
> > >
> > > --
> > > Juergen Kreileder, Blackdown Java-Linux Team
> > > http://www.blackdown.org/java-linux.html
> > > JVM'01: http://www.usenix.org/events/jvm01/
>
>
> ----------------------------------------------------------------------
> To UNSUBSCRIBE, email to [EMAIL PROTECTED]
> with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
----------------------------------------------------------------------
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
