Hi everybody, I'm a new mebmer to this list, but I've used LTSP v4.1(.1 ) for a few months.
Since I used LTSP v4.1(.1) with SuSE 9.0 and thin clients from IBM (NetVista 2000 8363) with kernel 2.4.19 -friendly sent to me by Karl Kappel-, there were no problems. Now I have installed CentOS 4.3 for the LTSP machine and I have discovered, that there are problems, perhaps with firewall and/or SELinux in conjunction with X, tftp or nfs. However, the IBM NetVista did not boot. Ok, please have a look to that, what I have done to "solve" the problem (it isn't solved utill now). On the CentoOS box I configured the firewall with the ports shown at LTSP Wiki. 69:udp (tftp) 111:tcp (Portmapper) 111:udp (Portmapper) 177:udp (XDMCP) 514:udp (Syslog) 2049:tcp (NFS) 2049:udp (NFS) 6000:tcp to 6063:tcp (X; should there be udp defined for these ports too?) and for extended functionality (future requests? ;) ) 7100:tcp (XFS) 7100:udp (XFS) 9100:tcp (printer via LTSP) 9101:tcp (printer via LTSP) 9102:tcp (printer via LTSP) 9200:tcp (ltspinfo) 9210:tcp (ltspswap; NBD Swap Server) 16001:tcp (ESD Sound) 16001:udp (ESD Sound) But this did not change anything. Then I turned off SELinux. Same. I turned off the firewall and the Client boots. Are ther any other ports needed? But the client did not boot completely into X! Here is the error message: ---8<--- Building the /tmp/XF86Config-4 file Fatal server error: Cannot open log file "/var/log/Xorg.0.0.log" --->8--- Is this a error caused by nfs or X? I don't know. Then, I turned on again SELinux. No effect. Of course I know, SELinux will not have any positive effect helping for booting a thin client ;) , but I think, SELinux belongs to a security feature of CentOS / RHEL, and it has to be turned on. Without SELinux I think CentOS will not be needed, or? Or do I have to turn it off for LTSP purposes? Next I have configured a telnet shell and a ssh login shell for console 2 and 3. The client now boots to a shell on console 2 and the ssh login on console 3, but X did not start in any way. Same procedure... :( Now I think, that SELinux does not affect booting with the services tftp and nfs, or am I wrong?. But remote X? In the meantime I have tested another Linux box as a fat client, with "X :1 -query ltspservername" and ... got the CentOS GUI login prompt (xdm). Ok, so far XDM and remote X seems to be unaffected by SELinux. Using the same fat client for booting from ltsp (PXE; Intel PRO/100 PCI), the same error message as above will appear (Fatal server error: Cannot open log file "/var/log/Xorg.0.0.log"). :( Now I do not know, where to search for the solution of this problem. For a first step: is there anyone out there, who has set up LTSP 4.1.x on a CentOS 4.3 box or Red Hat Enterprise Linux 4 box and for a second step is she or he using firewall and SELinux, too? I will be glad if someone may give me a hint. Please excuse my bad english. Thanks a lot. Regards Sven -- "Feel free" - 10 GB Mailbox, 100 FreeSMS/Monat ... Jetzt GMX TopMail testen: http://www.gmx.net/de/go/topmail ------------------------------------------------------- This SF.Net email is sponsored by xPML, a groundbreaking scripting language that extends applications into web and mobile media. Attend the live webcast and join the prime developer group breaking into this new coding territory! http://sel.as-us.falkag.net/sel?cmd=lnk&kid=110944&bid=241720&dat=121642 _____________________________________________________________________ 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
