This bug is about GDM breaking when a user remove system directories that they should never remove. Importance Critical would be ridiculous, I actually think even Medium is too much.
It is an incorrect assumption that it is OK to "tidy up" by running "rm -rf /var/log/*". Doing that is never correct, AFAIK /var/cache is the only directory under /var where the FHS say you may remove anything at any time. There is probably many other programs that can't recreate their own log directory, especially programs running as non-root. Only root can write to /var/log, so giving write permissions for other system uid/gid is often the reason that an application have a separate directory under /var/log. (SSD) Users that like to put /var/log on tmpfs will need to sync files to/from it at boot/shutdown, just as if they put any other system directory on tmpfs. If there are guides/howtos suggesting to mount an empty tmpfs on /var/log at boot then those guides needs to be fixed. Here are the relevant parts of FHS[1] and Debian Policy[2]: [1] http://www.debian.org/doc/packaging-manuals/fhs/fhs-2.3.html#THEVARHIERARCHY [2] http://www.debian.org/doc/debian-policy/ch-files.html -- gdm fails to start if /var/log/gdm does not exist https://bugs.launchpad.net/bugs/405227 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
