JBoss: Windows vs Linux and a Solaris boot issue

[Stuart Jansen]

On Wed, 2006-03-08 at 11:25 -0700, Bryan Sant wrote:
> Windows will use it's internal name resolution mechanism to lookup a
> name.  That is local name cache, lmhosts, hosts, WINS server, name
> server, and NetBIOS broadcast.  Linux will look at hosts, and then dns
> (and may do more depending on what's configured in
> /etc/nsswitch.conf).  If you have samba installed on your Linux
> machine you can add "wins" to the end of your "hosts:" line in
> /etc/nsswitch.conf and Linux will now do NetBIOS broadcast lookups for
> a Windows computer "name" just like Windows does.  The better solution
> though is to do what Shane suggested and make sure that all of the
> systems you reference by name are in the /etc/hosts file (your MSSQL
> 2000 server for example).  Name resolution delay may indeed be the
> problem.  What does your JDBC connect URL look like?

Putting hostnames in /etc/hosts will indeed be fastest. An easier to
manage solution would be to install a caching name server.

-- 
Stuart Jansen              e-mail/jabber: sjansen at buscaluz.org
                           google talk:   stuart.jansen at gmail.com
:0                         # copy & paste for your convenience
* ^From:.*sjansen@
/dev/null                  # /ignore sjansen!*@*
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 191 bytes
Desc: This is a digitally signed message part
Url : http://plug.org/pipermail/plug/attachments/20060308/17673b60/attachment.bin