why use setlogmask, really?

[Brian J. Murrell]

In dhcpd.c there is a call right after the openlog() call:

	setlogmask (LOG_UPTO (LOG_INFO));

Why do this?  Isn't this what the syslog.conf file is for?  Maybe it's done
in the server to reduce the number of actual calls made to syslogd?  If
this is the case, then I think a dhcpd.conf file flag is more appropriate
than hard-coding, no?  Maybe it is assumed that nobody other than hackers
would want to see debugging.  I find it handy to be able to turn off and on
because the change control required to actually place a new binary on a
production server is nothing less than Himalayan.

b.



--
Brian J. Murrell                                        Brian_Murrell at bctel.net
BCTel Advanced Communications                                      604 454 5279
Vancouver, B.C.