Once the /openils/bin directory was added to $PATH and the perl directory was added to the PERL5LIB, everything went swimmingly and I was able to use the staff client fine. I had no troubles becoming the opensrf user. I'm building it all from scratch again on VMWare and I'll report back if there are any other issues. Thanks, Dan - it looks like you've done a great job with the documentation. I've learned a lot from you.
Chris Sharp PINES System Administrator Georgia Public Library Service 1800 Century Place, Suite 150 Atlanta, GA 30345-4304 (404) 235-7147 [EMAIL PROTECTED] -----Original Message----- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Dan Scott Sent: Monday, June 30, 2008 1:20 PM To: Evergreen Discussion Group Subject: Re: [OPEN-ILS-GENERAL] Documentation Request Hi Chris: 2008/6/30 Sharp, Chris <[EMAIL PROTECTED]>: > Hello all, > > > > I've been working for a couple of months (on and off) with a virtual > installation of the Evergreen server. I've followed the "How to Install an > Evergreen Server on Debian" instructions several times, but could never get > it up and working until now, and this was with the VMWare image. The > problem was that when I started the EG server with the "osrf_ctl.sh" script, > the command wasn't recognized. This was solved by putting the /openils/bin > directory in my $PATH variable (which has been addressed on this list > before) and putting the /openils/lib/perl5 directory in the PERL5LIB > environment variable. I think adding these steps (which would be obvious > to more seasoned Unix users) to the main installation instructions would be > a big help! Everything worked very well once I got that sorted out! Interesting - that's what step 19 is for (setting these variables in .bashrc) - but it is possible if your opensrf user's shell isn't bash to not get these variables set, and to run into trouble as a result. I'm especially interested on the VMWare image, which should work out of the box - how were you becoming the opensrf user? To help out in those situations where things might have gone wrong, I'll add a debug step right after step 2 of the "starting evergreen" section that tells you what to do if you receive an error about command not found or Perl library not found. Thanks for the feedback! -- Dan Scott Laurentian University
