Devuan bug report logs - #680
RPCBind incorrect or incomplete runlevels

Full log

🔗 View this message in rfc822 format

MIME-Version: 1.0
X-Mailer: MIME-tools 5.509 (Entity 5.509)
X-Loop: owner@bugs.devuan.org
From: "Devuan bug Tracking System" <owner@bugs.devuan.org>
To: Ken Dibble <ken@beckydibble.com>
Subject: bug#680 closed by Mark Hindley <mark@hindley.org.uk> (Fixed in
 Debian #1012444)
Message-ID: <handler.680.D680.167337000116725.notifdone@bugs.devuan.org>
References: <Y72ZjbB338a1VXj0@hindley.org.uk>
 <d1b39174-889f-3444-ad58-f0e032588d85@beckydibble.com>
X-Devuan-PR-Message: they-closed 680
X-Devuan-PR-Package: rpcbind
X-Devuan-PR-Keywords: debian
Reply-To: 680@bugs.devuan.org
Date: Tue, 10 Jan 2023 17:00:05 +0000
Content-Type: multipart/mixed; boundary="----------=_1673370005-16728-1"

[Message part 1 (text/plain, inline)]

This is an automatic notification regarding your bug report
which was filed against the rpcbind package:

#680: RPCBind incorrect or incomplete runlevels

It has been closed by Mark Hindley <mark@hindley.org.uk>.

Their explanation is attached below along with your original report.
If this explanation is unsatisfactory and you have not received a
better one in a separate message then please contact Mark Hindley <mark@hindley.org.uk> by
replying to this email.


-- 
680: https://bugs.devuan.org/cgi/bugreport.cgi?bug=680
Devuan Bug Tracking System
Contact owner@bugs.devuan.org with problems

[Message part 2 (message/rfc822, inline)]

From: Mark Hindley <mark@hindley.org.uk>

To: 680-done@bugs.devuan.org

Subject: Fixed in Debian #1012444

Date: Tue, 10 Jan 2023 16:59:57 +0000

Version: 1.2.6-5

[Message part 3 (message/rfc822, inline)]

From: Ken Dibble <ken@beckydibble.com>

To: submit@bugs.devuan.org

Subject: RPCBind incorrect or incomplete runlevels

Date: Fri, 3 Jun 2022 10:45:38 -0400

Package: rpcbind

Version: 1.2.5-9


The only time rpcbind is brought up is at system start.

RUNLEVEL 1 kills it.



So either rpcbind shouldn't be killed at runlevel 1 or it should be

made sure to be running prior to nfs-kernel-server on runlevels 2-5.

$sudo su

# init 1

.

.

#init 5

# /etc/init.d/nfs-kernel-server restart

System response:

Stopping NFS kernel daemon: mountd nfsd.
Unexporting directories for NFS kernel daemon....
Exporting directories for NFS kernel daemon....
Starting NFS kernel daemon: nfsd
Not starting: portmapper is not running ... (warning).


#/etc/init.d/rpcbind restart

System response:

Stopping RPC port mapper daemon: rpcbind.
Starting RPC port mapper daemon: rpcbind.


#/etc/init.d/nfs-kernel-server restart

System response:

Stopping NFS kernel daemon: mountd nfsd.
Unexporting directories for NFS kernel daemon....
Exporting directories for NFS kernel daemon....
Starting NFS kernel daemon: nfsd mountd.


Investigation:

/etc$sudo find . -name *nfs-kernel-server
./rc2.d/S04nfs-kernel-server
./rc0.d/K01nfs-kernel-server
./rc1.d/K01nfs-kernel-server
./default/nfs-kernel-server
./init.d/nfs-kernel-server
./rc3.d/S04nfs-kernel-server
./rc4.d/S04nfs-kernel-server
./rc6.d/K01nfs-kernel-server
./rc5.d/S04nfs-kernel-server


/etc$ sudo find . -name *rpcbind
./rc0.d/K06rpcbind
./rc1.d/K06rpcbind
./rcS.d/S17rpcbind
./default/rpcbind
./init.d/rpcbind
./rc6.d/K06rpcbind
./insserv.conf.d/rpcbind


The fix would appear to be obvious and trivial.

Modify the installation script to set the rc scripts correctly.


Regards,

Ken

Send a report that this bug log contains spam.