On Mon, Nov 10, 2008 at 11:59, Thomas Smith <[EMAIL PROTECTED]> wrote: > Hi Jerrad, > > Not all programs are SELinux-aware and so can muck things up a bit > sometimes. When this happens, the best thing to do is to relabel the > filesystem. To do this, execute the following commands: > > touch /.autorelabel > reboot
I'll look into that. > Keep in mind that the reboot may take a while. > > If you want to see which files have an incorrect label (according to the > SELinux' policy), you can run this command: > > restorecon -n -R -v / Already did that on both the problem file (/dev/log) and recursed the fs (there are a lot of unlabeled files). For now, I've somewhat side-stepped the issue and am logging to a file. Not wonderful though, especially since Log::Dispatch doesn't seem to have support for 'none' so if RT emits and emergency message, it won't get through to syslog... -- Cambridge Energy Alliance: Save money. Save the planet. _______________________________________________ http://lists.bestpractical.com/cgi-bin/mailman/listinfo/rt-users Community help: http://wiki.bestpractical.com Commercial support: [EMAIL PROTECTED] Discover RT's hidden secrets with RT Essentials from O'Reilly Media. Buy a copy at http://rtbook.bestpractical.com
