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.
A nice place to discuss rumors, happenings, innovations, and challenges in the technology sphere. We also welcome discussions on the intersections of technology and society. If it’s technological news or discussion of technology, it probably belongs here.
Remember the overriding ethos on Beehaw: Be(e) Nice. Each user you encounter here is a person, and should be treated with kindness (even if they’re wrong, or use a Linux distro you don’t like). Personal attacks will not be tolerated.
Subcommunities on Beehaw:
This community's icon was made by Aaron Schneider, under the CC-BY-NC-SA 4.0 license.
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.
Or use inotifywait from inotify-tools. It logs acces to specified file/folder.
Interesting. I have not heard of this tools. But you say specified file or folder, that means you already know the file location?
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)
This is the way.
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!)
Check out the Lemmy install docs
well, lemmy is a webapp.
Those usually store config in some www/htdocs/config
dir. Lemmy does aswell and offers LEMMY_CONFIG_LOCATION
to override.
I mean, that's sort of what xdg is intended to accomplish, with making $HOME/.config be the place, but it's kind of up to the individual software developers to comply. (Yes, I know, this doesn't really apply to Windows/Mac OS) But yeah, it would really be nice if configs/config locations were even remotely standardized.
There's also $HOME/.local/share for 'static data files' as part of XDG.
which is not config files. ~/.local is just user specific override for /usr
What's imho worse is how often config options or command flags don't actually do at all what's described in the manpage. I then have to dig into the source code once again and since you have to read through the whole behaviour it takes much longer than just looking up where the program tries to read config files.
Please - if you find such wrong docs in Open source software, submit a fix to the doc. It's as important as normal bugfixes.
What I find more frustrating is undocumented environment variables to override config locations.
The amount of times I've had to dig through the source code for a CLI to find an environment variable to force the config somewhere should be zero. But it's not.
I genuinely do not like apps using environment variables for config if they aren't running in their own contained environment. It makes me uncomfortable.
This drives me freaking bonkers. A lot of times libraries tend not to expose the env var to discourage its usage but IF YOU MADE IT IN THE FIRST PLACE YOU HAD A USE CASE FOR IT.
I guess the difficulty here is that sometimes that decision is made by the package manager, not the developer. You'll see Debian distros using a different location compared to a red hat one, while Mac OS is again different, so it might be hard for a developer to tell you where it is.
Still, some kind of universal CLI flag that tells you where the binary/service looks for configuration would be a great idea.
And also: where it found the config file it is actually using at the moment. This would cover the 90% of the cases in which you just want to change a single Key to a different value or something or so...
It would be amazing yeah, standardising all user config files in the $HOME, and maybe etc/ or an default, non usable, user profile to store the original versions, in case of a bad config or corrupted file would save so much time debugging stuff.
Like $XDG_CONFIG_HOME
and $XDG_DATA_HOME
?
GoboLinux kind of solved that problem but it hasn't been updated in years.
take a look at NixOS
Does the nix configuration file contain also the config files of the programs within it?
Mixed. Many folks use home-manager
to configure their user environment with nix
, and you can specify config files there. However, escape hatches to use regular files not managed by nix
exist to make config tweaking faster. You can specify your config file contents in nix
, which works well for server deployments, but for desktop use it usually ends up being a mix of seldom-changed config going in the nix
definitions, and other things that, say, revolve around GUI tools for config tweaking (eg KDE apps) continuing to do their own thing.
I haven't met one person who doesn't use home-manager. Maybe that's because most people I talk to use tiling window managers and stuff like that, where you define everything in text files.
You can see my config at https://github.com/n3oney/nixus.
PC, Laptop and aarch64 server configured in one place with shared components
And even if the program doesn't use config files (like various gnome, xfce and other programs), it should be possible to programmatically export and import full or partial configurations.
With Synaptic, you can show all files associated with a package. That includes config files. Saved me a lot of hassle on numerous occasions.
Yeah anything installed via a package manager, like an rpm or deb package, you can query to see what files belong to that package. Problem is they often have default config file locations, like in your home dir, where they will not ship and install files. (Though they might create them as part of a post install process)
read the man page
The good ol' RTFM
For real. Usually the config file locations is at the bottom, so jumping to it is quick.
this is not really what the article is about.
yes you can read man page, you can find there all possible locations of config files. yet you still don't know where config file is stored. you have to check all the possible locations.
also if there would be some standard so you can query app for its config files, you could make automated backups easily. at least much easier that now.
of course I understand this is completely unrealistic, in software world everyone will do whatever they want..
If it's not in /etc it should be in the directory the exe file is located.
~/.config
is the non-root version of /etc
these days. But you just have to know that, which isn't ideal.
If you are a developer, please take a look at the XDG Base Directory Specification and try to follow it, users will be very grateful.
Short summary:
Look for $XDG_CONFIG_HOME
for configs and $XDG_STATE_HOME
for state. If they aren't available, use the defaults (./config
and .local/share
).
But what about .local/, or .appname/? It's just a mess
~/.local
is the non-root version of /usr
. By .appname
do you just mean a folder that a specific app made in your home for itself? Yeah, I never condone that. imo that's just a badly behaving app. It should move that folder into ~/.config
.
Configuration for root
is in /root/
, that is, root
's home directory. /etc
is for system configuration, different thing.
Certainly not. Nothing should write to /usr/bin except for the package manager in FHS distros and some distros binary directories aren't writable at all.
Well good because a program shouldn’t be writing to its config file either.
@wet_lettuce
Should be /etc or /usr/local/etc or /opt/etc or /opt/vendor/product/etc or ~/etc.
With some exceptions for historic compatibility (like ~/.bashrc)
The man page should specify where.
The exceptions should only apply for cases where XDG is not available. In any other case, the appropriate XDG directoy configured by the user should be used first.
For user-specific config files, aren't they all supposed to be in ~/.config
these days? I've never heard of software using ~/etc
.
Seriously, I've lost so muuuuch time just trying to find where some random program decides to store its config files. It sometimes takes me more time than actually "doing the config"
Fortunately half of apps use dconf nowadays
It puts it's Configs in /etc/ or it gets the hose again.
I think this is a drawback of not having more specialized communities in beehaw yet - I'm not sure if this advice is very niche advice or if it has some value in general awareness for the layperson?
Normally I'd look up and see "r/DevChat" or some such distinct community name and have immediate context of, "that's not really for you to figure out". But this is essentially "r/technology" so I'm left wondering if I personally can take anything of value from this post.
Not a criticism or complaint, just an observation.
obligitory windows user here to say that not only should every program should tell you where they are, but should also use them, or have a way to import configs via the command line. very frustrating to discover powershell automation is impossible for a program because ~~i am too lazy/stupid to figure out how to automate the gui~~ it doesn't have any way to modify configs without navigating the gui, cough cough winaero tweaker but this is only because i am an windows user, and i stubbornly refuse to learn how to use linux until absolutely necessary.