On Mon, 25 Apr 2022 15:12:17 +0200 Henrik Christian Grove <deb...@3001.dk> wrote: > > Instead of wasting time configuring and running a location service, I > just had a number of slightly different configuration files for redshift > (with different manual locations specified) and would just let > `.config/redshift.conf` be a symlink to the one corresponding to my > current location. (And do some extra work in new locations) > > That didn't work with the discussed restriction (but I could easily put > all the different configs in `.config/redshift/`. > > For now my workaround was simply to replace the symlink with a copy. >
I'm having a similar problem, because my redshift config file is in version control, and ~/.config/redshift.conf is a symlink to the version controlled file. I changed it to a hardlink, which allows redshift to read the config file, but this is not a robust solution. I don't know anything about apparmor, but is there some hope that the config could be changed to follow symlinks? Or perhaps that "defeats the purpose" of apparmor?
