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

2006-03-22 Thread Vivek Khera
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

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

2006-03-22 Thread Kris Kennaway
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

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

2006-03-22 Thread Scott Robbins
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On Wed, Mar 22, 2006 at 01:35:24PM -0500, Kris Kennaway wrote: 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

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

2006-03-22 Thread Doug Barton
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

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

2006-03-21 Thread Maxim Sobolev
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

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

2006-03-21 Thread Maxim Sobolev
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