On Tuesday 02 August 2005 05:44, [EMAIL PROTECTED] 
wrote:
> > In my previous email, I mentioned that your broadcast was wrong.
> >
> > It could be that you want that broadcast setting, in which case, you
> > need to change your netmask.
> >
> >
> > To sum it up, if you want a broadcast of 10.255.255.255, then you need
> > to change your netmask to 255.0.0.0
> >
> > If, on the other hand, you want your netmask to be 255.255.255.0, then
> > you need to change your broadcast to 10.2.2.255
> >
> > Does that make sense?  I hope so.  If you have any questions, just let
> > me know.
>
> Jim,
>
> It makes perfect sense. The broadcast address wasn't set explicitly:
> Debian set that for reasons beyond my understanding at the moment when
> nothing was set. The broadcast is now set to 10.2.2.255, and the problem
> remains. It should be noted that in addition to new terminals not
> getting NFS, old terminals are unable to open new applications and
> things slowly degrade to unusable. So this question relates to another
> one recently asked on this list
>
> eth0      Link encap:Ethernet  HWaddr 00:90:27:1B:2F:14
>           inet addr:10.2.2.254  Bcast:10.2.2.255  Mask:255.255.255.0
>           UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
>           RX packets:30035295 errors:2 dropped:0 overruns:0 frame:2
>           TX packets:31761182 errors:0 dropped:0 overruns:0 carrier:0
>           collisions:2305401 txqueuelen:1000
>           RX bytes:2740784130 (2.5 GiB)  TX bytes:3311432235 (3.0 GiB)
>           Interrupt:10 Base address:0xe000 Memory:dd221000-dd221038

Jeff the answer is complicated, and despite much trying I have not solved it.
By specifing files before dns in /etc/nsswitch.conf you would expect that this 
would be so. SOME network daemons do infact do so eg ssh does NOT

So with everything correct in /etc/hosts, no internet (no dns) we still get 
the delay (timeout) as the resolver tries to query the dns before quering the 
files. I can't change this behaviour. lTSP does it, as do all other machines.

It is not an LTSP issue per say, LTSP suffers as do all others.

James


-------------------------------------------------------
SF.Net email is sponsored by: Discover Easy Linux Migration Strategies
from IBM. Find simple to follow Roadmaps, straightforward articles,
informative Webcasts and more! Get everything you need to get up to
speed, fast. http://ads.osdn.com/?ad_idt77&alloc_id492&op=click
_____________________________________________________________________
Ltsp-discuss mailing list.   To un-subscribe, or change prefs, goto:
      https://lists.sourceforge.net/lists/listinfo/ltsp-discuss
For additional LTSP help,   try #ltsp channel on irc.freenode.net

Reply via email to