HI All,
I have configured LTSP fatclient on one of my server and clients are able
to boot also. When the users are sending mail from evolution it is not
storing mails in sent showing some errors with respect to Lock.
I have read somewhere if we use NFS home we wont face the problem so i
tried
15.02.2012 15:44, Aravind M D kirjoitti:
I have read somewhere if we use NFS home we wont face the problem so i
tried using home directory mounted as nfs.
In /opt/ltsp/i386/etc/lts.conf
[default]
NFS_HOME=/home
Not sure what you have done, because there is no need for manually
mounting
Hi, I have tree servers with LTSP5 and Ubuntu Desktop 8.4, I use NFS, no NBD. I
have to migrate to Ubuntu 10.4. I am probing LTSP5 and Ubuntu 10.4 in a virtual
machine. But I can not change of NBD to NFS. I use a old guide but the file
/opt/ltsp/i386/etc/default/ltsp-client-setup do not exist
Hi All,
I'm implementing an Ubuntu LTSP system with 10 thin client.
Perhaps I need Samba for some Windows clients in the network.
Is it better to use NFS or Samba with LTSP?
Giacomo.
--
Throughout its 18-year history,
On Wed, Jan 20, 2010 at 4:38 AM, Giacomo Trovato
giacomo.trov...@gmail.com wrote:
Hi All,
I'm implementing an Ubuntu LTSP system with 10 thin client.
Perhaps I need Samba for some Windows clients in the network.
Is it better to use NFS or Samba with LTSP?
I don't think it's any different
Giacomo,
On Wed, Jan 20, 2010 at 9:38 AM, Giacomo Trovato
giacomo.trov...@gmail.com wrote:
I'm implementing an Ubuntu LTSP system with 10 thin client. Perhaps I
need Samba for some Windows clients in the network. Is it better to
use NFS or Samba with LTSP?
It all depends on what you need.
Thanks.
But *SERVER* crash with high activite on HD (2 CABLED HD With PERC 6i in RAID 1)
2009/8/19 Xavier Brochard xav...@alternatif.org:
Le mercredi 19 août 2009 18:38:08, Osvaldo Filho a écrit :
Sorry!
- Ubuntu 9.04 Amd64 with i386 clients
- DELL PE T410 with 6Gb
- Switch Base Line 3Com
Le mardi 18 août 2009 22:08:18, Osvaldo Filho a écrit :
How can i totaly disable NFS ?
how can we understand your question if you don't provide any useful
informations ? ;-)
please give us
- the system (and version) you are running on
- the reason you doesn't want NFS
- the ltsp manual
Sorry!
- Ubuntu 9.04 Amd64 with i386 clients
- DELL PE T410 with 6Gb
- Switch Base Line 3Com 24 + 2 (1000)
- Slow Firefox - very slow javascript and others on firefox (right
click menus on google search links, for example)
- Server crash with 15 actives terminals with 3 on youtube.com
A friend
Le mercredi 19 août 2009 18:38:08, Osvaldo Filho a écrit :
Sorry!
- Ubuntu 9.04 Amd64 with i386 clients
- DELL PE T410 with 6Gb
- Switch Base Line 3Com 24 + 2 (1000)
- Slow Firefox - very slow javascript and others on firefox (right
click menus on google search links, for example)
There
How can i totaly disable NFS ?
--
Let Crystal Reports handle the reporting - Free Crystal Reports 2008 30-Day
trial. Simplify your report design, integration and deployment - and focus on
what you do best, core
Every time I reset my authentication server (which isn't often), all
my LTSP servers stop allowing clients to boot. The error message says
that /opt/ltsp/i386 cannot be mounted and gives a permission denied.
Any clients that were already booted can be used. Only clients that
reboot get denied. I
David Hopkins wrote:
I have searched unsuccessfully for an answer on exactly what services
need to be restarted to allow clients to boot. Note that my
authentication server is not the same system as the LTSP server and
that the authentication is using ldap.
A wild guess: You use LDAP for
On Mon, Sep 8, 2008 at 9:36 AM, Horst Prote [EMAIL PROTECTED] wrote:
David Hopkins wrote:
I have searched unsuccessfully for an answer on exactly what services
need to be restarted to allow clients to boot. Note that my
authentication server is not the same system as the LTSP server and
Hi all,
I'm trying to install LTSP5 (using ubuntu_feisty tarball) in FC8, but when I
boot my client, there is a message : NFS over TCP not available from ... and
then my client just halt.
What could possibly go wrong?
best regards,
sigit
Hi all,
I'm trying to install LTSP5 (using ubuntu_feisty tarball) in FC8, but when I
boot my client, there is a message : NFS over TCP not available from ... and
then my client just halt.
What could possibly go wrong?
best regards,
sigit
On 19 Feb at 23:03 jam [EMAIL PROTECTED] wrote in message
[EMAIL PROTECTED]
On Wednesday 20 February 2008 03:52:51
[EMAIL PROTECTED] wrote:
LTSP-5 under Debian Etch:
I thought it would be a clever idea to upgrade inetd to xinetd, and in
general that was successful. This may be a red
LTSP-5 under Debian Etch:
I thought it would be a clever idea to upgrade inetd to xinetd, and in
general that was successful. This may be a red herring.
However, my LTSP terminals are now failing to start.
The kernal loads OK, and it gets to (copied by hand):
Begin: Running
On Wednesday 20 February 2008 03:52:51
[EMAIL PROTECTED] wrote:
LTSP-5 under Debian Etch:
I thought it would be a clever idea to upgrade inetd to xinetd, and in
general that was successful. This may be a red herring.
However, my LTSP terminals are now failing to start.
I use xinet on
On Mon, 11 Feb 2008 15:23:40 -0700
Craig White [EMAIL PROTECTED] wrote:
a full explanation is on the wiki
http://wiki.ltsp.org/twiki/bin/view/Ltsp/Troubleshooting-mount-problems
Interesting. I am confused about this part:
QUOTE
If you have access to the client's /linuxrc file then you can
On Mon, 11 Feb 2008 14:32:55 -0800
Derek McKay [EMAIL PROTECTED] wrote:
This sounds like it could be the old UDP fragmentation problem showing
up again.
Now that's highly interesting and something I've never heard about before.
Is this a common problem with any particular kind or brand of
On Mon, 11 Feb 2008 14:22:24 -0700
Craig White [EMAIL PROTECTED] wrote:
Can you disable the
fancy stuff and tell it to just be a switch?
I am uncomfortable with that type of advice.
It seems the Macintosh computers struggle with spanning-tree protocol
and by switching it off on the
On Mon, 2008-02-11 at 15:18 -0600, Frank Cox wrote:
On Mon, 11 Feb 2008 13:09:32 -0800
Jim Kusznir [EMAIL PROTECTED] wrote:
Any suggestions? I have no idea what to start tweaking on the netgear...
I know nothing at all about a Netgear GSM7224 managed gigabit switch, but it
sounds like
Hi all:
I have a very strange problem. I have a working LTSP 4.2 setup. Our
network infrastructure is built around HP Procurve switches. We have
our primary LTSP server in our machine room, and thin clients in two
buildings throughout the building. All this works fine.
Then, one of our labs
On Mon, 2008-02-11 at 16:35 -0600, Frank Cox wrote:
On Mon, 11 Feb 2008 15:23:40 -0700
Craig White [EMAIL PROTECTED] wrote:
a full explanation is on the wiki
http://wiki.ltsp.org/twiki/bin/view/Ltsp/Troubleshooting-mount-problems
Interesting. I am confused about this part:
QUOTE
On Mon, 2008-02-11 at 16:15 -0600, Frank Cox wrote:
On Mon, 11 Feb 2008 14:32:55 -0800
Derek McKay [EMAIL PROTECTED] wrote:
This sounds like it could be the old UDP fragmentation problem showing
up again.
Now that's highly interesting and something I've never heard about before.
Is
On Mon, 11 Feb 2008 13:09:32 -0800
Jim Kusznir [EMAIL PROTECTED] wrote:
Any suggestions? I have no idea what to start tweaking on the netgear...
I know nothing at all about a Netgear GSM7224 managed gigabit switch, but it
sounds like something is not being passed through that switch, which
This sounds like it could be the old UDP fragmentation problem showing
up again. Some switches are much better than others at handling big UDP
packets that have to be fragmented to 1500 byte ethernet packets. Used
to be a big problem with 100/10 switches/hubs where the switch storage
would drop
On Mon, 2008-02-11 at 15:48 -0700, Craig White wrote:
On Mon, 2008-02-11 at 16:35 -0600, Frank Cox wrote:
On Mon, 11 Feb 2008 15:23:40 -0700
Craig White [EMAIL PROTECTED] wrote:
a full explanation is on the wiki
Hi,
I had to replace my mainboard in my LTSP server. (same model and rev.)
After correcting the udev rules to have the network working again, I
got the mentioned massage when booting a client(the message is repeated
every 2-4 seconds). If I restart the nfs-kernel-server on the server
Hi there.
ltsp5 etch /opt/ltsp i386
I take words from Scott to my heart (install it in /opt/ltsp) and I
got myself to need a path.
(I got there before with non-default instal, too, but ... I have a few
patches in my head, after few days u will have them here, too :)
Yes, u can bet, that
On Tue, May 29, 2007 at 05:03:21PM +0200, Jan Kunder wrote:
Hi there.
ltsp5 etch /opt/ltsp i386
I take words from Scott to my heart (install it in /opt/ltsp) and I
got myself to need a path.
(I got there before with non-default instal, too, but ... I have a few
patches in my head, after
On 5/29/07, Scott Balneaves [EMAIL PROTECTED] wrote:
On Tue, May 29, 2007 at 05:03:21PM +0200, Jan Kunder wrote:
Hi there.
ltsp5 etch /opt/ltsp i386
I take words from Scott to my heart (install it in /opt/ltsp) and I
got myself to need a path.
(I got there before with non-default
Scott Balneaves wrote:
On Tue, May 29, 2007 at 05:03:21PM +0200, Jan Kunder wrote:
Hi there.
ltsp5 etch /opt/ltsp i386
I take words from Scott to my heart (install it in /opt/ltsp) and I
got myself to need a path.
(I got there before with non-default instal, too, but ... I have a few
On 5/29/07, Jim McQuillan [EMAIL PROTECTED] wrote:
Scott Balneaves wrote:
On Tue, May 29, 2007 at 05:03:21PM +0200, Jan Kunder wrote:
Hi there.
Actually, the fact that LTSP-5 doesn't use the IP address in the
root-path is a bug, and it's being fixed. LTSP-4.2 could also figure
out the
I am upgrading from ltsp4.2 to ltsp5 my debian system.
I find this error in mounting nfs on clients:
...
Begin: Mounting root file system
Begin: Running /scripts/nfs-top
Done.
IP-Config:
...
Begin: Running /scripts/nfs-premount ...
Done.
nfsmount: need a path
Done.
Begin: Retrying nfs mount
David,
Edit your dhcpd.conf file, and take the IP address out of your root-path
statement.
LTSP-5 doesn't yet support that style of root-path.
In the end, your root-path should look like:
option root-path /opt/ltsp/i386;
Jim McQuillan
[EMAIL PROTECTED]
[EMAIL PROTECTED] wrote:
I
Hello all,
when I boot the fresh installed ltsp4.2 I get the message:
nfs server: 192.168.55.200 not responding
nfs server: 192.168.55.200 ok
nfs server: 192.168.55.200 not responding
nfs server: 192.168.55.200 ok
This is from the server log:
Apr 1 12:51:08 akazia mountd[4005]: authenticated
M Hoeller wrote:
Hello all,
when I boot the fresh installed ltsp4.2 I get the message:
nfs server: 192.168.55.200 not responding
nfs server: 192.168.55.200 ok
nfs server: 192.168.55.200 not responding
nfs server: 192.168.55.200 ok
This is from the server log:
Apr 1 12:51:08 akazia
I have what may look like a timeout problem as I just put in a new
switch to serve my LTSP client segment:
Old: CNET 100 Mbit switch
New: D-Link Gigabit switch.
Result: The client stopped booting when trying to set up the NFS share.
On the server system daemon log, I can see that the connection
I need to setup a couple of LTSP servers to support the number of users.
I decided to setup a nfs server so that certain directories remain the
same on all ltsp servers.
I am thinking 1 master server and 1+ slave server.
I am thinking of moving
/home
/opt/ltsp
/var/lib/tftpboot to the nfs server.
Halp!i have the original bill_c kernel and chroot which works fine from an
i386 server..loading the new ltsp5 ppc kernel from same server ,nfs craps
out and wont nfsmount,either chroot.
the old kernel will mount either chroot..but obviously doesnt finish up
with the new /opt/ltsp/powerpc croot
Hello,
It's been a long time since I've posted to this group. I want to thank
you for all the work
that you have done.
Here is the background information. We have been using LTSP for several
years. We run DHCP
and TFTP on Windows 2003 servers. We were using a Linux server (Suse
Hi Abraham,
On Thu, 21 Dec 2006, Abraham Pearson wrote:
Any help or suggestions would be greatly appreciated.
Have you sniffed the network traffic to see what it is? Wireshark
(formerly Ethereal) is a great tool for such an investigation.
Jason
Mandag 27 november 2006 20:12 skrev Verner Kjærsgaard:
Mandag 27 november 2006 19:33 skrev John P. New:
Verner,
This is a problem with NFS and 2.6 kernels, fast server NICs and
comparatively slower client NICs. This will show up when the server has
a 1000Mb card and the client a 100Mb,
Hi List,
A couple of times I've run into this problem...
The server is connected to a modern fancy switch using 1000Mbit. This switch
now connects to other switches, all 100Mbit.
When booting the clients, I get...
NFS Server Not Responding, still trying...
NFS Server Not Responding, still
Verner Kjærsgaard a écrit :
Hi List,
A couple of times I've run into this problem... The server is
connected to a modern fancy switch using 1000Mbit. This switch now
connects to other switches, all 100Mbit.
When booting the clients, I get...
NFS Server Not Responding, still trying...
Verner,
This is a problem with NFS and 2.6 kernels, fast server NICs and
comparatively slower client NICs. This will show up when the server has
a 1000Mb card and the client a 100Mb, or when the server has a 100Mb
card and the client a 10Mb.
Essentially, you have to pass some options to the
Mandag 27 november 2006 19:33 skrev John P. New:
Verner,
This is a problem with NFS and 2.6 kernels, fast server NICs and
comparatively slower client NICs. This will show up when the server has
a 1000Mb card and the client a 100Mb, or when the server has a 100Mb
card and the client a 10Mb.
Hi,
LTSP 4.2, Debian Stable/Testing
/etc/exports has entries to export /opt/ltsp and the swap file, for
172.28.30.*/255.255.255.0
/etc/hosts.allow also allows things to 172.28.
server ip address is 172.28.30.254
All machines are using the same isolated hub (no other network traffic),
dhcp
Lauro,
Try running this command:
showmount -e
That should show exactly what nfs is exporting.
If it doesn't agree with what's in /etc/exports, then it probably means
you've updated /etc/exports, but didn't run 'exportfs -ra' to update the
kernel tables.
Jim McQuillan
[EMAIL PROTECTED]
System Debian Testing. LTSP 4.2u3 kernel bzImage-2.6.17.8-ltsp-1
thin client IBM Think Pad A30
I am trying to boot using an Asus 330g bridge.
the waring I receive
nfs: server 192.168.0.100 not responding, still trying
means the nfs is timing out due to large packet size.
I created a custom
On Fri, September 1, 2006 9:55 am, J. Paul Bissonnette wrote:
System Debian Testing. LTSP 4.2u3 kernel bzImage-2.6.17.8-ltsp-1
thin client IBM Think Pad A30
I am trying to boot using an Asus 330g bridge.
the waring I receive
nfs: server 192.168.0.100 not responding, still trying
means the
Hi
I have the dreaded NFS timeouts with my systems [server a PCI rtl8139, client
an intel e1000 on crosover cable]
OK the wiki needs some work. I'll do it if I can get this to run
hello!
using ltsp4.1.
on Terminal A, i get this:
NFS warning version older than kernel
snip
Are you sure the NFS/Swap patch has been applied to the workstation kernel?
It says press Enter to continue, i pressed continue, and then it went
on fine.
on Terminal B, i also get this:
NFS
Joey,
the 2.6.9 kernel in ltsp-4.1 has lots of problems.
Also, the 2.6 kernel has NO support for NFS-Swap. That's a 2.4 thing only.
I highly recommend moving up to LTSP-4.2, where we have a 2.6.16 kernel
and if you need network swapping, we have NBD_Swap.
Jim McQuillan
[EMAIL PROTECTED]
Thanks Jim,
Will do that.
Thanks!
Jim McQuillan wrote:
Joey,
the 2.6.9 kernel in ltsp-4.1 has lots of problems.
Also, the 2.6 kernel has NO support for NFS-Swap. That's a 2.4 thing
only.
I highly recommend moving up to LTSP-4.2, where we have a 2.6.16
kernel and if you need network
I don't have a physical box to put in the subnet right now.
This is for a school where we have 3 subnets: staff, students, and
servers. We have a router in place that limits access to certain ports
and IP addresses in the server subnet and the internet. Mainly to keep
the students from doing
I'm trying to work out some NFS issues at boot time. I'm getting the
still trying error message and it just hangs...
I'm working through this page on the wiki:
*http://wiki.ltsp.org/twiki/bin/view/Ltsp/Troubleshooting-mount-problems*
Quick hardware fixes aren't going to happen. I don't have
Casey,
You don't need to access the /linuxrc script to modify the mount parameters.
Take a look at this wiki page:
http://wiki.ltsp.org/twiki/bin/view/Ltsp/NFS#NFS_Server_not_responding
Basically, you can pass any nfs options you want, via the 'MOPTS' parameter.
Jim McQuillan
[EMAIL
On Tue, May 16, 2006 at 11:22:56AM -0600, Casey Woods wrote:
snip
I'm not doing any filtering that should affect anything. It's just
doing IP forwarding between subnets.
Doing any UDP forwarding? NFS uses UDP for it's work. That's probably
the root of your problem.
How are you handling
On 5/16/06, Scott Balneaves [EMAIL PROTECTED] wrote:
On Tue, May 16, 2006 at 11:22:56AM -0600, Casey Woods wrote:
snip
I'm not doing any filtering that should affect anything. It's just
doing IP forwarding between subnets.
Doing any UDP forwarding? NFS uses UDP for it's work. That's
I'm using a DHCP relay agent on the FreeBSD router. You don't need to
have a DHCP server in the same subnet as the thin clients if you're
relaying the DHCP requests to a DHCP server in another subnet. DHCP
wasn't the issue at all since I could get an IP and boot up via TPFT.
It was getting
Always that I add some machine with NIC of 10Mhz or hub of 10Mhz my
server NFS falls, what can be happening?
---
This SF.Net email is sponsored by xPML, a groundbreaking scripting language
that extends applications into web and mobile media.
On Fri, April 14, 2006 9:40 am, Josafá Orrico wrote:
Always that I add some machine with NIC of 10Mhz or hub of 10Mhz my
server NFS falls, what can be happening?
You need to take a look at:
http://wiki.ltsp.org/twiki/bin/view/Ltsp/NFS#NFS_Server_not_responding
Jim McQuillan
[EMAIL
Jacky,
Take a look at the following wiki article:
http://wiki.ltsp.org/twiki/bin/view/Ltsp/NFS#NFS_Server_not_responding
That should explain what the problem is, and how to fix it.
Jim McQuillan
[EMAIL PROTECTED]
Jacky Li wrote:
Hi,
In a 100 Mbit network environment, I have no problem
hello!
i use etherboot so i should be working with MOPTS (what does this stand
for? more options) on /etc/dhcpd.conf right?
im actually considering it might be a network problem, but having tried
to replace cables, and nics, still get the same problem, maybe i should
look first in the
Hi Joey
nfs: server server not responding, still trying
nfs: server OK
I had the same problem on one of the machines on my network
and I solved it by changing the network cable.
Nico
On Mon, 20 Mar 2006 16:24:32 +0800
Joey S. Eisma [EMAIL PROTECTED] wrote:
hi!
server is running mandrake
Hi!
Would MOPTS recognize adding more options like timeo?
Some terminal experience sudden freeze, I have already enabled NFS
swapping, tried increase/decrease wsize/rsize, now nfs over tcp. But I
still have the same problem.
Thanks!
Jim McQuillan wrote:
Chris,
to do NFS over tcp, you'd
I'm no expert but playing with the MOPTS in
/tftpboot/lts/2.4.26-ltsp-3/pxelinux.cfg/default
will modify the way the terminal's root filesystem is mounted
to modify the swap mount options, look here
/opt/ltsp/i386/etc/rc.sysinit
Some terminal experience sudden freeze, I have already enabled NFS
Hi all,
I'd like to mount the terminal root filesystem using tcp (instead of udp).
I've tried editing
/tftpboot/lts/2.4.26-ltsp-3/pxelinux.cfg/default to add proto=tcp but
that doesn't seem to work.
How is this done?
I'd also like to mount the nfs-swaps via tcp too.
Has anyone done that?
hi!
server is running mandrake 10.1.
terminal has 64MB RAM,
dhcpd has this:
option option-128 e4:45:74:68:00:00;
option option-129 MOPTS=nolock,ro,rsize=4096,wsize=4096;
NFS swapping is enabled,
some terminals keep on freezing, i tried to put in SCREEN_01 = shell to
see what's going on
Chris,
to do NFS over tcp, you'd need to set the option like this:
MOPTS=nolock,ro,wsize=8192,rsize=8192,proto=tcp
The linuxrc script is looking for the 'MOPTS' variable to pass to the
mount command. You need to also pass the other options, because with
MOPTS, it's all or nothing. That
hello,
I am getting the NFS mount problem with HP-vetra p200 machines,
the process gets very slow while mounting NFs file it just stops at
doing pivot root.
I passed the parameters metinoned by Jim in ealier mails , but the issue
remains same.
How to check whether the PCI solt is proper or not ?
I'm trying to use LTSP 4.1 on Suse 9.3 x86_64. The root mount is
failing :
mounting root filesystem: /opt/ltsp/i386 from 172.30.4.74
mount: RPC: Timed out
mount: nfsmount failed: Bad file descriptor
nfs warning: mount version older than kernel
NFS: mount program didn't pass remote address!
On Thu, Jul 28, 2005 at 10:13:41PM -0400, Jim McQuillan wrote:
Jeff,
Do you have the workstations listed in the /etc/hosts file on the
server?
Also, on the server, can you do this:
ifconfig -a
and send us the output, so we can see how your network is configured.
eth0 Link
Jeff,
First thing I notice is that your broadcast (Bcast) isn't correct for
your chosen Netmask (Mask).
For a netmask of 255.255.255.0, your broadcast should be 10.2.2.255
I can't say for sure that it would cause your problems, but if eth0 is
the thin-client network, then NFS could certainly
Jeff,
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
On Mon, Aug 01, 2005 at 03:07:29PM -0400, Jim McQuillan wrote:
Jeff,
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
jeff,
Ok, the next thing to do is use tcpdump to watch the traffic that is
trying to go out through that interface.
if the external interfaced is eth1, then try this:
tcpdump -i eth1
Then sit back and watch, to see what traffic is trying to use the
interace.
That is, assuming you've pulled
On Mon, Aug 01, 2005 at 04:33:11PM -0400, Jim McQuillan wrote:
jeff,
Ok, the next thing to do is use tcpdump to watch the traffic that is
trying to go out through that interface.
if the external interfaced is eth1, then try this:
tcpdump -i eth1
Then sit back and watch, to see
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
Hi all,
I've got a trio of LTSP servers that all behave the same way. They're
happy to work if the internet is plugged in, but if you unplug it, they
fail to get NFS to their own internal terminal network, which is still
perfectly well plugged.
So here's the setup: Debian + LTSP
Jeff,
Do you have the workstations listed in the /etc/hosts file on the
server?
Also, on the server, can you do this:
ifconfig -a
and send us the output, so we can see how your network is configured.
Thanks,
Jim McQuillan
[EMAIL PROTECTED]
On Thu, 28 Jul 2005 [EMAIL PROTECTED] wrote:
On Thu, Jul 28, 2005 at 10:13:41PM -0400, Jim McQuillan wrote:
Jeff,
Do you have the workstations listed in the /etc/hosts file on the
server?
Also, on the server, can you do this:
ifconfig -a
and send us the output, so we can see how your network is configured.
Thanks,
Jim
Hi Jim and list,
- I read the wiki about the rsize=8192,wsize=8192 trick in the dhcpd.conf
file. It works fine.
- However, I seem to remember that I once put that parm into something
like /opt/ltsp/i386/etc/rc.sysinit (??), can that be true?
- And, would it not work the same way putting the
At 00:48 04/07/2005 -0400, Claude Gélinas agr. wrote:
Le dimanche 03 juillet 2005 à 23:22 -0400, Jim McQuillan a écrit :
Did you take a look at the wiki article on NFS?
http://wiki.ltsp.org/twiki/bin/view/Ltsp/NFS
Yes I've tried that but it didn't work. As I still have no luck with the
2.6
Le lundi 04 juillet 2005 à 13:11 +0700, Harry Sufehmi a écrit :
At 00:48 04/07/2005 -0400, Claude Gélinas agr. wrote:
Le dimanche 03 juillet 2005 à 23:22 -0400, Jim McQuillan a écrit :
Did you take a look at the wiki article on NFS?
http://wiki.ltsp.org/twiki/bin/view/Ltsp/NFS
Yes
when booting the terminal I get the following messages
nfs: server 192.168.1.7 not responding still trying
nfs: server 192.168.1.7 OK
nfs: server 192.168.1.7 not responding still trying
I know it's an NFS time out from the 2.6 kernel using a large default
blocksize of 32k for NFS packets. to
Claude,
Did you take a look at the wiki article on NFS?
http://wiki.ltsp.org/twiki/bin/view/Ltsp/NFS
Near the end, it shows that you need to add:
MOPTS=nolock,ro,wsize=2048,rsize=2048
to your kernel cmdline. That would be the 'append' line in your
pxelinux.cfg/default file.
Jim
Le dimanche 03 juillet 2005 à 23:22 -0400, Jim McQuillan a écrit :
Claude,
Did you take a look at the wiki article on NFS?
http://wiki.ltsp.org/twiki/bin/view/Ltsp/NFS
Near the end, it shows that you need to add:
MOPTS=nolock,ro,wsize=2048,rsize=2048
to your kernel cmdline.
At 13:53 14/06/2005 +0800, seekuel _lycos.com wrote:
sir I was setting up LTSP 4.1.0 using Mandrake 10.0 our workstaions are
all identical, evrything wroks fine exept for 1 workstation which was the
bios was updated to newer version. This are the last few lines the
workstation displays:
On 6/14/05, Harry Sufehmi [EMAIL PROTECTED] wrote:
At 13:53 14/06/2005 +0800, seekuel _lycos.com wrote:
sir I was setting up LTSP 4.1.0 using Mandrake 10.0 our workstaions are
all identical, evrything wroks fine exept for 1 workstation which was the
bios was updated to newer version. This are
Am Dienstag, den 14.06.2005, 13:53 +0800 schrieb seekuel _lycos.com:
Greetings!!!
sir I was setting up LTSP 4.1.0 using Mandrake 10.0 our workstaions are all
identical, evrything wroks fine exept for 1 workstation which was the bios
was updated to newer version. This are the last few lines
Greetings!!!
sir I was setting up LTSP 4.1.0 using Mandrake 10.0 our workstaions are all
identical, evrything wroks fine exept for 1 workstation which was the bios was
updated to newer version. This are the last few lines the workstation displays:
Running dhcpd on port 67
Mounting root
Hi,
I would suggest you replace
/opt/ltsp/i386*(rw)
with
/opt/ltsp192.168.0.0/255.255.255.0(ro,no_root_squash,sync)
in your dhcpd.conf.
I am not sure but it could help.
Regards,
CS
Le lundi 09 Mai 2005 14:31, tritri_24 Tr|aN a écrit :
Hello list:
First, sorry for my bad english.
My
Hello list:
First, sorry for my bad english.
My thin client don't boot. Only load the kernel image, but no mount
the filesystem via NFS.
This is the message of the error:
Mounting root filesystem:/opt/ltsp/i386 from 192.168.0.254
mount: RPC: Time out
mount: nfsmount failed: Bad file descriptor
Hi,
Your next-server field in dhcpd.conf is invalid.
Remove/comment the entry.
Try mounting nfs on from any standard linux
installation on your network. Ensure the client runs
portmap, nfs, nfslock, rpc services and the firewall
is down.
# mkdir /mnt/temp
# mount -t nfs -o ro
Sorry, old information.
The IP for root-path in dhcpd.conf it's 192.168.0.254. I change it
yesterday, but I copied the message other time.
Here the real information to this moment in my net.
Mounting root filesystem:/opt/ltsp/i386 from 192.168.0.254
mount: RPC: Time out
mount: nfsmount failed:
tritri wrote:
FILE DHCPD.CONF
FILE EXPORTS
FILE HOSTS
Presumably these block capitals are a typo.
127.0.0.1 tritriserver localhost
192.168.0.10 ws010
I thought complete hostnames were necessary here.
-
FILE host.allow
1 - 100 of 282 matches
Mail list logo
