Comment 2 for bug 1349949

This *might* be a debug setting that Landscape is invoking, if I look at
ps output on all these machines it's like this:

ubuntu@maas-1-04:/var/log/juju$ ps ax | grep juju
 8412 ? Ssl 0:07 /var/lib/juju/tools/machine-0/jujud machine
--data-dir /var/lib/juju --machine-id 0 --debug
10036 ? Ss 0:00 lxc-start --daemon -n juju-machine-0-lxc-0 -c
/var/lib/juju/containers/juju-machine-0-lxc-0/console.log -o
/var/lib/juju/containers/juju-machine-0-lxc-0/container.log -l DEBUG
10258 pts/2 S+ 0:00 grep --color=auto juju
10945 ? Ss 0:00 lxc-start --daemon -n juju-machine-0-lxc-1 -c
/var/lib/juju/containers/juju-machine-0-lxc-1/console.log -o
/var/lib/juju/containers/juju-machine-0-lxc-1/container.log -l DEBUG
11845 ? Ssl 2:25 /var/lib/juju/tools/machine-0-lxc-0/jujud
machine --data-dir /var/lib/juju --machine-id 0/lxc/0 --debug
11926 ? Ss 0:00 lxc-start --daemon -n juju-machine-0-lxc-2 -c
/var/lib/juju/containers/juju-machine-0-lxc-2/console.log -o
/var/lib/juju/containers/juju-machine-0-lxc-2/container.log -l DEBUG
12034 ? Ssl 2:15 /var/lib/juju/tools/unit-glance-0/jujud unit
--data-dir /var/lib/juju --unit-name glance/0 --debug
12541 ? Ssl 2:23 /var/lib/juju/tools/machine-0-lxc-1/jujud
machine --data-dir /var/lib/juju --machine-id 0/lxc/1 --debug

All the --debug's might be causing the traffic. Even so, perhaps we
should steer that to /var/log/juju/db.log rather than syslog? Perhaps
errors would still go to syslog regardless?

Mark