Comment 6 for bug 1735120

That seems like a plausible solution, although it might be awkward trying to debug and not knowing where in the log file a given panic happened (note that a panic print doesn't necessarily imply a restart - the HTTP handler prints panic stack traces too AFAIR). Another possibility might be to move log rotation out of juju into another program that reads juju's and writes it to the appropriate file, rotating/compressing logs as appropriate.