Description of problem:

The old condor problem: the documentation does not specify
in what units STARTER_RLIMIT_AS is to be expressed. 

In this case it looks like Terabytes; highly unlikely I think... 

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

condor-7.9.1-0.1.fc17.2.

How reproducible:

Always

Steps to Reproduce:
1. Put STARTER_RLIMIT_AS = 1 in the config file
2. Run a job
3. Grep through the StarterLog
   > grep virtual StarterLog
   > StarterLog.slot1_1:10/03/12 09:51:48 Setting job's virtual memory rlimit to 1048576 megabytes
  
Actual results:

> StarterLog.slot1_1:10/03/12 09:51:48 Setting job's virtual memory rlimit to 1048576 megabytes  

Expected results:

Some consistent scheme for addressing amounts of memory all over condor.
Like: all amounts are bytes, unless tagged with k, M, G of T.

Additional info:

When you specify 0, it reports 
  'Setting job's virtual memory rlimit to 0 megabytes'
but that is obviously not true, as that would prevent any job from starting.

Probably '0' means, 'leave it alone', but it should be reported as such then.