From: James Beale <jamesb@ludcastle.co.uk>
To: "'rhdb@sources.redhat.com'" <rhdb@sources.redhat.com>
Subject: rhdb-explain, rhdb-admin, rhdb-cc "Unable to find a java executab le" - FOR INFORMATION ONLY, NO NEED FOR REPLIES
Date: Thu, 25 Mar 2004 17:24:00 -0000 [thread overview]
Message-ID: <02FA758810D1D711943E0003470A8B918F1C@LCCNTSERVER1> (raw)
With my sincere thanks to Fernando Nasser and Kim Ho, without whom I'd be
floundering still, I post here the information I used to get things running
when I got errors "Unable to find a java executable" error running
rhdb-explain, rhdb-admin, and rhdb-admin.
No reply is needed, this is just for information for anyone else looking for
this information whilst searching the archives.
Note that this solution was deployed on RH9 using Sun Java j2re1.4.2. If
you use a different Java this will probably not work. Each Java places
things in different places.
I hope this is of use to someone else, and, again, thanks Fernando and Kim.
Extract:
James Beale wrote:
> Hi again
>
> Thanks very much for the pointers. I've added all the info thus:
>
> 1 - Edit /<userhomedirectory>/.bash_profile, and ensure it reads:
> JAVA_HOME=/usr/java/j2re1.4.2_04
> PATH=$JAVA_HOME/bin:$PATH:$HOME/bin
> BASH_ENV=$HOME/.bashrc
> USERNAME="root"
> export USERNAME BASH_ENV PATH
> CLASSPATH=/usr/share/java/rh-postgresql3.jar
> export CLASSPATH
>
> 2 - Edit the file /usr/share/rhdb-cc/rhdb-cc.sh file, adding the line if
> needed.
> JAVA_HOME=/usr/java/j2re1.4.2_04
>
==============================================
James M Beale MBCS CITP
Lud Castle (Computing) Ltd
Tel: +44 (0)1382 736031
Fax: +44 (0)8700 518 232
mailto:jamesb@ludcastle.co.uk
http://www.ludcastle.demon.co.uk
reply other threads:[~2004-03-25 17:24 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=02FA758810D1D711943E0003470A8B918F1C@LCCNTSERVER1 \
--to=jamesb@ludcastle.co.uk \
--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).