I am using and maintaining (more or less) the program logcheck. When the program is run (e.g. by a cronjob) and the directory /var/run/logcheck is not already present, it creates it. Since the recent update of the filesystem package, the lock directory is symlinked to /run/lock, which is in a temporary mountpoint, so that on every reboot, the directory needs to be re-created. The problem is that the program, running under its own "logcheck" account, does not possess sufficient rights to create a directory in /run/lock.
Any ideas how I should approach this - perhaps even short of rewriting the program in order not to use this subdirectory? (I think in the past, I have manually created the directory once and chowned it to "logcheck" so that the program was using it fine all the time.)
Last edited by awagner (2012-06-14 06:00:56)
Cool. I wasn't aware of this. Just to be sure: This will work even with plain old arch initscripts instead of systemd?
Great! Thanks for the advice (and for the tools of course). I will see to it that I include it in the next release of the logcheck package.