Gergely CZUCZY wrote:
On Wed, Nov 21, 2007 at 11:43:35PM -0800, Doug Barton wrote:
Gergely CZUCZY wrote:
echo 'sevice_enable=YES' /etc/rc.conf.local
Yes, I think we all know how to go about this manually. The question
at hand is whether or not it's possible or desirable to create the
Gergely CZUCZY wrote:
echo 'sevice_enable=YES' /etc/rc.conf.local
Yes, I think we all know how to go about this manually. The question
at hand is whether or not it's possible or desirable to create the
possibility of doing it for the user at port install time.
If what you're trying to say
On Wed, Nov 21, 2007 at 11:43:35PM -0800, Doug Barton wrote:
Gergely CZUCZY wrote:
echo 'sevice_enable=YES' /etc/rc.conf.local
Yes, I think we all know how to go about this manually. The question
at hand is whether or not it's possible or desirable to create the
possibility of doing it
On Thu, Nov 22, 2007 at 12:43:50AM -0800, Doug Barton wrote:
On Thu, 22 Nov 2007, Gergely CZUCZY wrote:
Gergely CZUCZY wrote:
echo 'sevice_enable=YES' /etc/rc.conf.local
I said, that this can be done from the Makefile as well, if that OPTIONS
of yours is enabled.
But that would
On Thu, 22 Nov 2007, Gergely CZUCZY wrote:
Gergely CZUCZY wrote:
echo 'sevice_enable=YES' /etc/rc.conf.local
I said, that this can be done from the Makefile as well, if that OPTIONS
of yours is enabled.
But that would violate the principle that ports shouldn't touch files in
/etc.
On Wed, 21 Nov 2007 22:48:59 -0800
Doug Barton [EMAIL PROTECTED] wrote:
RW wrote:
On Wed, 21 Nov 2007 12:14:17 -0800
Doug Barton [EMAIL PROTECTED] wrote:
... I have for some time wanted to add
support to rc.subr for a /usr/local/etc/rc.conf.d so that ports
Scot Hetzel wrote:
On Sun, Nov 18, 2007 at 08:17:36PM -0500, Chuck Robey wrote:
activate the port, and if so, the port would add a line of the form
'portname_enable=YES', and this would make your new port operate.
Well, it seems from what I see of my new system, that this is no longer
the
On Wed, 21 Nov 2007 12:14:17 -0800
Doug Barton [EMAIL PROTECTED] wrote:
... I have for some time wanted to add support
to rc.subr for a /usr/local/etc/rc.conf.d so that ports could install
sensible defaults for rc.conf,
What's the advantage of doing that over having
RW wrote:
On Wed, 21 Nov 2007 12:14:17 -0800
Doug Barton [EMAIL PROTECTED] wrote:
... I have for some time wanted to add support
to rc.subr for a /usr/local/etc/rc.conf.d so that ports could install
sensible defaults for rc.conf,
What's the advantage of doing
On Wed, Nov 21, 2007 at 10:48:59PM -0800, Doug Barton wrote:
RW wrote:
On Wed, 21 Nov 2007 12:14:17 -0800
Doug Barton [EMAIL PROTECTED] wrote:
... I have for some time wanted to add support
to rc.subr for a /usr/local/etc/rc.conf.d so that ports could install
On 11/18/07, Edwin Groothuis [EMAIL PROTECTED] wrote:
On Sun, Nov 18, 2007 at 08:17:36PM -0500, Chuck Robey wrote:
activate the port, and if so, the port would add a line of the form
'portname_enable=YES', and this would make your new port operate.
Well, it seems from what I see of my new
Naram Qashat wrote:
Also a good thing to point out is that portupgrade can be configured to
automatically start or stop a port's daemon via it's /usr/local/etc/rc.d
script, which still relies on having the appropriate line in
/etc/rc.conf to tell the rc.d script to run, but it is helpful for
In the pkgtools.conf file that portupgrade installs, there's two sections,
BEFOREINSTALL and AFTERINSTALL. In BEFOREINSTALL, you could put the following
in to make it try to stop the service if there's an rc script for the port:
'*' = proc { |origin| cmd_stop_rc(origin) }
And almost the same
Edwin Groothuis wrote:
On Sun, Nov 18, 2007 at 08:17:36PM -0500, Chuck Robey wrote:
activate the port, and if so, the port would add a line of the form
'portname_enable=YES', and this would make your new port operate.
Well, it seems from what I see of my new system, that this is no longer
the
Scot Hetzel wrote:
On 11/18/07, Edwin Groothuis [EMAIL PROTECTED] wrote:
On Sun, Nov 18, 2007 at 08:17:36PM -0500, Chuck Robey wrote:
activate the port, and if so, the port would add a line of the form
'portname_enable=YES', and this would make your new port operate.
Well, it seems from what I
Naram Qashat wrote:
In the pkgtools.conf file that portupgrade installs, there's two
sections, BEFOREINSTALL and AFTERINSTALL. In BEFOREINSTALL, you could
put the following in to make it try to stop the service if there's an rc
script for the port:
'*' = proc { |origin| cmd_stop_rc(origin)
I was wondering why ports apparently aren't allowed an obvious freedom,
that of being able to set themselves to run as daemons. A greate long
time past, I seem to remember that there used to be a file
/usr/local/etc/rc.local, which (if it existed) would be automatically
sourced in at the end
On Sun, Nov 18, 2007 at 08:17:36PM -0500, Chuck Robey wrote:
activate the port, and if so, the port would add a line of the form
'portname_enable=YES', and this would make your new port operate.
Well, it seems from what I see of my new system, that this is no longer
the case. I could
Also a good thing to point out is that portupgrade can be configured to
automatically start or stop a port's daemon via it's /usr/local/etc/rc.d script,
which still relies on having the appropriate line in /etc/rc.conf to tell the
rc.d script to run, but it is helpful for upgrading ports which
19 matches
Mail list logo
