Actions
Bug #486
closedClamAV rules updates create ugly traces
Start date:
2015-10-25
Due date:
% Done:
100%
Estimated time:
Patch Available:
Confirmed:
No
Branch:
Entity:
DuckCorp
Security:
Help Needed:
Description
Oct 25 07:46:23 orfeo clamd[15822]: Reading databases from /var/lib/clamav Oct 25 07:46:38 orfeo clamd[15822]: pointer argument cannot be last argument Oct 25 07:46:38 orfeo clamd[15822]: ; Function Attrs: nounwind Oct 25 07:46:38 orfeo clamd[15822]: define internal fastcc i32 @bc1f0([136 x i8]*) #1 { Oct 25 07:46:38 orfeo clamd[15822]: %2 = bitcast [136 x i8]* %0 to i8* Oct 25 07:46:38 orfeo clamd[15822]: %3 = getelementptr inbounds [136 x i8]* %0, i32 0, i32 96 Oct 25 07:46:38 orfeo clamd[15822]: %4 = bitcast i8* %3 to [64 x i32]** Oct 25 07:46:38 orfeo clamd[15822]: %5 = load [64 x i32]** %4 …
This also causes:
Oct 25 07:46:38 orfeo rsyslogd-2177: imuxsock[pid 15822]: begin to drop messages due to rate-limiting Oct 25 08:49:38 orfeo rsyslogd-2177: imuxsock[pid 15822]: 6863 messages lost due to rate-limiting Oct 25 08:49:54 orfeo rsyslogd-2177: imuxsock[pid 15822]: begin to drop messages due to rate-limiting Oct 25 08:50:10 orfeo rsyslogd-2177: imuxsock[pid 15822]: 6864 messages lost due to rate-limiting …
Updated by Marc Dequènes almost 7 years ago
- Status changed from New to Resolved
- Assignee set to Marc Dequènes
- % Done changed from 0 to 100
Since we switched to BytecodeSecurity TrustSigned
it does not appear anymore. As we're most probably stuck using this setting, I see no reason to keep this BR around.
Actions