The workaround: 1. Create a script in the chroot whose purpose is to set up proper permissions on the client resolver file:
$ sudo touch /opt/ltsp/i386/etc/init.d/chmod-resolv.sh Contents: ----------- #! /bin/sh chmod 644 /etc/resolv.conf ----------- 2. Rebuild the client image 3. Add options to lts.conf (DNS search domain and nameserver for your network; and location of above file relative to the chroot) ----------- SEARCH_DOMAIN = example.com DNS_SERVER = 192.168.1.1 RCFILE_01 = /etc/init.d/chmod-resolv.sh ----------- -- jaunty ltsp client creates /etc/resolv.conf with 000 permissions https://bugs.launchpad.net/bugs/347957 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list [email protected] https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
