Date: Mon, 28 Apr 2008 22:10:04 GMT From: Volker <volker@vwsoft.com> To: freebsd-bugs@FreeBSD.org Subject: Re: bin/123065: inetd takes 100% cpu Message-ID: <200804282210.m3SMA4uS013613@freefall.freebsd.org>
next in thread | raw e-mail | index | archive | help
The following reply was made to PR bin/123065; it has been noted by GNATS. From: Volker <volker@vwsoft.com> To: bug-followup@FreeBSD.org, thogard@abnormal.com Cc: Subject: Re: bin/123065: inetd takes 100% cpu Date: Tue, 29 Apr 2008 00:05:12 +0200 Tim, while your idea might look nice in the first place, I see a lot problems with that solution. I think you're already aware of the security risks of your hack. Your config instructs inetd to set verbose debugging mode, bind to a specific IP address and write it's pidfile to /tmp. It is not guaranteed (and by default not the case) to have 1) syslogd running in single user mode and 2) the network interfaces are up. Also inetd lives in /usr/sbin, needs libs from /usr/lib, telnetd lives in /usr/libexec and also needs libs from /usr/lib. In single user mode the only filesystem mounted will be the root-fs and it's mounted read-only. syslogd logs by default to /var/log. Please make sure, filesystems root-fs, /usr, /var and /tmp are mounted and /tmp and /var are writable, syslogd is started. If you can make sure all these conditions are met, please check if you can reproduce this. If the problem persists, we need ktrace debug output. Also when logging in and out, login(1) tries to write wtmp which may also fail with r/o mounts. Please keep in mind, your solution should not be used in the public network. Volker
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?200804282210.m3SMA4uS013613>