Howdy

I have solved this problem.

I commented out the nameserver line in /etc/resolv.conf and the GATEWAY line 
in /etc/sysconfig/network

Regards
Warwick Chapman
Managing Member
Thusa Business Support cc
Cell: +27 83 7797094
Fax: +27 31 2055838

-- There are 10 types of people in this world. Those
who understand binary, and those who don't.


Quoting Warwick Bruce Chapman <[EMAIL PROTECTED]>:

> Howdy
> 
> The reason we are using the PXELINUX boot method is because we don't want to
> 
> have to explicitly specify each client, as in K12LTSP (Which we find too 
> sluggish) and, lord forbid, Windows Terminal Services.
> 
> If they have auto generated host names, where can I find the defaults to add
> 
> them to a hosts file?
> 
> Warwick Chapman
> Managing Member
> Thusa Business Support cc
> Cell: +27 83 7797094
> Fax: +27 31 2055838
> 
> -- There are 10 types of people in this world. Those
> who understand binary, and those who don't.
> 
> 
> Quoting Jake Schroeder <[EMAIL PROTECTED]>:
> 
> > Okay, the workstations *never* "have no names".
> > 
> > They get an IP address from the DHCP server.  If you define their IP
> > addresses, then each one has a known IP address.
> > 
> > When their hostname is looked up (through either "reverse-DNS lookups"
> > or lts.conf), they have a name.
> > 
> > So, define all of your workstations in dhcpd.conf, lts.conf, and hosts.
> > 
> > For example (from Guides at http://akejay.freeshell.org/openbox.html):
> > 
> > #> Setting up a new Station:
> > #* Know: the MAC address of the station (like 00:10:23:46:12:35)
> >     the hostname you want to give the station (like obs001)
> >     the IP address you want to give the station (like 192.168.0.1)
> >     optionally, what kernel options you want to supply
> >     whether you want to create a guest account for the station
> >     whether you want autologin to happen when the station boots
> >             (and what username it should autologin with)
> > 1.  # echo __IP address__ __hostname__ >>/etc/hosts
> > 2.  #: Edit "/etc/dhcpd.conf":
> >     inside the "group" section, add these lines:
> > ---cut-->
> > host __hostname__ {
> >   hardware ethernet __MAC address__;
> >   fixed-address __hostname__;
> >   filename "/tftpboot/lts/vmlinuz-2.4.19-ltsp-1";
> > }
> > <--cut---
> >     if you want to supply any kernel commandline options,
> >             add these lines inside the new "host" section:
> > ---cut-->
> >   option option-128 e4:45:74:68:00:00;
> >   option option-129 "__kernel options__";
> > <--cut---
> > 3.  # invoke-rc.d dhcp restart
> > 4.  If you want to create a guest account for the Station:
> >     add the account "__hostname__":
> >             password: "__hostname__"
> >             full name: "OpenBox Station"
> > 5.  If you want an account to autologon when the station boots:
> >     Edit "/etc/kde2/kdm/kdmrc": add this to the end:
> > ---cut-->
> > [X-__hostname__:0-Core]
> > AutoLoginEnable=true
> > AutoLoginUser=__account name__
> > [X-__hostname__:0-Greeter]
> > DefaultUser=__hostname__
> > <--cut---
> > 6.  Run "echo [__hostname__] >>/opt/ltsp/i386/etc/lts.conf"
> > 7.  On the Station, run Etherboot and see if it starts up.  If not,
> >     get help from someone who knows LTSP (or TFTP/NFS/XDMCP/XFS).
> > 
> > Let us know how it goes!
> > - Jake
> > 
> > P.S.  Please critique me on the Guides, if you read them!
> > 
> > 
> > 
> > On Tue, Feb 25, 2003 at 07:59:07PM +0200, Warwick Bruce Chapman wrote:
> > > Howdy
> > > 
> > > How do I add workstations to the hosts file, when the stations have no
> > names.  
> > > I am using the PXELINUX boot method, and therefore the "Setting
> hostname"
> > line 
> > > during the workstation bootup doesn't have any name?
> > > 
> > > Warwick Chapman
> > > Managing Member
> > > Thusa Business Support cc
> > > Cell: +27 83 7797094
> > > Fax: +27 31 2055838
> > > 
> > > -- There are 10 types of people in this world. Those
> > > who understand binary, and those who don't.
> > > 
> > > 
> > > Quoting Matthew Johannes Winther <[EMAIL PROTECTED]>:
> > > 
> > > > Do you have the workstations in the hosts file? because it sounds like
> a
> > > > name resolving issue I had a while ago. And when I added the
> > workstations
> > > > to the hosts file, It was fixed.
> > > > 
> > > > Matthew Winther
> > > > 
> > > > On Tue, 25 Feb 2003, Ken Cobler wrote:
> > > > 
> > > > > Jake Schroeder wrote:
> > > > > 
> > > > > >Please help, o great NFS gurus!
> > > > > >
> > > > > >The client is just sitting there and mounting, mounting, mounting. 
> > It
> > > > > >seems that it tries about once every ten seconds.  Why would this
> > fail?
> > > > > >
> > > > > >
> > > > > >Sadly this has gone beyond my experience in troubleshooting NFS.  I
> > > > > >would investigate how to turn up debugging on the server to get
> more
> > > > > >descriptive errors about what is failing.  
> > > > > >
> > > > > >I wish you lots of luck though!  Let us all know how it goes.
> > > > > >- Jake
> > > > > >
> > > > > >
> > > > > >
> > > > > >On Tue, Feb 25, 2003 at 05:31:07PM +0200, Warwick Bruce Chapman
> > wrote:
> > > > > >  
> > > > > >
> > > > > >>Howdy
> > > > > >>
> > > > > >>When I say sleep, I mean it does nothing more/freezes/dies.
> > > > > >>
> > > > > >>/var/log/messages says:
> > > > > >>
> > > > > >>Feb 25 19:16:26 krakatoa rpc.mountd: authenticated mount request
> from
> > 
> > > > > >>192.168.0.150:688 for /opt/ltsp/i386 (/opt/ltsp/i386)
> > > > > >>Feb 25 19:17:06 krakatoa last message repeated 4 times
> > > > > >>Feb 25 19:18:16 krakatoa last message repeated 7 times 
> > > > > >>Feb 25 19:19:17 krakatoa last message repeated 6 times
> > > > > >>Feb 25 19:20:27 krakatoa last message repeated 7 times 
> > > > > >>    
> > > > > >>
> > > > > I had a similar problem and never received an answer.  I did
> determine
> > 
> > > > > this much.
> > > > > 
> > > > > My server (Redhat 8.0) has 2 ethernet cards with 10 LTSP
> workstations.
> > 
> > > > >  eth0 (10.0.0.X) was the LAN,  eth1 (192.168.1.X) was the Internet 
> > > > > connection through DSL.  Default routing (gateway) went through
> eth1.
> > > > > 
> > > > > If I turned off default routing, then the LTSP workstation NFS
> mounted
> > 
> > > > > quickly as expected.  However, without a default route, we could not
> 
> > > > > access the internet.
> > > > > 
> > > > > If I turned on default routing, we could access the Internet. 
> However,
> > 
> > > > > the NFS would start the described (see above) sleep like state during
> 
> > > > > LTSP boot.  The server would go from 95% idle to 20% idle.  After
> about
> > 
> > > > > 90 seconds, the LTSP workstation NFS mounted and the LTSP workstation
> 
> > > > > booted the rest of the way as expected.
> > > > > 
> > > > > It looked like to me, that the NFS replies were being sent down the 
> > > > > wrong ethernet connection (eth1).  After the server kernel timed
> out,
> > it 
> > > > > would switch to eth0 and LTSP workstation would get its reply and 
> > > > > complete NFS mounting.
> > > > > 
> > > > > For now, we don't turn off the LTSP workstations unless we absolutely
> 
> > > > > necessary.  When we do, we just expect the 90 second delay before
> LTSP
> > 
> > > > > booting.
> > > > > 
> > > > > Any insights would be greatly appreciated.
> > > > > 
> > > > > Ken Cobler
> > > > > 
> > > > > >>    
> > > > > >>
> > > > > 
> > > > > 
> > > > > 
> > > > > 
> > > > > -------------------------------------------------------
> > > > > This sf.net email is sponsored by:ThinkGeek
> > > > > Welcome to geek heaven.
> > > > > http://thinkgeek.com/sf
> > > > >
> _____________________________________________________________________
> > > > > 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
> > > > > 
> > > > 
> > > > 
> > > > 
> > > > -------------------------------------------------------
> > > > This sf.net email is sponsored by:ThinkGeek
> > > > Welcome to geek heaven.
> > > > http://thinkgeek.com/sf
> > > > _____________________________________________________________________
> > > > 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
> > > > 
> > 
> > -- 
> > 
> > 
> > -------------------------------------------------------
> > This sf.net email is sponsored by:ThinkGeek
> > Welcome to geek heaven.
> > http://thinkgeek.com/sf
> > _____________________________________________________________________
> > 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
> > 
> 
> 
> 
> -------------------------------------------------------
> This sf.net email is sponsored by:ThinkGeek
> Welcome to geek heaven.
> http://thinkgeek.com/sf
> _____________________________________________________________________
> 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
> 



-------------------------------------------------------
This SF.net email is sponsored by: Scholarships for Techies!
Can't afford IT training? All 2003 ictp students receive scholarships.
Get hands-on training in Microsoft, Cisco, Sun, Linux/UNIX, and more.
www.ictp.com/training/sourceforge.asp
_____________________________________________________________________
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