Your message dated Tue, 10 Nov 2015 15:55:18 +0000
with message-id <[email protected]>
and subject line Bug#679716: fixed in rpcbind 0.2.3-0.1
has caused the Debian Bug report #679716,
regarding rpcbind: Please consider patch to enable socket-based activation for 
systemd
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 [email protected]
immediately.)


-- 
679716: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=679716
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
Package: rpcbind
Version: 0.2.0-8
Severity: wishlist

Hi,

when installing the sysvinit replacement systemd, rpcbind is still started
through LSB compatibility support by systemd. This results in rpcbind
not being reliably started before any services that depend on rpcbind
like NFS mounts.

In our particular case, the home directory would not get mounted upon
boot since systemd often tries to mount the home directory before
it starts rpcbind due to the boot parallelization. A problem that
we have also observed when using sysvinit when rpcbind might not
get reliably started or crashes for whatever reason.

To resolve this problem, systemd upstream has patched rpcbind to be
compatible with socket-based activation [1]. With the patch, rpcbind
will be started by systemd through socket-based activation and is hence
always guaranteed to be available for services like NFS.

While I understand that this patch might be problematic for Debian
since it might trigger problems with the non-Linux kernels, I'd
still like to point out the need for a socket-activated rpcbind
and this patch.

I will perfom some testing with a patched rpcbind on the kFreeBSD-
and Hurd-based versions of Debian and report back. If rpcbind
still continues to build and work fine on these platforms with
sysvinit, the idea might not be too bad for Debian to patch
rpcbind for socket-based activation, since it really improves
reliability for NFS mounts.

Thanks,

Adrian

[1] 
http://lists.freedesktop.org/archives/systemd-devel/2012-February/004336.html

-- System Information:
Debian Release: wheezy/sid
  APT prefers testing
  APT policy: (500, 'testing'), (100, 'unstable'), (1, 'experimental')
Architecture: amd64 (x86_64)
Foreign Architectures: i386

Kernel: Linux 3.2.0-2-amd64 (SMP w/4 CPU cores)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8) (ignored: LC_ALL 
set to en_US.UTF-8)
Shell: /bin/sh linked to /bin/dash

Versions of packages rpcbind depends on:
ii  initscripts  2.88dsf-22.1
ii  insserv      1.14.0-3
ii  libc6        2.13-33
ii  libtirpc1    0.2.2-5
ii  libwrap0     7.6.q-23
ii  lsb-base     4.1+Debian7

rpcbind recommends no packages.

rpcbind suggests no packages.

-- no debconf information



--- End Message ---
--- Begin Message ---
Source: rpcbind
Source-Version: 0.2.3-0.1

We believe that the bug you reported is fixed in the latest version of
rpcbind, which is due to be installed in the Debian FTP archive.

A summary of the changes between this version and the previous one is
attached.

Thank you for reporting the bug, which will now be closed.  If you
have further comments please address them to [email protected],
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Laurent Bigonville <[email protected]> (supplier of updated rpcbind package)

(This message was generated automatically at their request; if you
believe that there is a problem with it please contact the archive
administrators by mailing [email protected])


-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA256

Format: 1.8
Date: Tue, 10 Nov 2015 13:36:12 +0100
Source: rpcbind
Binary: rpcbind
Architecture: source amd64
Version: 0.2.3-0.1
Distribution: unstable
Urgency: low
Maintainer: Anibal Monsalve Salazar <[email protected]>
Changed-By: Laurent Bigonville <[email protected]>
Description:
 rpcbind    - converts RPC program numbers into universal addresses
Closes: 679716 747134 748074
Changes:
 rpcbind (0.2.3-0.1) unstable; urgency=low
 .
   * Non-maintainer upload.
   * New upstream release
     - Enable systemd socket activation support (Closes: #679716)
   * Override init.d-script-not-included-in-package and
     init.d-script-not-marked-as-conffile lintian warnings/errors
   * Add systemd and tmpfiles.d files (Closes: #748074)
   * Add 07-Delete-the-unix-socket-only-if-we-have-created-it.patch: rpcbind
     daemon shouldn't try to remove its socket if it as been socket activated
   * Include some upstart jobs changes from Ubuntu (Closes: #747134)
     - debian/rpcbind.rpcbind-boot.upstart: document that this job emits the
       start-rpcbind event.
     - Don't pass -w to rpcbind on boot up, since the files won't be there to
       be read.
Checksums-Sha1:
 bfb2544de6f0dba912039ba4e33bdb76f1c94650 1507 rpcbind_0.2.3-0.1.dsc
 e79974a99d09b6d6fff9d86bf00225dc33723ce2 121306 rpcbind_0.2.3.orig.tar.bz2
 ab0412b20e35a2d30300ad79756d83efe459397a 11256 rpcbind_0.2.3-0.1.debian.tar.xz
 4938895d047a52692da020e9d2b6e49789ccbe18 44544 rpcbind_0.2.3-0.1_amd64.deb
Checksums-Sha256:
 4d2ea81fb4af2a44ec945c8125b7b4f152044f6e5e443ac10536ea3364eb6251 1507 
rpcbind_0.2.3-0.1.dsc
 9897823a9d820ea011d9ea02054d5ab99469b9ca5346265fee380713c8fed27b 121306 
rpcbind_0.2.3.orig.tar.bz2
 51d44f38a8bba8c358ff5919d2e9cd806d046acb72a6f322b5e4d8f2fa23db23 11256 
rpcbind_0.2.3-0.1.debian.tar.xz
 b728cee8be57bd12a055ef5570d342c563cbbb3aa2d4a41a595427193c32c836 44544 
rpcbind_0.2.3-0.1_amd64.deb
Files:
 7e2304cb905b5c02979cc9661f6f41d1 1507 net standard rpcbind_0.2.3-0.1.dsc
 c8875246b2688a1adfbd6ad43480278d 121306 net standard rpcbind_0.2.3.orig.tar.bz2
 aa963a617c42c1e86450367ee57bebbf 11256 net standard 
rpcbind_0.2.3-0.1.debian.tar.xz
 04dd8643579e15d7ecc069758d025c0f 44544 net standard rpcbind_0.2.3-0.1_amd64.deb

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1

iQEcBAEBCAAGBQJWQgSzAAoJEB/FiR66sEPV4IIH/2OMAGef82QE+IJ4pu2r7dND
bt+n51/+t1a0bOBi3V/Z4X0C5Bqgka0tlTmS8iDubdG9jOGOkap7Ad1NpYNBX6dr
cmKSmEWYLBVOOC/IqkmtTRXKrNXEY2XSQtRabA0akk+irWQ7m8wFK6C6stDE2oMi
2Y3x/L4eNswMYWPnF1a57wPZ7XwAZqFOWYqdq4vqQgU8PE9smw57hsxaMQPm2qCM
zS8R5jBcty3nSbSfRQv9dEIIpbHyDkHyUXo3oDJXCNHIFZy43guIyCNp/UoiJoDc
shZO2wXo/HQWGzSr+HyoQLMh7KfZPu0vDr8Ca/4gf/1WORIplv8T+tC22tw/OTo=
=kT9J
-----END PGP SIGNATURE-----

--- End Message ---

Reply via email to