First, I somewhat conjoined two effects of these debug msgs from asb100
so let me clarify the effects and resultant problem (and modify the
subject line):
1) the debug msgs from asb100 (invoked via dev_dbg() in asb100.c) get
dumped into the kernel ring buffer, such that it gets outputted if
'dmesg' is invoked (but this *doesn't* apparently fill or effect my
/var/log partition)
2) they also get dumped into /var/log/debug and /var/log/kern.log (this
*does* cause a filling of my /var/log partition)
It is the filling of my /var/log partition that is of concern to me most
of all.
On 12/04/17 10:51, KP Kirchdoerfer wrote:
> The option [CONFIG_I2C_DEBUG_BUS] is already disabled - at least
> in 4.2.
>
> So this is not the cause of the problem, unfortunately.
Alas, I guess this forced me to do this right? way ... by reconfiguring
syslog-ng (via /etc/syslog-ng/syslog-ng.conf) to 'ignore' the logging of
these debug msgs.
I chose to have syslog-ng pipe to /dev/null any messages that are of
level DEBUG, and contain text found in both these lines of information.
To accomplish this I added, at the end of the 'destinations' section of
the syslog-ng config file:
> destination my_dp_null { pipe("/dev/null" owner("root") group("root")
> perm(0777) ); };
and at the end of the 'filters' section:
> filter my_f__debug__asb100_device_update {
> level(debug)
> and match("kernel:.* asb100 .* device update");
> };
and at the *beginning* of the 'log' section:
> log {
> source(s_all);
> filter(my_f__debug__asb100_device_update);
> destination(my_dp_null);
> flags(final);
> };
Works like a charm regarding stopping the filling of my /var/log partition!
I'm still left with the noisome overrunning of dmesg output but suspect
that I'm SOL for resolving that one (i.e. as with the shorewall logging
msgs also cluttering/overfilling dmesg's output).
PS: Thx for your quick response KP - it promptly moved me along to
finding this solution.
Cheers & thanks all, for LEAF!
------------------------------------------------------------------------------
For Developers, A Lot Can Happen In A Second.
Boundary is the first to Know...and Tell You.
Monitor Your Applications in Ultra-Fine Resolution. Try it FREE!
http://p.sf.net/sfu/Boundary-d2dvs2
------------------------------------------------------------------------
leaf-user mailing list: [email protected]
https://lists.sourceforge.net/lists/listinfo/leaf-user
Support Request -- http://leaf-project.org/
