Devuan logs - #680, boring messages

Message sent to [email protected], [email protected]:

Subject: bug#680: RPCBind incorrect or incomplete runlevels
Reply-To: Ken Dibble <[email protected]>, [email protected]
Resent-From: Ken Dibble <[email protected]>
Resent-To: [email protected]
Resent-CC: [email protected]
Resent-Date: Fri, 03 Jun 2022 14:48:02 +0000
Resent-Message-ID: <[email protected]>
Resent-Sender: [email protected]
Message-ID: <[email protected]>
Date: Fri, 3 Jun 2022 10:45:38 -0400
MIME-Version: 1.0
Content-Language: en-US
To: [email protected]
From: Ken Dibble <[email protected]>
Content-Type: text/plain; charset=UTF-8; format=flowed
Content-Transfer-Encoding: 7bit

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

Message sent:

Content-Disposition: inline
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-Mailer: MIME-tools 5.509 (Entity 5.509)
Content-Type: text/plain; charset=utf-8
X-Loop: [email protected]
From: "Devuan bug Tracking System" <[email protected]>
To: Ken Dibble <[email protected]>
Subject: bug#680: Acknowledgement (RPCBind incorrect or incomplete runlevels)
Message-ID: <[email protected]>
References: <[email protected]>
X-Devuan-PR-Message: ack 680
X-Devuan-PR-Package: rpcbind
Reply-To: [email protected]
Date: Fri, 03 Jun 2022 14:48:05 +0000

Thank you for filing a new bug report with Devuan.

You can follow progress on this bug here: 680: https://bugs.devuan.org/cgi/=
bugreport.cgi?bug=3D680.

This is an automatically generated reply to let you know your message
has been received.

Your message is being forwarded to the package maintainers and other
interested parties for their attention; they will reply in due course.

Your message has been sent to the package maintainer(s):
 [email protected]

If you wish to submit further information on this problem, please
send it to [email protected].

Please do not send mail to [email protected] unless you wish
to report a problem with the Bug-tracking system.

--=20
680: https://bugs.devuan.org/cgi/bugreport.cgi?bug=3D680
Devuan Bug Tracking System
Contact [email protected] with problems

Message sent to [email protected], [email protected]:

Subject: bug#680: RPCBind incorrect or incomplete runlevels
Reply-To: Mark Hindley <[email protected]>, [email protected]
Resent-From: Mark Hindley <[email protected]>
Resent-To: [email protected]
Resent-CC: [email protected]
Resent-Date: Tue, 07 Jun 2022 10:20:01 +0000
Resent-Message-ID: <[email protected]>
Resent-Sender: [email protected]
References: <[email protected]> <[email protected]>
Date: Tue, 7 Jun 2022 11:18:55 +0100
From: Mark Hindley <[email protected]>
To: Ken Dibble <[email protected]>, [email protected]
Message-ID: <[email protected]>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <[email protected]>

Control: tag -1 debian

Ken,

Thanks for this.

On Fri, Jun 03, 2022 at 10:45:38AM -0400, Ken Dibble wrote:
> Package: rpcbind
> 
> Version: 1.2.5-9
> 
> The only time rpcbind is brought up is at system start.
> 
> RUNLEVEL 1 kills it.

I don't know why the LSB header specifies that either. The oldest version in
Debian[1] also has the same header wrt runlevels.

src:rpcbind is not a forked package and Devuan uses Debian's packages
directly without recompilation. Please report this  to Debian's BTS to be
addressed.

Thanks

Mark

[1]  https://deb.debian.org/debian/pool/main/r/rpcbind/rpcbind_0.2.3-0.6.dsc

Message received at [email protected]:

Date: Tue, 7 Jun 2022 11:18:55 +0100
From: Mark Hindley <[email protected]>
To: Ken Dibble <[email protected]>, [email protected]
Subject: Re: bug#680: RPCBind incorrect or incomplete runlevels
Message-ID: <[email protected]>
References: <[email protected]>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <[email protected]>

Control: tag -1 debian

Ken,

Thanks for this.

On Fri, Jun 03, 2022 at 10:45:38AM -0400, Ken Dibble wrote:
> Package: rpcbind
> 
> Version: 1.2.5-9
> 
> The only time rpcbind is brought up is at system start.
> 
> RUNLEVEL 1 kills it.

I don't know why the LSB header specifies that either. The oldest version in
Debian[1] also has the same header wrt runlevels.

src:rpcbind is not a forked package and Devuan uses Debian's packages
directly without recompilation. Please report this  to Debian's BTS to be
addressed.

Thanks

Mark

[1]  https://deb.debian.org/debian/pool/main/r/rpcbind/rpcbind_0.2.3-0.6.dsc

Message received at [email protected]:

Received: (at control) by bugs.devuan.org; 8 Jun 2022 10:15:04 +0000
Return-Path: <[email protected]>
Delivered-To: [email protected]
Received: from mail.dyne.org [141.95.83.167]
	by doc.devuan.org with IMAP (fetchmail-6.4.16)
	for <debbugs@localhost> (single-drop); Wed, 08 Jun 2022 10:15:04 +0000 (UTC)
Received: from mx.hindley.org.uk (193-36-131-86.cfwn.uk [193.36.131.86])
	(using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits))
	(No client certificate requested)
	by mail.dyne.org (Postfix) with ESMTPS id 1E8E466135B
	for <[email protected]>; Wed,  8 Jun 2022 12:14:04 +0200 (CEST)
Received: from apollo.hindleynet ([192.168.1.3] helo=hindley.org.uk)
	by mx.hindley.org.uk with smtp (Exim 4.84_2)
	(envelope-from <[email protected]>)
	id 1nyshP-0003YR-8c
	for [email protected]; Wed, 08 Jun 2022 11:14:03 +0100
Received: (nullmailer pid 21341 invoked by uid 1000);
	Wed, 08 Jun 2022 10:14:03 -0000
From: Mark Hindley <[email protected]>
To: [email protected]
Subject: bug 680 is forwarded to https://bugs.debian.org/1012444
Date: Wed, 08 Jun 2022 11:14:03 +0100
Message-ID: <[email protected]>
X-Spam-Status: No, score=0.4 required=5.0 tests=RCVD_IN_DNSWL_BLOCKED,
	RDNS_DYNAMIC,SPF_PASS,TVD_SPACE_RATIO autolearn=disabled version=3.4.2
X-Spam-Checker-Version: SpamAssassin 3.4.2 (2018-09-13) on mail.dyne.org

forwarded 680 https://bugs.debian.org/1012444
thanks

Message sent:

MIME-Version: 1.0
X-Mailer: MIME-tools 5.509 (Entity 5.509)
X-Loop: [email protected]
From: "Devuan bug Tracking System" <[email protected]>
To: Mark Hindley <[email protected]>
Subject: bug#680: marked as done (RPCBind incorrect or incomplete runlevels)
Message-ID: <[email protected]>
References: <[email protected]>
 <[email protected]>
X-Devuan-PR-Message: closed 680
X-Devuan-PR-Package: rpcbind
X-Devuan-PR-Keywords: debian
Reply-To: [email protected]
Date: Tue, 10 Jan 2023 17:00:04 +0000
Content-Type: multipart/mixed; boundary="----------=_1673370004-16728-0"

This is a multi-part message in MIME format...

------------=_1673370004-16728-0
Content-Disposition: inline
Content-Transfer-Encoding: quoted-printable
Content-Type: text/plain; charset="utf-8"

Your message dated Tue, 10 Jan 2023 16:59:57 +0000
with message-id <[email protected]>
and subject line Fixed in Debian #1012444
has caused the Devuan bug report #680,
regarding RPCBind incorrect or incomplete runlevels
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.)


--=20
680: https://bugs.devuan.org/cgi/bugreport.cgi?bug=3D680
Devuan Bug Tracking System
Contact [email protected] with problems

------------=_1673370004-16728-0
Content-Type: message/rfc822
Content-Disposition: inline
Content-Transfer-Encoding: 7bit

Received: (at submit) by bugs.devuan.org; 3 Jun 2022 14:46:42 +0000
Return-Path: <[email protected]>
Delivered-To: [email protected]
Received: from mail.dyne.org [141.95.83.167]
	by doc.devuan.org with IMAP (fetchmail-6.4.16)
	for <debbugs@localhost> (single-drop); Fri, 03 Jun 2022 14:46:41 +0000 (UTC)
