On Tue, 25 Nov 2008 20:30:07 +0100
"Sandro Tosi" <[EMAIL PROTECTED]> wrote:

> Hello Patrick,
> all your conversation went unnoticed to be due to use of -quite and
> -submitter, so only now I see your patch.
> 
> On Tue, Nov 25, 2008 at 20:04, Patrick Matthäi
> <[EMAIL PROTECTED]> wrote:
> >> I have noexec on /tmp and /var/tmp, but AFAIK that is not suposed
> >> to break anything policy-wise.
> 
> mh, even if I still don't understand how --oknodo fix the problem, I
> may think to add it.
> 
> > noexec breaks for example debconf in some situations.
> 
> So, aren't we working around a problem on the user system? I think
> many uses noexec on some partitions, so that's weird what's happening
> only on the user's system and not on all the other box.

How many use the package according to popcon?  Maybe no one else
notice / reported the problem.  I know I have tried to explain what
start-stop-daemon needs in another bug report, because that seems to
the source of the problem.  Perhaps another read through of the
start-stop-daemon manpage (which is quite helpful), and remember that
gkrellm is the one that should be creating the pidfile through the
equivalent of gkrellm --pidfile (IIRC you need --pidfile twice in the
start script, once for start-stop-daemon and once after the -- for
gkrellm, but I could be misremembering that; the actually commandline
needed is in the bug report).

Regards,

Daniel

-- 
And that's my crabbing done for the day.  Got it out of the way early, 
now I have the rest of the afternoon to sniff fragrant tea-roses or 
strangle cute bunnies or something.   -- Michael Devore
GnuPG Key Fingerprint 86 F5 81 A5 D4 2E 1F 1C      http://gnupg.org
The C Shore: http://www.wightman.ca/~cshore

Attachment: signature.asc
Description: PGP signature

Reply via email to