With the probable exception of maas.log, all logs messages are also
stored by journald. We should simply *stop* logging to regiond.log and
rackd.log. Leave a message in rackd.log and regiond.log like so:
Use `journalctl -u maas-rackd.service` to view the rack logs.
or:
Use `journalctl -u maas-regiond*.service` to view the region logs.
This would mean we're not logging the bulk of MAAS's output _twice_ and
make it reasonable to keep more history of maas.log around.
FWIW, this has been the situation for *years*. Every time I mention it
the silence is deafening. What's blocking us from just doing this?
With the probable exception of maas.log, all logs messages are also
stored by journald. We should simply *stop* logging to regiond.log and
rackd.log. Leave a message in rackd.log and regiond.log like so:
Use `journalctl -u maas-rackd.service` to view the rack logs.
or:
Use `journalctl -u maas-regiond* .service` to view the region logs.
This would mean we're not logging the bulk of MAAS's output _twice_ and
make it reasonable to keep more history of maas.log around.
FWIW, this has been the situation for *years*. Every time I mention it
the silence is deafening. What's blocking us from just doing this?