We can have two types of configuration files
1 - /etc/vblade.cfg
2 - ~/.vbladerc-$-$
The second allows more granular control over how vblade behaves in
respect to what it targets.
So, vbladed 0 1 will load defaults from /etc if they exist, then
~/.vbladerc-0-1 which can over-write those defaults (partly, or fully).
Will this be OK?
No, I won't rely on tidle (~) expansion from the shell.
This allows (beyond nice) a user to specify logging targets based on the
shelf, etc, selected. 0 1 is local syslog, 0-2 though 0-5 might be
Since the second inherits the first, the second can be quite minimal.
Tim Post wrote:
> We can have two types of configuration files
> 1 - /etc/vblade.cfg
> 2 - ~/.vbladerc-$-$
At first glance, for a general-purpose utility that seems fine.
However, as vblade is a very specialized system utility and, since it
requires opening of a raw socket, it's going to need root privileges at
some point in time. That being said, I can't forsee more than one user
running vblade at a time on a given machine: either it's run as root or
run as a service account, both of which would (presumably) require
administrator access to a machine. I think one config file should be
sufficient; shelf/slot-specific config stanzas in /etc/vblade.conf can
be separated using syntax, or, if individual files are deemed necessary
they should probably be in /etc/vblade.d/ or something, instead of a
user's home directory. ~/.*rc files are usually specified for
interactive utilities rather than system daemons.
Sr. Systems Administrator, DrJays.com
9180 Camino Santa Fe, San Diego, CA 92121
888.437.5297x134 (desk) 619.852.6374 (cell)