[Guillem Jover]
So the solution, is to add a '+' to the portmap entry in
insserv.conf and either make rpcbind provide a
/etc/insserv.conf.d/rpcbind file, or append rpcbind to $portmap in
/etc/insserv.conf.
I suspect the proper fix is to remove $portmap from insserv.conf and
instead add a
merge 565201 565230
affects 564501 rpcbind
thanks
Hi!
On Sun, 2010-01-10 at 01:49:42 +0200, Oren Held wrote:
On Saturday 09 January 2010 22:54:08 Petter Reinholdtsen wrote:
[Oren Held]
As far as I understand this cannot be done in /etc/insserv.d/,
because $portmap is already defined
[Guillem Jover]
So the solution, is to add a '+' to the portmap entry in
insserv.conf and either make rpcbind provide a
/etc/insserv.conf.d/rpcbind file, or append rpcbind to $portmap in
/etc/insserv.conf.
I suspect the proper fix is to remove $portmap from insserv.conf and
instead add a
Package: insserv
Version: 1.12.0-14
Severity: important
Tags: patch
The rpcbind service is an alternative to the portmap service.
There are many services that depend on $portmap, e.g. nfs-common,
nfs-kernel-server.
Thus, I believe that we should add rpcbind as a portmap alternative.
As far as
[Oren Held]
As far as I understand this cannot be done in /etc/insserv.d/,
because $portmap is already defined in /etc/insserv.conf.
I thought this worked fine. Did you test it and it failed? How did
it fail? Note that the directory is /etc/insserv.conf.d/.
Happy hacking,
--
Petter
Hi,
I didn't test it. I just believed that it doesn't make sense to APPEND things
to a facility already declared on /etc/insserv.conf.
But - I was wrong. Just tested and it works better than I've expected.
So please reject this bug, sorry for opening before checking. I was too
convinced.
I'll
6 matches
Mail list logo
