I've just spent a hair-tearing day trying to get qpopper 4.0.9 to work on my new LFS system.
The problem was that popper kept exiting after trying to do its second fork. This was on a system that was using xinetd (there is more detail about the problem, and log extracts, over on the LFS support list, because I initially thought the problem was something more basic than either qpopper or xinetd). The "solution" was to leave off the --enable-standalone option when configuring qpopper. I don't know why this solved the problem, but it did (I reproduced this several times). Of course, without the option I can't run qpopper standalone...but then the only time I've ever done that was today when I was trying to figure out why popper was dying under xinetd but running okay standalone. I think this might deserve mention in the BLFS errata. - Mark __________ Information from ESET NOD32 Antivirus, version of virus signature database 3057 (20080426) __________ The message was checked by ESET NOD32 Antivirus. http://www.eset.com -- http://linuxfromscratch.org/mailman/listinfo/blfs-support FAQ: http://www.linuxfromscratch.org/blfs/faq.html Unsubscribe: See the above information page
