As I posted in blfs-support, it appears portmapper, at least when run using
the blfs bootscript (and not started by inetd/xinetd as the portmapper manpage
recommends), runs as UID 1 regardless of whether or not that is even a valid
UID. Either the book needs to add a "bin" user (I assume that's what it wants
to run as) for portmapper, or (preferably) a patch to portmap is needed.

Actually I suppose that if running under xinetd fixes the problem, that could
be the solution, too.

Jeremy
--
http://linuxfromscratch.org/mailman/listinfo/blfs-dev
FAQ: http://www.linuxfromscratch.org/blfs/faq.html
Unsubscribe: See the above information page

Reply via email to