I've asked -ports before whether it is suitable to let ports startup scripts
honor /etc/rc.conf{,.local} settings by sourcing /etc/defaults/rc.conf and
then running a source_rc_confs (or whatever is appropriate).
my suggestion:
this is the 'modified' loop for the ${local_startup} in
On Thu, Jun 14, 2001 at 10:49:11AM +0300, Danny Braniss wrote:
I've asked -ports before whether it is suitable to let ports startup scripts
honor /etc/rc.conf{,.local} settings by sourcing /etc/defaults/rc.conf and
then running a source_rc_confs (or whatever is appropriate).
my
Peter Pentchev([EMAIL PROTECTED])@2001.06.14 20:19:27 +:
OK, and what do I do if I want to manually start/stop the service later,
and it needs variables defined in /etc/rc.conf{,local} ?
if [ x${_RC_CONF} != x1 ]; then . /etc/rc.conf; fi
in the beginning of the local startup script?
if it
On Thu, Jun 14, 2001 at 08:59:16PM +0200, Karsten W. Rohrbach wrote:
Peter Pentchev([EMAIL PROTECTED])@2001.06.14 20:19:27 +:
OK, and what do I do if I want to manually start/stop the service later,
and it needs variables defined in /etc/rc.conf{,local} ?
if [ x${_RC_CONF} != x1 ];
the idea is to modify /etc/rc to not start stuff in /usr/local/etc/rc.d
blindly,
and just 'extrapolate' rc.conf.
you can still start/stop the /usr/local/etc/rc.d/*.sh to your heart content,
i didn't propose changing them, though modifying mysql-server.sh to
mysql_server.sh would make things
5 matches
Mail list logo