Received: from sender4-of-o51.zoho.com (sender4-of-o51.zoho.com [136.143.188.51])
	(using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits))
	(No client certificate requested)
	by mail.dyne.org (Postfix) with ESMTPS id 9529F6617B5
	for <[email protected]>; Fri,  3 Jun 2022 16:45:44 +0200 (CEST)
ARC-Seal: i=1; a=rsa-sha256; t=1654267541; cv=none; 
	d=zohomail.com; s=zohoarc; 
	b=Fqgud1KAYkqUqEfnsJdxLPPlko5mcSk+hptHsJwHFTdm+7hgcKXbOQba7tniIEEGmp5Ubn/NuYCtliOGzg8ViHACfieQhIlyESpGV38+3KNGIJgxNKU1GcQGLefsk93EIevxLtbSjr4ssN42PzGZY/NN4flbBjDtPumHtrJPREQ=
ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=zohomail.com; s=zohoarc; 
	t=1654267541; h=Content-Type:Content-Transfer-Encoding:Date:From:MIME-Version:Message-ID:Subject:To; 
	bh=RYZvhLcxsTrW5TBfINAzucjbJHJ2qLNzhV/vgqMyHtY=; 
	b=SSVUnz5MDnh3Rk1HR8xcfzGhO7d4d3KH03/6+ro2DFwaO0wbYRSf/AZ+DrUVOpMJsAIC7/79bbsnN9yKbc/XBiAtka2Y83hcodfjX8ecftwYkN87zWL4FOssscZqiOAHvGsBsQw4l3EzNgCxLxT5ZurXs0NYBaICaK7pzhnVndI=
ARC-Authentication-Results: i=1; mx.zohomail.com;
	spf=pass  [email protected];
	dmarc=pass header.from=<[email protected]>
Received: from [192.168.0.17] (cpe-71-64-9-76.insight.res.rr.com [71.64.9.76]) by mx.zohomail.com
	with SMTPS id 1654267540267377.49097590979216; Fri, 3 Jun 2022 07:45:40 -0700 (PDT)
Message-ID: <[email protected]>
Date: Fri, 3 Jun 2022 10:45:38 -0400
MIME-Version: 1.0
Content-Language: en-US
To: [email protected]
From: Ken Dibble <[email protected]>
Subject: RPCBind incorrect or incomplete runlevels
Content-Type: text/plain; charset=UTF-8; format=flowed
Content-Transfer-Encoding: 7bit
X-ZohoMailClient: External
X-Spam-Status: No, score=-0.0 required=5.0 tests=RCVD_IN_DNSWL_NONE,SPF_PASS
	autolearn=disabled version=3.4.2
X-Spam-Checker-Version: SpamAssassin 3.4.2 (2018-09-13) on mail.dyne.org

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

------------=_1673370004-16728-0
Content-Type: message/rfc822
Content-Disposition: inline
Content-Transfer-Encoding: 7bit

Received: (at 680-done) by bugs.devuan.org; 10 Jan 2023 17:00:01 +0000
Return-Path: <[email protected]>
Delivered-To: [email protected]
Received: from email.devuan.org [2001:41d0:2:d06e::5c4:2612]
	by doc.devuan.org with IMAP (fetchmail-6.4.16)
	for <debbugs@localhost> (single-drop); Tue, 10 Jan 2023 17:00:01 +0000 (UTC)
Received: from email.devuan.org
	by email.devuan.org with LMTP
	id S03rMY6ZvWMJKwAAmSBk0A
	(envelope-from <[email protected]>)
	for <[email protected]>; Tue, 10 Jan 2023 16:59:58 +0000
Received: by email.devuan.org (Postfix, from userid 109)
	id BEA31DB6; Tue, 10 Jan 2023 16:59:58 +0000 (UTC)
X-Spam-Checker-Version: SpamAssassin 3.4.6 (2021-04-09) on email.devuan.org
X-Spam-Level: 
X-Spam-Status: No, score=0.4 required=5.0 tests=RDNS_DYNAMIC,SPF_PASS
	autolearn=no autolearn_force=no version=3.4.6
Received-SPF: Pass (mailfrom) identity=mailfrom; client-ip=193.36.131.86; helo=mx.hindley.org.uk; [email protected]; receiver=<UNKNOWN> 
Received: from mx.hindley.org.uk (193-36-131-86.cfwn.uk [193.36.131.86])
	by email.devuan.org (Postfix) with ESMTPS id 6A026B69
	for <[email protected]>; Tue, 10 Jan 2023 16:59:58 +0000 (UTC)
Received: from apollo.hindleynet ([192.168.1.3] helo=hindley.org.uk)
	by mx.hindley.org.uk with smtp (Exim 4.84_2)
	(envelope-from <[email protected]>)
	id 1pFHyf-00032F-C5
	for [email protected]; Tue, 10 Jan 2023 16:59:57 +0000
Received: (nullmailer pid 25534 invoked by uid 1000);
	Tue, 10 Jan 2023 16:59:57 -0000
Date: Tue, 10 Jan 2023 16:59:57 +0000
From: Mark Hindley <[email protected]>
To: [email protected]
Subject: Fixed in Debian #1012444
Message-ID: <[email protected]>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
X-Debbugs-No-Ack: No Thanks

Version: 1.2.6-5
------------=_1673370004-16728-0--

Message sent:

MIME-Version: 1.0
X-Mailer: MIME-tools 5.509 (Entity 5.509)
X-Loop: [email protected]
From: "Devuan bug Tracking System" <[email protected]>
To: Ken Dibble <[email protected]>
Subject: bug#680 closed by Mark Hindley <[email protected]> (Fixed in
 Debian #1012444)
Message-ID: <[email protected]>
References: <[email protected]>
 <[email protected]>
X-Devuan-PR-Message: they-closed 680
X-Devuan-PR-Package: rpcbind
X-Devuan-PR-Keywords: debian
Reply-To: [email protected]
Date: Tue, 10 Jan 2023 17:00:05 +0000
Content-Type: multipart/mixed; boundary="----------=_1673370005-16728-1"

This is a multi-part message in MIME format...

------------=_1673370005-16728-1
Content-Disposition: inline
Content-Transfer-Encoding: quoted-printable
Content-Type: text/plain; charset="utf-8"

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 <[email protected]>.

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@hin=
dley.org.uk> by
replying to this email.


--=20
680: https://bugs.devuan.org/cgi/bugreport.cgi?bug=3D680
Devuan Bug Tracking System
Contact [email protected] with problems

------------=_1673370005-16728-1
Content-Type: message/rfc822
Content-Disposition: inline
Content-Transfer-Encoding: 7bit

Received: (at 680-done) by bugs.devuan.org; 10 Jan 2023 17:00:01 +0000
Return-Path: <[email protected]>
Delivered-To: [email protected]
Received: from email.devuan.org [2001:41d0:2:d06e::5c4:2612]
	by doc.devuan.org with IMAP (fetchmail-6.4.16)
	for <debbugs@localhost> (single-drop); Tue, 10 Jan 2023 17:00:01 +0000 (UTC)
Received: from email.devuan.org
	by email.devuan.org with LMTP
	id S03rMY6ZvWMJKwAAmSBk0A
	(envelope-from <[email protected]>)
	for <[email protected]>; Tue, 10 Jan 2023 16:59:58 +0000
Received: by email.devuan.org (Postfix, from userid 109)
	id BEA31DB6; Tue, 10 Jan 2023 16:59:58 +0000 (UTC)
X-Spam-Checker-Version: SpamAssassin 3.4.6 (2021-04-09) on email.devuan.org
X-Spam-Level: 
X-Spam-Status: No, score=0.4 required=5.0 tests=RDNS_DYNAMIC,SPF_PASS
	autolearn=no autolearn_force=no version=3.4.6
Received-SPF: Pass (mailfrom) identity=mailfrom; client-ip=193.36.131.86; helo=mx.hindley.org.uk; [email protected]; receiver=<UNKNOWN> 
Received: from mx.hindley.org.uk (193-36-131-86.cfwn.uk [193.36.131.86])
	by email.devuan.org (Postfix) with ESMTPS id 6A026B69
	for <[email protected]>; Tue, 10 Jan 2023 16:59:58 +0000 (UTC)
