Re: sysrc -- a sysctl(8)-like utility for managing /etc/rc.conf et. al.

2010-10-07 Thread Douglas K . Rand
I think that this script might also fill a void with using Puppet as a
configuration tool. Currently Puppet, as its default behaviour, uses
files in /etc/rc.conf.d to set variables. I've found this approach
really lacking because you cannot do things like:

  nfs_server_enable=YES

via a /etc/rc.conf.d file because multiple things (like lockd, mountd,
nfsd, nfsserver, and statd) all need nfs_server_enable set, as one
example. This script would provide an easy method for puppet to edit
lines in /etc/rc.conf.

I have a feature request though: How about a switch like -c
config-file to change which file sysrc_set adds the line to. We use
both /etc/rc.conf and /etc/rc.conf.local on some systems, and it would
be nice to be able to specify that this particular knob should be
placed in /etc/rc.conf.local. I'm unsure what should happen if -c is
specified and the knob you want to change already exists in another
rc.conf file: Should it be moved to the new location, or changed where
it is? (Maybe that'd be yet another option to sysrc.)

___
freebsd-hackers@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-hackers
To unsubscribe, send any mail to freebsd-hackers-unsubscr...@freebsd.org


Re: sysrc -- a sysctl(8)-like utility for managing /etc/rc.conf et. al.

2010-10-07 Thread Douglas K . Rand
Warren Consider also the docs that tell the user to
Warrenecho 'something_enable=YES'  /etc/rc.conf

Warren which can produce duplicate and possibly differing entries.

Yup!  Which is exactly why I like the idea of this tool.
___
freebsd-hackers@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-hackers
To unsubscribe, send any mail to freebsd-hackers-unsubscr...@freebsd.org


Nagios Linux Threads

2006-04-10 Thread Douglas K. Rand
I'm running Nagios 2.0 on FreeBSD 6 and I occasionally experience the
problem originally discussed 
http://www.freebsd.org/cgi/getmsg.cgi?fetch=165398+171880+/usr/local/www/db/text/2005/freebsd-hackers/20050821.freebsd-hackers

(That is: a forked nagios process that consumes as much CPU time as it
can.)

Living with this problem while annoying isn't the end of the world. I
was looking for workarounds.

One solution for a work around was to use Linux threads. I was
wondering if anybody had managed to get Nagios 2.0 to use Linux
threads successfully. And if so, what changes to the port were
required. 

___
freebsd-hackers@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-hackers
To unsubscribe, send any mail to [EMAIL PROTECTED]


Re: FreeBSD boot manager, where is latest version?

2001-01-16 Thread Douglas K. Rand

I've recently switched to Smart Boot Manager which I noticed on
freshmeat awhile ago. You can find it at
http://www.gnuchina.org/~suzhe/ I found it easiest to download the DOS
.exe and put it on a floppy and install it that way. For fitting in
the boot block (no seperate partition required) it has quite a number
of features.



To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-hackers" in the body of the message



Re: several NFS mounts within a filesystem

2000-08-17 Thread Douglas K. Rand

** Peter Pentchev [EMAIL PROTECTED] on Wed, 16 Aug 2000 19:47:52 +0300
** in [several NFS mounts within a filesystem] writes:

Peter OK, so it might very well be that I haven't read everything; in that
Peter case, sorry for taking your time. However..

Peter Am I right in thinking that the kernel won't let me export more
Peter than one subdir of the same filesystem?  If so, how do I get
Peter around this?

What you want to do is either include the -alldirs as "Kenneth
D. Merry" [EMAIL PROTECTED] suggests, or list the directories you want to
export on the same line. From my /etc/exports:

   /usr/ports /usr/src /usr/obj-network=x.x.x.0 -mask=255.255.255.0 -maproot=root

/usr/ports, /use/src, and /usr/obj are all on the /usr file system,
and this exports only those directories.



To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-hackers" in the body of the message