Re: too-nearly-full filesystem '/'. (was upgrade problem: space on '/' filesystem.)

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



On 10/18/19 11:42 AM, home user wrote:
(Ed and Samuel)
> As noted by Samuel, I too don't have that directory.
> Just delete it.
ok.  But let's not do "half a job".
There must be something more fundamental going on here.  I never knowingly or willfully did anything to create "/var/cache/abrt-di/usr/" or anything under it, or configure where crash data goes.  And surely, we all experience crashes.  Yet there is this basic difference between my system and yours.  Is this
- a side effect of something I did?  If yes, what?
or
- something I did not do, or a side effect of something I did not do?  If yes, what?
Or are you are doing something to automatically remove that directory and/or its contents?
Removing that directory is a short-term fix.  We all experience crashes.  I get the impression that that directory will come back with new contents.

The directory "/var/cache/abrt-di is created by the abrt-addon-ccpp.

How/what/when the sub-directories are created I don't recall.  And, I'm not that curious to take the time to
research it.

However, those directories only contain information used for debug purposes.  They may be related to
automatically reporting bugs.  So, the stuff in there is of no value at this point.  I wouldn't delete the directory but all the contents below it.

You can check back in a month or so to see if new stuff has been placed there.


(Ed)
Your idea regarding /home is interesting.  I'll come back to that later.  (Please remind me if I tag the thread solved without doing that!)

I suggest you make a note of it.  I'm only responsible for reminding my cats not to wake me at 3AM.
They ignore my request.  :-)

--
The key to getting good answers is to ask good questions.
_______________________________________________
users mailing list -- users@xxxxxxxxxxxxxxxxxxxxxxx
To unsubscribe send an email to users-leave@xxxxxxxxxxxxxxxxxxxxxxx
Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: https://lists.fedoraproject.org/archives/list/users@xxxxxxxxxxxxxxxxxxxxxxx



[Index of Archives]     [Older Fedora Users]     [Fedora Announce]     [Fedora Package Announce]     [EPEL Announce]     [EPEL Devel]     [Fedora Magazine]     [Fedora Summer Coding]     [Fedora Laptop]     [Fedora Cloud]     [Fedora Advisory Board]     [Fedora Education]     [Fedora Security]     [Fedora Scitech]     [Fedora Robotics]     [Fedora Infrastructure]     [Fedora Websites]     [Anaconda Devel]     [Fedora Devel Java]     [Fedora Desktop]     [Fedora Fonts]     [Fedora Marketing]     [Fedora Management Tools]     [Fedora Mentors]     [Fedora Package Review]     [Fedora R Devel]     [Fedora PHP Devel]     [Kickstart]     [Fedora Music]     [Fedora Packaging]     [Fedora SELinux]     [Fedora Legal]     [Fedora Kernel]     [Fedora OCaml]     [Coolkey]     [Virtualization Tools]     [ET Management Tools]     [Yum Users]     [Yosemite News]     [Gnome Users]     [KDE Users]     [Fedora Art]     [Fedora Docs]     [Fedora Sparc]     [Libvirt Users]     [Fedora ARM]

  Powered by Linux