freebsd stable - Mar 2006 - Switch to using rc.d for local packages is premature for RELENG_6

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.

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.

Therefore, I think that the RELENG_6 should be reverted to using old 
stuff and it should be left for 7.x tree.

Regards,

Maxim

I have just realized that maybe the best approach to address this 
problem would be not reverting the change in question, but making 
find_local_scripts_new() more strict, so that only those local rc.d 
scripts that have been explicitly marked by maintainer as fully 
rc.d-safe are handled in a new way. Checking for '^# PROVIDE:'
doesn't
really work reliably.

-Maxim

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.
> 
> 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.
> 
> Therefore, I think that the RELENG_6 should be reverted to using old 
> stuff and it should be left for 7.x tree.
> 
> Regards,
> 
> Maxim
>

On Mar 21, 2006, at 11:23 PM, Maxim Sobolev wrote:
> 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
I upgraded a server from 5.4-stable to 6.1-PRERELEASE on march 2, and  
postgres started up just fine as did apache 2.0.  i even did a full  
reinstall of all ports and it continued to work.

On Tue, Mar 21, 2006 at 08:23:40PM -0800, 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.
Did you e.g. neglect to mergemaster?  This really does work for others.

Kris
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 189 bytes
Desc: not available
Url :
http://lists.freebsd.org/pipermail/freebsd-stable/attachments/20060322/4643f58a/attachment.pgp

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
mfc'ed.
> 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.

Doug

-- 

    This .signature sanitized for your protection