I just used the YAST2 Online update tool to install the latest patches on
our instances running WAS.  After the install I discovered Websphere
wouldn't start.  

After some newsgroup searching I found that the problem was due to the fact
that localhost resolved to 127.0.0.1 instead of the "external" ip of the
instance.   I edited the /etc/hosts file to fix this and websphere then
started.

Problem is that everytime SuSEconfig is ran my changes to the /etc/hosts
file are lost.  Anyone have any ideas on what I can do to keep this problem
from happening.


Josh Konkol, CNE MCSE
Technical Research Specialist
 .~.    GuideOne Insurance
 /V\    
/( )\   
^^-^^   [EMAIL PROTECTED]


   
This message and accompanying documents are covered by the Electronic
Communications Privacy Act, 18 U.S.C. �� 2510-2521, and contains information
intended for the specified individual(s) only. This information is
confidential. If you are not the intended recipient or an agent responsible
for delivering it to the intended recipient, you are hereby notified that
you have received this document in error and that any review, dissemination,
copying, or the taking of any action based on the contents of this
information is strictly prohibited. If you have received this communication
in error, please notify us immediately by e-mail, and delete the original
message.

Reply via email to