On Tue, 14 Jun 2005, Michael W. Lucas wrote:
a) old-style .sh scripts are not supported, Michael needs to rewrite them for
rcNG
b) old-style .sh scripts are supported, Michael has some other system problem
Have you tried moving out most of the scripts and leaving a subset.. if
those start
Hi,
i have follows your trouble with rc-scripts.
now im usind BSD for many years and i know! that *sh-ish rc-scripts
should be supported. But this is not my interest.
you have writte that the boxes with these behavior was updated from
RELENG_4 to RELENG_5? right?
if so double-check all these
I'm certain this is documented somewhere, but danged if I can find it.
I have a whole variety of custom scripts in /usr/local/etc/rc.d. For
years now, simply giving them a name ending in .sh and making them
executable has been sufficient to make them start on boot.
On 5.x, it's not. And now,
For scripts in /usr/local/etc/rc.d You should add an entry to /etc/rc.conf.
For example, if You script is somedaemon.sh, then add
somedaemon_enable='YES' to /etc/rc.conf and it will run at the next boot.
Cheers,
Gábor Kövesdán
Michael W. Lucas wrote:
I'm certain this is documented
You have to in rc.conf variable to run application as was for ssh and
others in this way:
if you want to run samba and dhcpd you have to put into rc.conf this:
samba_enable=YES
dhcpd_enable=YES
Il giorno mar, 14/06/2005 alle 11.02 -0400, Michael W. Lucas ha scritto:
I'm certain this is
That works fine for ports, but what about truly local custom scripts?
For example, I have a server with about 400 separate MRTG daemons on
it. (Yes, they must be separate, for administrative rather than
technical reasons.) Each daemon has a custom script. These aren't
ports, and they have no
On Jun 14, 2005, at 11:10 AM, Kövesdán Gábor wrote:
For scripts in /usr/local/etc/rc.d You should add an entry to /etc/
rc.conf.
For example, if You script is somedaemon.sh, then add
somedaemon_enable='YES' to /etc/rc.conf and it will run at the next
boot.
but his scripts don't use
]
Cc: [EMAIL PROTECTED]
Sent: Tuesday, June 14, 2005 4:19 PM
Subject: Re: /usr/local/etc/rc.d/*.sh not working?
That works fine for ports, but what about truly local custom scripts?
For example, I have a server with about 400 separate MRTG daemons on
it. (Yes, they must be separate
On Tue, 14 Jun 2005, Michael W. Lucas wrote:
I'm certain this is documented somewhere, but danged if I can find it.
I have a whole variety of custom scripts in /usr/local/etc/rc.d. For
years now, simply giving them a name ending in .sh and making them
executable has been sufficient to make
On Jun 14, 2005, at 11:19 AM, Michael W. Lucas wrote:
For example, I have a server with about 400 separate MRTG daemons on
it. (Yes, they must be separate, for administrative rather than
technical reasons.) Each daemon has a custom script. These aren't
ports, and they have no rcNG
On Tue, Jun 14, 2005 at 11:22:07AM -0400, Vivek Khera wrote:
On Jun 14, 2005, at 11:10 AM, K?vesd?n G?bor wrote:
For scripts in /usr/local/etc/rc.d You should add an entry to /etc/
rc.conf.
For example, if You script is somedaemon.sh, then add
somedaemon_enable='YES' to /etc/rc.conf
On Tuesday 14 June 2005 18:58, Michael W. Lucas wrote:
On Tue, Jun 14, 2005 at 11:22:07AM -0400, Vivek Khera wrote:
On Jun 14, 2005, at 11:10 AM, K?vesd?n G?bor wrote:
For scripts in /usr/local/etc/rc.d You should add an entry to /etc/
rc.conf.
For example, if You script is somedaemon.sh,
On Tue, Jun 14, 2005 at 11:58:36AM -0400, Michael W. Lucas wrote:
On Tue, Jun 14, 2005 at 11:22:07AM -0400, Vivek Khera wrote:
On Jun 14, 2005, at 11:10 AM, K?vesd?n G?bor wrote:
For scripts in /usr/local/etc/rc.d You should add an entry to /etc/
rc.conf.
For example, if You script
On Tue, Jun 14, 2005 at 06:43:55PM +0200, Erik Trulsson wrote:
On Tue, Jun 14, 2005 at 11:58:36AM -0400, Michael W. Lucas wrote:
On Tue, Jun 14, 2005 at 11:22:07AM -0400, Vivek Khera wrote:
On Jun 14, 2005, at 11:10 AM, K?vesd?n G?bor wrote:
For scripts in /usr/local/etc/rc.d You
On Tue, Jun 14, 2005 at 11:19:04AM -0700, Brooks Davis wrote:
It's b) and this guess is wrong because we don't do any detection of
rcorder compatable scripts yet. See /etc/rc.d/localpkg for exactly how
the scripts in /usr/local/etc/rc.d get run.
My suggestion would be to write up a single
On 2005.06.14 14:25:13 -0400, Michael W. Lucas wrote:
On Tue, Jun 14, 2005 at 11:19:04AM -0700, Brooks Davis wrote:
It's b) and this guess is wrong because we don't do any detection of
rcorder compatable scripts yet. See /etc/rc.d/localpkg for exactly how
the scripts in /usr/local/etc/rc.d
On Tue, Jun 14, 2005 at 02:25:13PM -0400, Michael W. Lucas wrote:
On Tue, Jun 14, 2005 at 11:19:04AM -0700, Brooks Davis wrote:
It's b) and this guess is wrong because we don't do any detection of
rcorder compatable scripts yet. See /etc/rc.d/localpkg for exactly how
the scripts in
On Tue, Jun 14, 2005 at 11:19:39AM -0400, Michael W. Lucas wrote:
For example, I have a server with about 400 separate MRTG daemons on
it. (Yes, they must be separate, for administrative rather than
technical reasons.) Each daemon has a custom script. These aren't
ports, and they have no
On Wed, 15 Jun 2005 01:18, Vivek Khera wrote:
On Jun 14, 2005, at 11:19 AM, Michael W. Lucas wrote:
For example, I have a server with about 400 separate MRTG daemons on
it. (Yes, they must be separate, for administrative rather than
technical reasons.) Each daemon has a custom script.
On Wed, Jun 15, 2005 at 10:46:22AM +0930, Daniel O'Connor wrote:
On Wed, 15 Jun 2005 01:18, Vivek Khera wrote:
On Jun 14, 2005, at 11:19 AM, Michael W. Lucas wrote:
For example, I have a server with about 400 separate MRTG daemons on
it. (Yes, they must be separate, for administrative
20 matches
Mail list logo
