Hide Forgot
Description of problem: # rpm -ql dracut | grep dracut.log /var/log/dracut.log # ls -l /var/log/dracut.log ls: cannot access /var/log/dracut.log: No such file or directory Version-Release number of selected component (if applicable): dracut-004-38.el6.noarch How reproducible: Always As a result dracut will not write its log to this file because it doesn't exist. If root does `touch /var/log/dracut.log' then dracut successfully writes to this file. Also related to bug #676018.
While trying to test bug #676018. Harald instructed me to create $HOME/dracut.log before testing. dracut should automatically create its log files if they are not present: /var/log/dracut.log and $HOME/dracut.log if invoked with -l.
Reproduced on RHEL6.0 GA x86_64 Server. Verified on RHEL6.1-20110330.2 x86_64 Server. dracut-004-46.el6.noarch
An advisory has been issued which should help the problem described in this bug report. This report is therefore being closed with a resolution of ERRATA. For more information on therefore solution and/or where to find the updated files, please follow the link below. You may reopen this bug report if the solution does not work for you. http://rhn.redhat.com/errata/RHBA-2011-0523.html