Comment 7 for bug 94804

My pleasure sir.

From dhcpd.conf:

##Config file starts##
authoritative;
subnet 10.1.1.0 netmask 255.255.255.0 {
  range 10.1.1.3 10.1.1.250;
  option domain-name "sneakywhoami.biz";
 option domain-name-servers 127.0.0.1, 202.27.158.40, 202.27.156.72, 208.67.222.222;
  option broadcast-address 10.1.1.255;
  option routers 10.1.1.1;
# next-server 192.168.0.254;
# get-lease-hostnames true;
  option subnet-mask 255.255.255.0;
    option root-path "/opt/ltsp/i386";
    if substring( option vendor-class-identifier, 0, 9 ) = "PXEClient" {
        filename "/ltsp/i386/pxelinux.0";
    } else {
        filename "/ltsp/i386/nbi.img";
    }
}
##Config file ends##

My last message lacked crucial detail though.
On further inspection I find something more interesting. There are two obvious ways to generate an error message (or no error message)

My blank error message was caused by not having root privilege at the moment that I called dhcp3-server and it started successfully when I did sudo it. As I stated in my last message, it only stated the error after I had reverted your edit to the script dhcp3-server
BUT
Fixing the error output for permissions problems breaks the output for config file problems..

So your fix perfectly solved the problem, but there seems to be some other problem, perhaps this should be in a different bug report..?
To put it differently:

"/usr/sbin/dhcpd3 -t -q -cf $CONFIG_FILE" only prints an error WITHOUT sudo
"/usr/sbin/dhcpd3 -t -cf $CONFIG_FILE 2>&1| sed '1,4d'" only prints an error WITH sudo

I still don't feel that's very clear. Sorry for any confusion.