tags 637209 +moreinfo thanks On Tue, Aug 09, 2011 at 02:26:10PM +0100, sentimental.br...@gmail.com wrote: > Flaws with installation: > > 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.) > 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. > Solutions: > > Correct permissions: > > chown -r debian-sks:root /var/log/sks/* According to postinst the original permission for /var/log/sks should be debian-sks:adm 2750. Does this represent the state of your system? Since sks is started as debian-sks the owner for new files inside that directory should be debian-sks. Also since the directory is setgid adm, the group of contained files should be adm as well. Has this been the case prior to invoking your "solution"? If yes, why do you believe that the group should be root instead of adm? > Add correct path for debial-sks account: > > cat <<END >> /etc/profile.d/sks > if [ "`id -un`" == "debian-sks" ]; then > PATH="/usr/sbin:$PATH" > fi > export PATH > END >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. Helmut -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