Received: from apollo.hindleynet ([192.168.1.3] helo=hindley.org.uk)
	by mx.hindley.org.uk with smtp (Exim 4.84_2)
	(envelope-from <[email protected]>)
	id 1pFHyf-00032F-C5
	for [email protected]; Tue, 10 Jan 2023 16:59:57 +0000
Received: (nullmailer pid 25534 invoked by uid 1000);
	Tue, 10 Jan 2023 16:59:57 -0000
Date: Tue, 10 Jan 2023 16:59:57 +0000
From: Mark Hindley <[email protected]>
To: [email protected]
Subject: Fixed in Debian #1012444
Message-ID: <[email protected]>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
X-Debbugs-No-Ack: No Thanks

Version: 1.2.6-5
------------=_1673370005-16728-1
Content-Type: message/rfc822
Content-Disposition: inline
Content-Transfer-Encoding: 7bit

Received: (at submit) by bugs.devuan.org; 3 Jun 2022 14:46:42 +0000
Return-Path: <[email protected]>
Delivered-To: [email protected]
Received: from mail.dyne.org [141.95.83.167]
	by doc.devuan.org with IMAP (fetchmail-6.4.16)
	for <debbugs@localhost> (single-drop); Fri, 03 Jun 2022 14:46:41 +0000 (UTC)
Received: from sender4-of-o51.zoho.com (sender4-of-o51.zoho.com [136.143.188.51])
	(using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits))
	(No client certificate requested)
	by mail.dyne.org (Postfix) with ESMTPS id 9529F6617B5
	for <[email protected]>; Fri,  3 Jun 2022 16:45:44 +0200 (CEST)
ARC-Seal: i=1; a=rsa-sha256; t=1654267541; cv=none; 
	d=zohomail.com; s=zohoarc; 
	b=Fqgud1KAYkqUqEfnsJdxLPPlko5mcSk+hptHsJwHFTdm+7hgcKXbOQba7tniIEEGmp5Ubn/NuYCtliOGzg8ViHACfieQhIlyESpGV38+3KNGIJgxNKU1GcQGLefsk93EIevxLtbSjr4ssN42PzGZY/NN4flbBjDtPumHtrJPREQ=
ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=zohomail.com; s=zohoarc; 
	t=1654267541; h=Content-Type:Content-Transfer-Encoding:Date:From:MIME-Version:Message-ID:Subject:To; 
	bh=RYZvhLcxsTrW5TBfINAzucjbJHJ2qLNzhV/vgqMyHtY=; 
	b=SSVUnz5MDnh3Rk1HR8xcfzGhO7d4d3KH03/6+ro2DFwaO0wbYRSf/AZ+DrUVOpMJsAIC7/79bbsnN9yKbc/XBiAtka2Y83hcodfjX8ecftwYkN87zWL4FOssscZqiOAHvGsBsQw4l3EzNgCxLxT5ZurXs0NYBaICaK7pzhnVndI=
ARC-Authentication-Results: i=1; mx.zohomail.com;
	spf=pass  [email protected];
	dmarc=pass header.from=<[email protected]>
Received: from [192.168.0.17] (cpe-71-64-9-76.insight.res.rr.com [71.64.9.76]) by mx.zohomail.com
	with SMTPS id 1654267540267377.49097590979216; Fri, 3 Jun 2022 07:45:40 -0700 (PDT)
Message-ID: <[email protected]>
Date: Fri, 3 Jun 2022 10:45:38 -0400
MIME-Version: 1.0
Content-Language: en-US
To: [email protected]
From: Ken Dibble <[email protected]>
Subject: RPCBind incorrect or incomplete runlevels
Content-Type: text/plain; charset=UTF-8; format=flowed
Content-Transfer-Encoding: 7bit
X-ZohoMailClient: External
X-Spam-Status: No, score=-0.0 required=5.0 tests=RCVD_IN_DNSWL_NONE,SPF_PASS
	autolearn=disabled version=3.4.2
X-Spam-Checker-Version: SpamAssassin 3.4.2 (2018-09-13) on mail.dyne.org

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

------------=_1673370005-16728-1--