On 2012-04-18 19:23, Brett Glass wrote:
And then, there's the question of how to restart daemons (but not the
whole system!) when configurations are changed... when this is
possible.
Monit can be configured to do this, as a side effect of monitoring your
daemons.
It also likes to be in char
Brett Glass wrote:
> I have several nearly identical servers in my network, and would
> like to control their configurations entirely from one file ...
You might find sysutils/puppet useful.
___
freebsd-questions@freebsd.org mailing list
http://lists.
On 04/19/2012 02:32 AM, Erich Dollansky wrote:
> Hi,
>
> I think you have had the list twice in the address list.
>
> On Thursday 19 April 2012 06:23:26 Brett Glass wrote:
>
>> Has anyone out there worked on the problem of generating
>> configuration files for important daemons (e.g. mpd, dnscache
Hi,
I think you have had the list twice in the address list.
On Thursday 19 April 2012 06:23:26 Brett Glass wrote:
> Has anyone out there worked on the problem of generating
> configuration files for important daemons (e.g. mpd, dnscache from
are you sure that you really need this dynamically
Everyone:
I have several nearly identical servers in my network, and would
like to control their configurations entirely from one file (such
as /etc/rc.conf). Unfortunately, while some flavors of embedded
Linux have systems to do this, FreeBSD doesn't make it easy. A lot
of files (/etc/resolv
Hello all,
I have been browsing through the FreeBSD kernel's source
code trying to understand its working .
In the mi_startup() in /sys/kern/init_main.c all the SYSINIT objects are
sorted using bubble sort and then they are executed in order.
My doubt is that we have declared the
