those are the native_threads you asked for...
the pthread impl on Linux has each thread take an space in the process
table, which is what ps et al are reading. take a look at the archives for
the list back around end of last year, begining of this one for the gory
details.
cabbey at home dot n
While trying to get apache jserv to work, I kept getting errors about not being
able to resolve the hostname "localhost".
Thus I went browsing and found a few simple programs, none of which I could get
to work properly. Here is the one that I found most useful:
import java.net.*;
class HostCheck
Hi Patrick,
this is the correct behaviour with native threads under linux. The
thread implementation of linux treats processes and threds basically the
same way, they just have different sets of shared vs. non-shared
ressources. One result of this is that any thread shows up in the
process table.
I was wondering anyone could help me and/or point me in
right direction to the following issue I have with Linux and
JDK117/JDK1.2;
I seem to have multiple process instances when ever I issue
the interpreter ($JAVA_HOME/bin/jre, $JAVA_HOME/bin/java) with any versions of
Linux that I have
Eric vanberkel wrote:
>
> Folks,
>
> Though I'm confessin' that I read a bit less than I should
> maybe,
They (Sun) changed how the $CLASSPATH environment variable and the -cp
and the -classpath command line options work when they went from JDK
1.1.x to 1.2.
The change is for the better. The
Folks,
Though I'm confessin' that I read a bit less than I should
maybe, why do applets in JDK 1.2 ignore my $CLASSPATH?
It worked with JDK 1.1.4 on my TurboLinux.
After installing, the applicable text to read says:
'No $CLASSPATh, no $JAVA_HOME, just run it!"
Fairly enthusiastic that, but what
Yes, Greg,
and it's the most stupid thing they invented at SUN because
now you have to juggle with most filemanagers extension
feature to execute a java class program.
Moreover, since the sacred URL needs every character of a
given path, it would be suitable if that went for .class
too. Anyway, w
Actually, libXm.so is Motif, which is required by AWT, and therefore
Java. You'll need to get a Motif distribution (I use RedHat Motif 2.1.10
with no problems).
--Jeff
Carsten Hoeger wrote:
>
> On Tue, Sep 28, Rolf wrote:
>
> > I am running a SuSe Linux 6.1 on my box and have libc 2 installe
