According to [EMAIL PROTECTED]: While burning my CPU.
>
> Richard,
>
> You seem to imply that one can only start one session of Netscape, and then
> in addition only Netscape side applications, not another main session itself.
> If so, that's not been my experience. I run 2-3 separate sessions of the
> Communicator itself frequently.
If that is the case then that is possably why you cant kill the process in
the first place.
There *must* be a lock_file in your ~/.netscape directory.
Just to see what happens here is the text netscape gives when you try to
open another netscape session from the icon *while* there is already a
netscape session running.
Netscape has detected a /home/pa3gcu/.netscape/lock
file
This may indicate that another user is running
Netscape using your /home/pa3gcu/.netscape files.
It appears to be running on host pa3gcu.ampr.org
under process-ID 4659.
You may continue to use Netscape, but you will
be unable to use the disk chace, global history,
or your personal certificates.
Otherwise, you may choose Cancel, make sure that
you are not running another Netscape Navigator,
delete the /home/pa3gcu/.netscape/lock file, and
restart Netscape.
Now take all that into consideration and you will now know why your having
problems.
>
> Perhaps I misunderstood your point. Just for fun I just opened three sessions
> of Communicator from the menu simultaneously as I write. No problem.
Yup and only ONE will work the way it should, others will just sit there and
"possably do just what you described in your origanal post about i cant kill
the process"
If you want multiple navigator sessions or what ever, use the icon _IN_
netscape itself to open another browuser or what ever, NOT another Netscape
session.
>
> Haines
>
--
Regards Richard.
[EMAIL PROTECTED]
