[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Bug#522294: marked as done (nfs-kernel-server: Fails to start: start-stop-daemon: command not found [SRM])

Your message dated Sat, 10 Dec 2022 14:35:35 +0100
with message-id <Y5SLJ3dZIEGjaIOz@mraw.org>
and subject line Re: Bug#522294: nfs-kernel-server: Fails to start: start-stop-daemon: command not found [SRM]
has caused the Debian Bug report #522294,
regarding nfs-kernel-server: Fails to start: start-stop-daemon: command not found [SRM]
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact owner@bugs.debian.org
immediately.)


-- 
522294: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=522294
Debian Bug Tracking System
Contact owner@bugs.debian.org with problems
--- Begin Message --- 
Package: nfs-kernel-server
Version: 1:1.1.2-6lenny1
Severity: serious
Justification: Policy 9.9

Hi.

In a clean lenny environment with mostly nfs-kernel-server installed, it
fails to start because of:
| start-stop-daemon: command not found

Obviously, since there's no default PATH set in the init script, that
just can't work. That's Policy 9.9:
| A program must not depend on environment variables to get reasonable
| defaults

Please set PATH to something like /sbin:/bin:/usr/sbin:/usr/bin or
whatever you see fit.

Please also fix the package in lenny (that's why I've put [SRM] in the
subject, and X-Debbugs-Cc'd debian-release@).

Thanks already.

Cheers,
-- 
Cyril Brulebois

-- System Information:
Debian Release: 5.0
  APT prefers stable
  APT policy: (500, 'stable')
Architecture: amd64 (x86_64)

Kernel: Linux 2.6.26-1-amd64 (SMP w/2 CPU cores)
Locale: LANG=fr_FR.UTF-8, LC_CTYPE=fr_FR.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/bash

Versions of packages nfs-kernel-server depends on:
ii  libblkid1             1.41.3-1           block device id library
ii  libc6                 2.7-18             GNU C Library: Shared libraries
ii  libcomerr2            1.41.3-1           common error description library
ii  libgssglue1           0.1-2              mechanism-switch gssapi library
ii  libkrb53              1.6.dfsg.4~beta1-5 MIT Kerberos runtime libraries
ii  libnfsidmap2          0.20-1             An nfs idmapping library
ii  librpcsecgss3         0.18-1             allows secure rpc communication us
ii  libwrap0              7.6.q-16           Wietse Venema's TCP wrappers libra
ii  lsb-base              3.2-20             Linux Standard Base 3.2 init scrip
ii  nfs-common            1:1.1.2-6lenny1    NFS support files common to client
ii  ucf                   3.0016             Update Configuration File: preserv

nfs-kernel-server recommends no packages.

nfs-kernel-server suggests no packages.

-- no debconf information

--- End Message ---
--- Begin Message --- 
Cyril Brulebois <kibi@debian.org> (2009-04-02):
> severity 522294 wishlist
> thanks
> (control@ in Bcc)
> 
> Cyril Brulebois <cyril.brulebois@kerlabs.com> (02/04/2009):
> > Package: nfs-kernel-server
> > Version: 1:1.1.2-6lenny1
> > Severity: serious
> > Justification: Policy 9.9
> 
> OK, I really shot too fast. “rc” indeed does the right thing, and I
> guess unsetting some variables in a previous init script would qualify
> as being very unfair to the other scripts (particularly for $PATH).
> That's why I'm lowering the severity to a wishlist bug.

Since I'm getting pinged about this once in a while: I've been using
n-k-s on more recent systems without any issues, and whatever problems I
thought I spotted at the time are no practical problems at this time.

(Having a systemd service unit makes the init.d script moot anyway.)


Cheers,
-- 
Cyril Brulebois (kibi@debian.org)            <https://debamax.com/>
D-I release manager -- Release team member -- Freelance Consultant

Attachment: signature.asc
Description: PGP signature


--- End Message ---
Reply to: