One of my F9 machines -- actually my #1 main machine -- started having display problems. I see this a lot, because my hardware isn't really up to date enough to handle my monitor optimally. So I tried a couple of tricks that usually help, and they didn't. Then I thought to run baobab. Lo and behold, I was running out of space -- because /var/log shows up consuming 54 GB of space! Yes, fifty- four gigs. What could be causing this, and what do i do about it?? At present, the machine offers only a CLI login; if I use is as root, startx still works; but if I log in as user, startx fails. So I can't run Pan, and can't c&p directly between anything in it (including this list!) and the CLI. I can still do what I'm doing now: access the list via Pan on another machine, and go back & forth with my KVM switch; but it makes it hard, for instance, to post things like a list of contents for /var/log, or any whole file in it. Obviously, I want to cut /var/log with electronic double-bitted axes in both hands, to get to my user's GUI again; and to find the source of the bloat and correct it. What should I do first?? -- Beartooth Staffwright, PhD, Neo-Redneck Linux Convert Remember I know precious little of what I am talking about. -- fedora-list mailing list fedora-list@xxxxxxxxxx To unsubscribe: https://www.redhat.com/mailman/listinfo/fedora-list Guidelines: http://fedoraproject.org/wiki/Communicate/MailingListGuidelines
