804
All programs should tell you where they store config files (utcc.utoronto.ca)
submitted 3 years ago by to c/technology@beehaw.org
99 comments fedilink hide all child comments
 

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.

you are viewing a single comment's thread
view the rest of the comments
[–] 3 points 3 years ago (8 children)

The *nix equivalent is the lsof command. This doesn't help you finding out in which hierarchy config files are parsed when the program accesses multiple ones, which is often the case.

  • permalink
  • fedilink
  • source
  • parent
  • hideshow 8 child comments
    •
  • [–] 7 points 3 years ago (7 children)

    You can use something like strace -eopen -f -o strace.out the_program to find all files that the program tried or succeeded to open. Then you can try to find the config file(s) in strace.out.

  • permalink
  • fedilink
  • source
  • parent
  • hideshow 7 child comments
    •
  • [–] 2 points 3 years ago (4 children)

    You still don't know which location is preffered and how get they get merged. In my experience, digging into the source is the most straighforward. But my usual problem is more that the config option doesn't do at all what the documentation says it does.

  • permalink
  • fedilink
  • source
  • parent
  • hideshow 4 child comments
    •
  • [–] 1 point 3 years ago* (3 children)

    Wouldn't the strace.out file be in chronological order?

  • permalink
  • fedilink
  • source
  • parent
  • hideshow 3 child comments
    •
  • [–] 1 point 3 years ago (2 children)

    Yes, though if two different files allow for the same config key - you're stuck opening both to check

  • permalink
  • fedilink
  • source
  • parent
  • hideshow 2 child comments
    •