On 15 July 2010 10:18, Frank Murphy <frankly3d@xxxxxxxxx> wrote: > Quite a lot of kvm\qemu, being doing a lot of testing. OK. There are two options here depending on whether or not the KVM/Qemu stuff is useful to you in your testing. If it is, then the best option is probably going to be to try and pull the KVM/Qemu stuff out of the main "/var/log/messages" file and put it into a dedicated log file. Once you've done that you could also use Logrotate to set a more appropriate retention policy on those files such as rotating daily and discarding the log files after a week, for instance. If you don't need the entries then the best option would be to try and prevent them from getting them logged in the first place, either via the configuration files of KVM/Qemu or by increasing the necessary severity of a KVM/Qemu message before RSyslog writes it to the file. That might be a bit tricky though because KVM is closely integrated with the kernel and probably just logs messages as "kernel", so changes may impact *all* kernel logging, which could result in other, more useful, kernel messages not getting logged. Unfortunately I can't be more specific than that at the moment. I don't use either KVM or Qemu so I don't have any information on the specific configuration options available or what you might need to change in "/etc/rsyslog.conf" to tune the logging, but I suspect KVM will log as "kernel". If you can post a few samples then I'll probably be able to at least point you in the right direction. -- Andy The only person to have all his work done by Friday was Robinson Crusoe -- users mailing list users@xxxxxxxxxxxxxxxxxxxxxxx To unsubscribe or change subscription options: https://admin.fedoraproject.org/mailman/listinfo/users Guidelines: http://fedoraproject.org/wiki/Mailing_list_guidelines
