On Wed, 2012-11-28 at 10:43 -0500, Michael J. Hammel wrote:
> On Wed, 2012-11-28 at 01:47 -0500, Eric Charles wrote:
> > Hi,
> > It seems that localhost is resolved to 64.95.64.218.
> > Is this correct? Can you try connection to -h 127.0.0.1?
> 
> Well, it seems that way if I run james-cli.sh.  But I can ping localhost
> and get back the loopback IP address.  So I'm not sure why James is
> routing to that address.
> 
> I can't find the cause, so I'm punting: reinstall the OS and reinstall
> James from the tarball (none of my changes applied).  If it still does
> it, then its likely an incompatibility with the 32bit version of F16.
> Something tells me this will work and that my previous installs were
> just fubar.

For completeness sake: 

A reinstall of the OS and loading James manually and testing at each
point along the way worked.  James is running fine on my F16 i686 laptop
now. 

I have no idea what was wrong before.  But at least whatever it was,
it's fixed.

-- 
Michael J. Hammel
[email protected]

Exports of information/data contained herein may be subject to the
export laws of the United States including, but not limited to, the US
International Traffic in Arms Regulations (ITAR) and may require advance
authorization from the U.S. Government.  The parties shall not export,
disclose or transfer any such data directly or indirectly without
compliance with this or any other applicable laws and regulations.

CONFIDENTIALITY NOTICE: This e-mail message, including any  
attachments, is for the sole use of the intended recipient(s) and  
contains information that is confidential and proprietary to Colorado  
Engineering Incorporated. It is to be used solely for the purpose of  
furthering the parties' business relationship. All unauthorized  
review, use, disclosure or distribution is prohibited. If you are not  
the intended recipient, please contact the sender by reply e-mail and  
destroy all copies of the original message.


---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to