Bug 139255 - wb8 ch1 online exercise and $RPMS
Summary: wb8 ch1 online exercise and $RPMS
Keywords:
Status: CLOSED EOL
Alias: None
Product: Red Hat Academy
Classification: Retired
Component: RHA130 Curriculum
Version: 2.1
Hardware: All
OS: Linux
medium
medium
Target Milestone: ---
Assignee: Bowe Strickland
QA Contact: Bowe Strickland
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2004-11-14 14:52 UTC by Tomasz Chilinski
Modified: 2020-03-27 16:46 UTC (History)
0 users

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2020-03-27 16:46:56 UTC
Embargoed:


Attachments (Terms of Use)

Description Tomasz Chilinski 2004-11-14 14:52:22 UTC
From Bugzilla Helper:
User-Agent: Mozilla/5.0 (X11; U; Linux i686; pl-PL; rv:1.4.3)
Gecko/20040924

Description of problem:
1. Actually: RPMS="ftp://rha-server/pub/es3/RedHat/RPMS"
   should be: RPMS="ftp://rha-server/pub/es3/RedHat/RPMS/" because of
curl problem.
2. Student appends to his ~/.bash_profile following lines:
   
   RPMS="ftp://rha-server/pub/es3/RedHat/RPMS/"
   export RPMS

when /usr/share/rha/server/scripts/rha130-2.1/rpmrhn_rpmie.script is
executed as remote command (without interactive shell) .bash_profile
is not executed so RPMS environment value is not set! Thus there is no
chance to successful execution "curl $RPMS | grep redhat-release".
With interactive shell everything is ok.
Possible solution:
appending lines above to ~/.bashrc.


Version-Release number of selected component (if applicable):


How reproducible:
Always

Steps to Reproduce:
as above
    

Additional info:

Comment 1 Brad Smith 2005-01-01 23:12:25 UTC
Should be fixed in 2.2. The new text instructs the student to use
.bashrc (with the corrected url) and points out that while environment
variables are ususally set in .bash_profile, only .bashrc gets read
when commands are executed remotely via ssh, which is how the lab will
be graded. 

Comment 2 Bowe Strickland 2005-01-05 18:32:34 UTC
this'll stand for now, but i want to find a more graceful fix...


Note You need to log in before you can comment on or make changes to this bug.