[2.0b4] external maas-rack-controller logs to syslog instead of maas.log

Connected an external rack controller, but it didn't log import of images:

ubuntu@maas-rack2:~⟫ tail -f /var/log/maas/*.log
==> /var/log/maas/maas.log <==

==> /var/log/maas/rackd.log <==
2016-05-03 22:41:04+0000 [Uninitialized] ClusterClient connection established (HOST:IPv4Address(TCP, '192.168.10.2', 38426) PEER:IPv4Address(TCP, '192.168.10.27', 5250))
2016-05-03 22:41:04+0000 [Uninitialized] ClusterClient connection established (HOST:IPv4Address(TCP, '192.168.10.2', 40226) PEER:IPv4Address(TCP, '192.168.20.104', 5253))
2016-05-03 22:41:05+0000 [ClusterClient,client] Event-loop 'trusty-maas9:pid=6142' authenticated.
2016-05-03 22:41:05+0000 [ClusterClient,client] Event-loop 'trusty-maas9:pid=6144' authenticated.
2016-05-03 22:41:05+0000 [ClusterClient,client] Rack controller '4y3ha6' registered (via trusty-maas9:pid=6142).
2016-05-03 22:41:05+0000 [ClusterClient,client] Rack controller '4y3ha6' registered (via trusty-maas9:pid=6144).
2016-05-03 22:41:34+0000 [-] Event-loop trusty-maas9:pid=6139 (10.216.160.107:5252): User timeout caused connection failure.
2016-05-03 22:41:35+0000 [Uninitialized] ClusterClient connection established (HOST:IPv4Address(TCP, '192.168.10.2', 33936) PEER:IPv4Address(TCP, '192.168.20.104', 5252))
2016-05-03 22:41:35+0000 [ClusterClient,client] Event-loop 'trusty-maas9:pid=6139' authenticated.
2016-05-03 22:41:35+0000 [ClusterClient,client] Rack controller '4y3ha6' registered (via trusty-maas9:pid=6139).