• taladar@sh.itjust.works
    link
    fedilink
    English
    arrow-up
    2
    arrow-down
    16
    ·
    2 years ago

    It solves virtually none of them, it is pretty good at destroying all the evidence needed to actually fix the problem for good though.

    • qprimed@lemmy.ml
      link
      fedilink
      English
      arrow-up
      5
      ·
      2 years ago

      we are not talking about backend systems here.

      we are talking about user devices in the wild, likely in an unknown state, with highly variable usage patterns by the user. someone with experience can usually determine how deeply to poke based on 30 seconds of questioning the user.

      “reboot” is absolutely valid when the issue is trivial, non-recurring and the equipment is not sensitive. if a reboot destroys logs then the device was not important to you to begin with.