I wholeheartedly agree with this blog post. I believe someone on here yesterday was asking about config file locations and setting them manually. This is in the same vein. I can’t tell you how many times a command line method for discovering the location of a config file would have saved me 30 minutes of googling.

  • KIM_JONG_JUICEBOX@beehaw.orgEnglish
    41·
    1 year ago

    Start your application / program with “strace” and see all the files it opens.

    Also run “lsof” on a running process to see what files it has open.

      • KIM_JONG_JUICEBOX@beehaw.orgEnglish
        5·
        1 year ago

        Interesting. I have not heard of this tools. But you say specified file or folder, that means you already know the file location?

        • Leirda@lemm.eeEnglish
          2·
          1 year ago

          You can call it recursively on .config (for instance), and watch for specific events (creation, deletion, modification, etc). But I expect this to be expensive on really large folders and I’d avoid it if I could.

          Btw it’s syscalls iirc (inotify-tools just exposes them)

    • heeplr@feddit.deEnglish
      3·
      1 year ago

      I doubt that’s a linux problem. All apps store config in /etc, ~/.*rc or ~/.config

      Everything else should be considered a bug (looking at you, systemd!)