When I run my cron task to update SA. I am getting a LOT of lines in the crpn output along the lines of
info: rules: meta test KAM_REALLY_FAKE_DELIVER has dependency 'KAM_RPTR_PASSED' with a zero score
And a lot of compile lines like:
cc -c -DHAS_FPSETMASK -DHAS_FLOATINGPOINT_H -DUSE_THREAD_SAFE_LOCALE -fno-strict-aliasing -pipe -fstack-protector-strong -I/usr/local/include -D_FORTIFY_SOURCE=2 -O2 -pipe -fstack-protector-strong -fno-strict-aliasing -DVERSION=\"1.0\" -DXS_VERSION=\"1.0\" -DPIC -fPIC "-
Basically, I get about 200 lines each day. I am assuming something is wrong in my setup?
Crontab:
19 1 * * * sa-update ; sa-update --gpgkey 24C063D8 --channel kam.sa-channels.mcgrail.com ; sa-compile && service sa-spamd restart
I could redirect sa-compile to null, of course, but having spamd restart only when the compile succeeds seems like a good idea?
Also, I don't remember SA being this noisy? OTOH, I don't keep these cron logs more than a day or two, so maybe they were always this noisy and I didn't notice.
Is this something I need to worry about or just expected behavior? (I generally only look at this log file when there is a problem, and there hasn't beed a problem in a while.)
--
We’re despairing in style, as befits two former High Kings of Fillory.
info: rules: meta test KAM_REALLY_FAKE_DELIVER has dependency 'KAM_RPTR_PASSED' with a zero score
And a lot of compile lines like:
cc -c -DHAS_FPSETMASK -DHAS_FLOATINGPOINT_H -DUSE_THREAD_SAFE_LOCALE -fno-strict-aliasing -pipe -fstack-protector-strong -I/usr/local/include -D_FORTIFY_SOURCE=2 -O2 -pipe -fstack-protector-strong -fno-strict-aliasing -DVERSION=\"1.0\" -DXS_VERSION=\"1.0\" -DPIC -fPIC "-
Basically, I get about 200 lines each day. I am assuming something is wrong in my setup?
Crontab:
19 1 * * * sa-update ; sa-update --gpgkey 24C063D8 --channel kam.sa-channels.mcgrail.com ; sa-compile && service sa-spamd restart
I could redirect sa-compile to null, of course, but having spamd restart only when the compile succeeds seems like a good idea?
Also, I don't remember SA being this noisy? OTOH, I don't keep these cron logs more than a day or two, so maybe they were always this noisy and I didn't notice.
Is this something I need to worry about or just expected behavior? (I generally only look at this log file when there is a problem, and there hasn't beed a problem in a while.)
--
We’re despairing in style, as befits two former High Kings of Fillory.