Please do not reply directly to this email. All additional comments should be made in the comments box of this bug report.
Summary: Review Request: ltsp-server-config - LTSP5 server-side configurations and setup scripts
https://bugzilla.redhat.com/show_bug.cgi?id=331731
------- Additional Comments From eharrison@mesd.k12.or.us 2007-10-17 20:17 EST ------- (in reply to comment #31)
At least iptables-ltsp (until an alternative is implemented) and ltsp-dhcpd need to be started by default if the server is configured to boot thin clients.
I'll contact the iptables maintainer
usr/share/ltsp5/config/ltsp-dhcpd.conf fixed.
I changed ltsp-dhcpd-create to cat because I was going to make it a template and run it through sed (i.e. cat ltsp-dhcpd.conf.template | sed s/IP/$IP/ > /etc/ltsp-dhcpd.conf), but got side-tracked fixing other bugs.
I added an empty file in etc/ltsp-dhcpd.conf because %{ghost} & friends were complaining that the file did not exist. I need to read up on the docs on that one, I'm obviously doing something wrong.
/tftpboot/ltps5/pxe fixed.
tftpd chroots into /tftpboot/, a symlink will not work.
Jim McQuillian @ LTSP contacted the LSB long ago asking for assistance on where to place the ltsp root. They settled on /opt/. I just checked and both Ubuntu and Debian are currently using /opt/ for their ltsp5 implementations. I didn't see where they are putting the swap files. I'll get to that shortly. That said, I'm not particularly attached to /opt/, but it is nice to be consistent with everyone else.
I just pushed out an update with a bunch of scripting fixes. I'll push out all of the above changes here shortly.