Remove spurious log messages to container terminal

Issue #62 resolved
Jan Blechta created an issue

When run

docker pull quay.io/fenicsproject/stable:2017.1.0
docker run -ti --rm quay.io/fenicsproject/stable:2017.1.0

and kept up for a while one can see messages coming from container guts:

fenics@be3e93eb8574:~/demo/undocumented/dg-advection-diffusion/python$ May 14 06:47:01 be3e93eb8574 CRON[1378]: (root) CMD (test -x /usr/sbin/anacron || ( cd / && run-parts --report /etc/cron.weekly ))
May 14 07:17:01 be3e93eb8574 CRON[1385]: (root) CMD (   cd / && run-parts --report /etc/cron.hourly)
May 14 08:17:01 be3e93eb8574 CRON[1388]: (root) CMD (   cd / && run-parts --report /etc/cron.hourly)
May 14 09:17:01 be3e93eb8574 CRON[1391]: (root) CMD (   cd / && run-parts --report /etc/cron.hourly)
May 14 10:17:01 be3e93eb8574 CRON[1394]: (root) CMD (   cd / && run-parts --report /etc/cron.hourly)
May 14 11:17:01 be3e93eb8574 CRON[1397]: (root) CMD (   cd / && run-parts --report /etc/cron.hourly)
May 14 12:17:01 be3e93eb8574 CRON[1400]: (root) CMD (   cd / && run-parts --report /etc/cron.hourly)
May 14 13:17:01 be3e93eb8574 CRON[1403]: (root) CMD (   cd / && run-parts --report /etc/cron.hourly)
May 14 14:17:01 be3e93eb8574 CRON[1406]: (root) CMD (   cd / && run-parts --report /etc/cron.hourly)
May 14 15:17:01 be3e93eb8574 CRON[1409]: (root) CMD (   cd / && run-parts --report /etc/cron.hourly)
May 14 16:17:01 be3e93eb8574 CRON[1412]: (root) CMD (   cd / && run-parts --report /etc/cron.hourly)
May 14 17:17:01 be3e93eb8574 CRON[1415]: (root) CMD (   cd / && run-parts --report /etc/cron.hourly)
May 14 18:17:01 be3e93eb8574 CRON[1418]: (root) CMD (   cd / && run-parts --report /etc/cron.hourly)
May 14 19:17:01 be3e93eb8574 CRON[1421]: (root) CMD (   cd / && run-parts --report /etc/cron.hourly)
May 14 20:17:01 be3e93eb8574 CRON[1424]: (root) CMD (   cd / && run-parts --report /etc/cron.hourly)
May 14 21:17:01 be3e93eb8574 CRON[1427]: (root) CMD (   cd / && run-parts --report /etc/cron.hourly)
May 14 22:17:01 be3e93eb8574 CRON[1430]: (root) CMD (   cd / && run-parts --report /etc/cron.hourly)
May 14 23:17:01 be3e93eb8574 CRON[1433]: (root) CMD (   cd / && run-parts --report /etc/cron.hourly)
May 15 00:17:01 be3e93eb8574 CRON[1436]: (root) CMD (   cd / && run-parts --report /etc/cron.hourly)
May 15 01:17:01 be3e93eb8574 CRON[1439]: (root) CMD (   cd / && run-parts --report /etc/cron.hourly)
May 15 02:17:01 be3e93eb8574 CRON[1442]: (root) CMD (   cd / && run-parts --report /etc/cron.hourly)
May 15 03:17:01 be3e93eb8574 CRON[1445]: (root) CMD (   cd / && run-parts --report /etc/cron.hourly)
May 15 04:17:01 be3e93eb8574 CRON[1448]: (root) CMD (   cd / && run-parts --report /etc/cron.hourly)
May 15 05:17:01 be3e93eb8574 CRON[1451]: (root) CMD (   cd / && run-parts --report /etc/cron.hourly)
May 15 06:17:01 be3e93eb8574 CRON[1454]: (root) CMD (   cd / && run-parts --report /etc/cron.hourly)
May 15 06:25:01 be3e93eb8574 CRON[1457]: (root) CMD (test -x /usr/sbin/anacron || ( cd / && run-parts --report /etc/cron.daily ))
May 15 06:43:15 be3e93eb8574 syslog-ng[21]: Configuration reload request received, reloading configuration;
May 15 07:17:01 be3e93eb8574 CRON[1536]: (root) CMD (   cd / && run-parts --report /etc/cron.hourly)
May 15 08:17:01 be3e93eb8574 CRON[1539]: (root) CMD (   cd / && run-parts --report /etc/cron.hourly)
May 15 09:17:01 be3e93eb8574 CRON[1542]: (root) CMD (   cd / && run-parts --report /etc/cron.hourly)
May 15 10:17:01 be3e93eb8574 CRON[1545]: (root) CMD (   cd / && run-parts --report /etc/cron.hourly)
May 15 11:17:01 be3e93eb8574 CRON[1548]: (root) CMD (   cd / && run-parts --report /etc/cron.hourly)

fenics@be3e93eb8574:~/demo/undocumented/dg-advection-diffusion/python$ exit
ok: down: /etc/service/cron: 0s, normally up
ok: down: /etc/service/sshd: 262351s
ok: down: /etc/service/syslog-forwarder: 0s
ok: down: /etc/service/syslog-ng: 0s, normally up

Those might not be wanted.

Comments (2)

  1. Log in to comment