On Mon, 12 Dec 2011 11:51:36 +0100, Helmut Grohne <hel...@subdivi.de> wrote: > > Incorrect ownership of /var/log/sks/db.log > > Please always state precisely what is wrong. Otherwise a maintainer can > only guess what might be wrong. (See below for my guess.)
Freshly installed system, no log output generated, or server fails to start. > > sks executable located in /usr/sbin/sks > > So where is the "flaw" with putting a daemon in /usr/sbin? I would call > that complying with FHS. Not on the path, the init script fails. Silently. Nothing starts up. My understanding is that /usr/sbin is only added to root's path. Regular, non-root programs will not have it added to their path. > > Solutions: > > > > Correct permissions: > > > > chown -r debian-sks:root /var/log/sks/* > ls -la /var/log/sks/db.log -rw------- 1 debian-sks root 516 Dec 12 12:05 /var/log/sks/db.log > From your "solution" I can guess that the some script tries to invoke > sks as user debian-sks without specifying its full path. However I was > unable to find a matching invocation. For instance build_sks.sh is > patched to use absolute paths. This bug was submitted several months ago. I lost a bunch of docs, about a month later. All I now know - is that sks or one of it's helpers (on a fresh install) fails without that path, that the failure was silent, and that it took me 2 days to figure out the problem, which was why I submitted (my naive) fixes. -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
