[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
RE: No reliable outputs in 2.1.15 ?
From: |
David Masterson |
Subject: |
RE: No reliable outputs in 2.1.15 ? |
Date: |
Wed, 12 Oct 2005 09:48:29 -0700 |
Chip Seraphine wrote:
> Martin, Jason H wrote:
>
>>> your own custom tweaks in (for example, I always change the
>>> hard coded default LOG_DAEMON and LOG_USER openlog calls in
>>> log.c to LOG_LOCAL1, which cuts down on the noise in my
>>> messages file).
>>
>> Sounds like that would be handy as a configurable value.
>>
> Anyone wise in the ways of autoconfig? It would make a lovely
> compile-time ./configure option. (I hacked such a patch together
> loooooong ago that replaced those tokens with #defined values set in
> defs, but that patch never made it in; I assumed that Mark would
> prefer it properly implemented in configure.ac rather than something
> that requires passing -Dfoo=bar lines.)
It's not that difficult. Just add #undef lines to src/conf.h.in for your
variables, then set up an appropriate AC_ARG_WITH() in the configure.ac file
(there are examples already in there) with appropriate AC_DEFINE statements.
Of course, you'll need to have Autoconf and Automake installed to test it out
with. Then do:
1. make maintainer-clean
2. aclocal; autoconf; autoheader; automake --add-missing
3. configure; make; make install
However, isn't this all already handled by the Syslog() and SyslogFacility()
calls in cfagent?
--
David Masterson
VMware, Inc.
Palo Alto, CA
- Re: No reliable outputs in 2.1.15 ?, (continued)
- RE: No reliable outputs in 2.1.15 ?, David Masterson, 2005/10/11
- RE: No reliable outputs in 2.1.15 ?, David Masterson, 2005/10/11
- RE: No reliable outputs in 2.1.15 ?, David Masterson, 2005/10/11
- RE: No reliable outputs in 2.1.15 ?, Martin, Jason H, 2005/10/11
- RE: No reliable outputs in 2.1.15 ?, Martin, Jason H, 2005/10/12
- RE: No reliable outputs in 2.1.15 ?, Martin, Jason H, 2005/10/12
- RE: No reliable outputs in 2.1.15 ?,
David Masterson <=