public inbox for rhdb@sourceware.org
 help / color / mirror / Atom feed
From: John Allgood <john@turbocorp.com>
To: Fernando Nasser <fnasser@redhat.com>, rhdb@sources.redhat.com
Subject: Re: Java Problems
Date: Tue, 20 Jan 2004 21:30:00 -0000	[thread overview]
Message-ID: <400D9DFE.8020803@turbocorp.com> (raw)
In-Reply-To: <400D9CF1.4050001@redhat.com>

Fernando Nasser wrote:

> John,
>
> The Control Center tool will be running as root (under PAM, of course) 
> so your 'root' user must have the JAVA_HOME variable set (and to its 
> PATH as well). Some JVMs set that when they are installed (IBM's used 
> to) other don't (like Sun's).
>
> We have been talking of ways to make our tools smarter in locating 
> Java JVMs by looking at usual places for the most common JVM 
> providers, but there are issues like what to do if there are more than 
> one etc.  Eventually Java will be added to the 'alternatives' 
> configuration and all these problems will go away.
>
> In the meanwhile, set your root users JAVA_HOME and PATH and you 
> should be able to start rhdb-cc.
>
> Regards,
> Fernando
>
> John Allgood wrote:
>
>>  
>>
>> -----Original Message-----
>> From: rhdb-owner@sources.redhat.com 
>> [mailto:rhdb-owner@sources.redhat.com]
>> On Behalf Of Fernando Nasser
>> Sent: Tuesday, January 20, 2004 1:46 PM
>> To: David Jee
>> Cc: John Allgood; rhdb@sources.redhat.com
>> Subject: Re: Java Problems
>>
>> rhdb-cc requires the 'postgres' user password (it should accept the 
>> root password as well).
>>
>> You must 'su -' to become root and then assign a password to the 
>> postgres
>> user with 'passwd postgres'.
>>
>> I tried that still reports unable to find java executable. I already 
>> checked
>> permission
>>
>> When I run which java it gives me
>>  
>> /usr/java/j2re1.4.1_06/bin/java
>>
>>
>
>
>
Thats exactly what I have done. Here is my env for root. As you can see 
JAVA_HOME is set and the path and CLASSPATH is set.

Any Ideas.

PATH=/usr/kerberos/sbin:/usr/kerberos/bin:/usr/java/j2re1.4.1_06/bin:/usr/local/sbin:/usr/local/bin:/sbin:/bin:/usr/sbin:/usr/bin:/usr/X11R6/bin:/root/bin
INPUTRC=/etc/inputrc
PWD=/root
JAVA_HOME=/usr/java/j2re1.4.1_06
LANG=en_US.UTF-8
LAMHELPFILE=/etc/lam/lam-helpfile
SSH_ASKPASS=/usr/libexec/openssh/gnome-ssh-askpass
SHLVL=1
HOME=/root
XPVM_ROOT=/usr/share/pvm3/xpvm
BASH_ENV=/root/.bashrc
LOGNAME=root
CLASSPATH=/usr/share/java/postgresql.jar
LESSOPEN=|/usr/bin/lesspipe.sh %s
DISPLAY=:0



  reply	other threads:[~2004-01-20 21:30 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-01-19 16:12 John Allgood
2004-01-19 17:59 ` Patrick Macdonald
2004-01-19 19:17   ` John Allgood
2004-01-19 19:25     ` Patrick Macdonald
2004-01-19 20:17       ` John Allgood
2004-01-19 20:27         ` David Jee
2004-01-19 21:17           ` John Allgood
2004-01-19 21:28             ` David Jee
     [not found]               ` <400C4F35.7000307@turbocorp.com>
2004-01-20 14:54                 ` David Jee
2004-01-20 15:33                   ` John Allgood
2004-01-20 18:23                     ` David Jee
2004-01-20 18:45                       ` Fernando Nasser
2004-01-20 21:05                         ` John Allgood
2004-01-20 21:26                           ` Fernando Nasser
2004-01-20 21:30                             ` John Allgood [this message]
2004-01-20 21:53                               ` Kim Ho
2004-01-20 22:01                                 ` John Allgood

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=400D9DFE.8020803@turbocorp.com \
    --to=john@turbocorp.com \
    --cc=fnasser@redhat.com \
    --cc=rhdb@sources.redhat.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).