maas.log is created by syslog. Obviously, if it is deleted it won;t come
back automatically because mAAS does not control it. Marking this bug
invalid.
** Changed in: maas
Status: New => Invalid
** Changed in: maas (Ubuntu)
Status: New => Invalid
--
You received this bug notificat
** Also affects: maas
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to maas in Ubuntu.
https://bugs.launchpad.net/bugs/1350270
Title:
/var/log/maas/maas.log doesn't come back if deleted
To
Just a note for whoever looks at this. Changing ownership/permissions on
the directory would certainly fix this, but would it affect anything
else (eg. other files in the directory)? Letting www-data write would
also allow anything running under Apache to delete files from there too;
is this a prob
Robie, the problem is that the logging depends on the packaging to have
touched + chowned + chmodded the empty file beforehand. Ideally it
would just set write permissions for www-data on the parent directory.
--
You received this bug notification because you are a member of Ubuntu
Server Team,
Apache should have write permissions so that it can rewrite the file.
On Wed, Jul 30, 2014 at 11:48 AM, Robie Basak <1350...@bugs.launchpad.net>
wrote:
> I'm assuming the file was deleted by accident, rather than by some other
> problem?
>
> I'm not sure if this is a bug. Traditionally when user
I'm assuming the file was deleted by accident, rather than by some other
problem?
I'm not sure if this is a bug. Traditionally when users rearrange
things, packaging is supposed to get out of the way. Here, packaging
doesn't know if you've intentionally moved the file elsewhere.
OTOH, it would be