Page 2 of 4 FirstFirst 1234 LastLast
Results 11 to 20 of 34

Thread: Disk Usage Analyzer - Need help understanding result

  1. #11
    Join Date
    Dec 2014
    Beans
    2,641

    Re: Disk Usage Analyzer - Need help understanding result

    Without 'sudo' it couldn't access some things which only root has access to, but otherwise found nothing changed within the given time frame. With sudo it could access those places and still found nothing. So whatever happened didn't happen while you were away. I'd try again (several times) but leave out ~/.cache and ~/.mozilla (those directories are full of stuff that changes all the time) and decrease the '+180' part and increase the '-720' to see what was changed. BTW the '+' and '-' in those time values is important; the '+' means 'more than' and the '-' means 'less than'. If you give a time without either, find will look for files changed exactly that many minutes ago.

    Holger

  2. #12
    Join Date
    Jul 2005
    Location
    I think I'm here! Maybe?
    Beans
    Hidden!
    Distro
    Xubuntu 24.04 Noble Numbat

    Re: Disk Usage Analyzer - Need help understanding result

    Something very strange going on there!

    When I run that command I see nothing listed which is much as expected.

  3. #13
    Join Date
    Mar 2019
    Beans
    215

    Re: Disk Usage Analyzer - Need help understanding result

    Quote Originally Posted by Holger_Gehrke View Post
    Without 'sudo' it couldn't access some things which only root has access to, but otherwise found nothing changed within the given time frame. With sudo it could access those places and still found nothing. So whatever happened didn't happen while you were away. I'd try again (several times) but leave out ~/.cache and ~/.mozilla (those directories are full of stuff that changes all the time) and decrease the '+180' part and increase the '-720' to see what was changed. BTW the '+' and '-' in those time values is important; the '+' means 'more than' and the '-' means 'less than'. If you give a time without either, find will look for files changed exactly that many minutes ago.

    Holger


    OK.

    Thanks for the tip.


    And what about the last post, where I got more than 4,000 code lines in response?

  4. #14
    Join Date
    Mar 2019
    Beans
    215

    Re: Disk Usage Analyzer - Need help understanding result

    Quote Originally Posted by ajgreeny View Post
    Something very strange going on there!

    When I run that command I see nothing listed which is much as expected.
    Is this addressed to me or to Holger?

    And what command are you referring to?

  5. #15
    Join Date
    Dec 2014
    Beans
    2,641

    Re: Disk Usage Analyzer - Need help understanding result

    Quote Originally Posted by bhubunt View Post
    When I posted the following code, which, I take it, was a search to see what had been changed in the last 24 hours

    Code:
     find /usr -mtime -1
    I got an enormous list in return, 4865 code lines, a list so long, I had to put it in pastebin

    https://pastebin.com/aHLAsEUj
    That's just the latest kernel update, specifically the modules and the includes. Look at the last few items in /var/log/apt/history.log. The files themselves get the modification time from the tar-file inside the deb-package, but the directories get modified during the update and show up in your search results.

    Holger

  6. #16
    Join Date
    Jul 2005
    Location
    I think I'm here! Maybe?
    Beans
    Hidden!
    Distro
    Xubuntu 24.04 Noble Numbat

    Re: Disk Usage Analyzer - Need help understanding result

    Quote Originally Posted by bhubunt View Post
    Is this addressed to me or to Holger?

    And what command are you referring to?
    It was an answer to you about the command find /usr -mtime -1

  7. #17
    Join Date
    Mar 2019
    Beans
    215

    Re: Disk Usage Analyzer - Need help understanding result

    Quote Originally Posted by Holger_Gehrke View Post
    Look at the last few items in /var/log/apt/history.log. The files themselves get the modification time from the tar-file inside the deb-package, but the directories get modified during the update and show up in your search results.

    Holger

    OK -- so this is what I got without sudo

    Code:
     bash: /var/log/apt/history.log: Permission denied
    Last edited by bhubunt; June 18th, 2023 at 10:29 PM.

  8. #18
    Join Date
    Aug 2016
    Location
    Wandering
    Beans
    Hidden!
    Distro
    Xubuntu Development Release

    Re: Disk Usage Analyzer - Need help understanding result

    Try "cat" and not bash
    Code:
    cat /var/log/apt/history.log
    With realization of one's own potential and self-confidence in one's ability, one can build a better world.
    Dalai Lama>>
    Code Tags | System-info | Forum Guide lines | Arch Linux, Debian Unstable, FreeBSD

  9. #19
    Join Date
    Mar 2019
    Beans
    215

    Re: Disk Usage Analyzer - Need help understanding result

    Holger, I did get a syslog through the gedit command but there is something wrong with it. I am attaching a screenshot, as there are more than 12,000 code lines. Perhaps you could look at the screenshot to assess what is wrong with the syslog?
    Attached Images Attached Images

  10. #20
    Join Date
    Dec 2014
    Beans
    2,641

    Re: Disk Usage Analyzer - Need help understanding result

    For looking at log files use 'less' (it's an enhanced replacement for an older pager named 'more' - 'less is more than more'). You can freely move through a file, search it, mark places in the file and return to them later and it can open multiple files at once and switch between them. You can even start an editor from 'less' to change files if you spot an error.

    And I don't see anything catastrophically wrong in that syslog screenshot. Looks like networkd-dispatcher is loosing it's mind about the loopback interface (which it really shouldn't bother with, it's for your machine talking to itself ...) and 'enp0s25' (probably a wired ethernet connection which isn't plugged in). Nothing to see here, except for gedit throwing a fit at not being able to automatically deduce the encoding of the file. Might be a bit of binary in there somewhere from a misbehaving program or some terminal control sequences. 12000 lines isn't especially much, considering that the first second after boot already produces more than 1500 lines ...

    Holger

Page 2 of 4 FirstFirst 1234 LastLast

Tags for this Thread

Bookmarks

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •