Switch to using rc.d for local packages is premature for RELENG_6

Doug Barton dougb at FreeBSD.org
Wed Mar 22 23:40:30 UTC 2006

Maxim Sobolev wrote:
> Hi guys,
> As part of testing how well some of our products work with latest
> RELENG_6, I have make a new build and found that lot of important
> services (for example PostgreSQL, Apache) doesn't start up (despite
> having respective xxx_enable entries in /etc/rc.conf) when installed
> from the freshly updated ports tree onto a clean, freshly updated
> RELENG_6 system. This is very bad, considering how close to release are
> we and how much FreeBSD users rely on those services to work OOB.

While I can certainly appreciate your frustration, "it doesn't work" isn't
much of a bug report. You mentioned latest RELENG_6, and if you got the new
local_startup code then I assume that you've mergemaster'ed, that leaves
your ports. Are you using the latest versions of everything? The two
specific examples you gave have both been updated since the first of the
year to address problems that surfaced after the local_startup change was

> I would expect them to be really pissed off when lot of important
> services just don't work after upgrading their server from 6.0 to 6.1 or
> after installing it from install cd. This is apparently caused by the
> fact that lot of rc.d scripts in /usr/local/etc/rc.d are newstyle one
> now (sufficiently newstyle to pass find_local_scripts_new check), but
> few of them were actually tested to work correctly in fully rc.d
> environment.

On the contrary, as I said above, the two you mentioned specifically have
both been upgraded for the new environment. If you can provide more
information (perhaps as a followup to the -ports list) I'm sure we can help
you debug it more thoroughly.



    This .signature sanitized for your protection

More information about the freebsd-stable mailing list