clone 637209 -1 retitle -1 /etc/init.d/sks redirects error messages from sks to /dev/null severity -1 wishlist submitter -1 ! tags -1 - moreinfo summary -1 0 thanks
Thanks for your quick reply. On Mon, Dec 12, 2011 at 12:47:12PM +0000, Bryan Hunt wrote: > 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. The daemon does not start by default: | Starting sks daemons: Not starting sks (as configured in /etc/default/sks) However if you enable it in /etc/default/sks and have it badly configured, it will write its error messages to /dev/null. This is because it is started using start-stop-daemon --background. > 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. The init script starts $DAEMON which is an absolute path. So $PATH is not even used here. > > > 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 This likely is due to your chown command. The original permission on a freshly installed sks are 600 debian-sks adm. > 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. Unfortunately you have only presented workarounds for yet unknown problems so far. The only real problem I could discover from your mails is that the init script hides the error messages and exit code returned from sks. I have cloned this issued (see above). Maybe you can try to reproduce the issues you ran into and document all the steps? Otherwise I see little value in adding your solutions to the package. To me the chown seems just wrong and I fail to see which aspect th $PATH change improves. Helmut -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
