Darren J Moffat wrote:
Darren Reed wrote:
Darren J Moffat wrote:
Logging everything that is available from a given DHCP server is easy.
Just create an /etc/dhcp/eventhook script that grabs all the
interesting things using dhcpinfo and write them out to a file
format you like with appropriate time stamps.
Something based off this simple for loop should do what you want:
for option in $(nawk '/^#/ { next } /^$/ { next } {print $1}'
/etc/dhcp/inittab) ; do
value="$(/sbin/dhcpinfo $option 2> /dev/null)"
echo "$option"="$value"
done
Unless you're proposing that this be added to Solaris for
everyone, I'd classify this as a work around for the problem.
Exactly what problem is that though ? Is it really necessary for
every Solaris machine to have a log of all this info ?
The problem is having an audit trail of how your machine's networking
has been configured over time and I believe it is of benefit for Solaris
machines to record this information through syslogd.
How do you deal with log management ? Do you intend to have tools to
do something with the data or is it just paging through the raw log.
The problem of log management, etc, should not be a detterence from
using logs. Otherwise we might as well ship with syslogd disabled (and
nothing using it) because there's no complete log management solution in
Solaris today.
...
Ultimately it really sounds like a debug trace for dhcpagent(1m) and I
don't see how that is actually interesting to the vast majority of
people who use any OpenSolaris derived OS as an end user, or in most
cases even as the admin responsible for network config.
Well it would be nice if dhcpagent used syslog for recording information
that was actually useful rather than what it does now, with close to 200
messages a day of nothing worth more than a yawn. Most of it is telling
me the lease will expire in x seconds. I'd rate this as substantially
less interesting than the network information used to configure the
interface, yet we log it.
In this thread, my basis of comparison is the DHCP client software from
ISC and its default behaviour.
But the point is in this comment you made: "Q: How often did I look at
it ? Almost NEVER." The point here being that if you never had it then
you'd never have been able to use it.
Most of the time I don't find the information useful either, but if it
is never there then when I do want it, it's not available. I'd much
rather it be there and rarely/never used than never there and impossible
to make useof.
Darren
_______________________________________________
networking-discuss mailing list
[email protected]
