> If you build a kernel without INET, the following switches don't > result in any daemons being started if you set them to YES: > > syslog_enable
> sendmail_enable > lpd_enable I think you are confused. These will all start regardless of whether INET is enabled. > These are all things that are clearly useful on a system without an > internet connection. None of them start if you disable INET in the > kernel. Neither the defaults/rc.conf file, the rc.conf man page, nor > the man pages for those daemons mentiont that INET is required in the > kernel to run them. Nor do the LINT or GENERIC files mention that > turning off INET will cause various daemons useful on a machine > without an internet connection to quit working. You seem surprised that programs which depend upon networking don't function as expected when it is not available. > If anyone is actually willing to > look at fixing these things, I'll PR them. And probably start a > witchhunt for other rc.conf variables that can be broken by careful > selection of options in the config file. Why not fix them yourself? The issues you're observing have nothing to do with rc.conf variables; they have to do with bugs in the above-referenced programs, specifically, they depend upon networking. > So simply > expanding the documentation and comments will solve the problem. No, it will not. Making the programs robust (where reasonable) is necessary. To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-stable" in the body of the message
