Hi!
On Wed, 2014-10-15 at 12:53:05 +0200, Christoph Martin wrote:
> Am 13.10.2014 um 20:28 schrieb Guillem Jover:
> > This is certainly a regression in s-s-d. It does still create a pidfile
> > when using --background. I do have to wonder why the init script is not
> > using --background though, b
Am 13.10.2014 um 20:28 schrieb Guillem Jover:
>
> This is certainly a regression in s-s-d. It does still create a pidfile
> when using --background. I do have to wonder why the init script is not
> using --background though, because otherwise any error from it will not
> be noticed at all by the
On Mon, 2014-10-13 at 20:28 +0200, Guillem Jover wrote:
> No, it does not. This is certainly about related software, as the
> package is using s-s-d explicitly. This is not what critical is for,
> please do not escalate bug severities.
Sorry,... guess I took the definition too broad in the sense o
Control: sevrity -1 serious
Control: retitle -1 s-s-d: Does not create a pidfile w/o --background
[ CCing the SKS maintainers. ]
On Mon, 2014-10-13 at 19:21:57 +0200, Christoph Anton Mitterer wrote:
> Package: dpkg
> Version: 1.17.18
> Severity: critical
> Justification: breaks unrelated software
found 765110 1.17.16
stop
seems to happen already at least in 1.17.16.
smime.p7s
Description: S/MIME cryptographic signature
Package: dpkg
Version: 1.17.18
Severity: critical
Justification: breaks unrelated software
Hi.
It seems that start-stop-daemon no longer creates a PID file, at least when
called like this:
start-stop-daemon --start --oknodo --chuid debian-sks:debian-sks --make-pidfile
--pidfile $SKSDBPID --exec
6 matches
Mail list logo
