On Sat, Nov 29, 2008 at 11:03 AM, Aníbal Monsalve Salazar
<[EMAIL PROTECTED]> wrote:
>
> Hello All,
>
> Please test if portmap 6.0-9 fixes this bug.
It fixes the problem for me, thanks.
--
Giuseppe "Oblomov" Bilotta
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe"
On Sat, Nov 29, 2008 at 01:24:08AM -0500, Jacob Welsh wrote:
>Same problem here; I believe it is caused by /etc/init.d/portmap line
>33:
>
>pid=$( pidofproc portmap )
>if [ -n "$pid" ] ; then ...
>
>pidofproc then calls "/bin/pidof -o %PPID -x $1", but since it was run
>from a subshell, PPID does n
Same problem here; I believe it is caused by /etc/init.d/portmap line
33:
pid=$( pidofproc portmap )
if [ -n "$pid" ] ; then ...
pidofproc then calls "/bin/pidof -o %PPID -x $1", but since it was run
from a subshell, PPID does not refer to the "portmap" script and it is
not excluded. I worked aro
reassign 506995 portmap
thanks
[Giuseppe Bilotta]
> When bringing up the network interfaces, the init script attempt to mount nfs
> remotes fails, because statd previously failed to load. This is in turn due to
> portmap failing to load.
This I believe is because of a bug in portmap or lsb-base.
Package: initscripts
Version: 2.86.ds1-61
Severity: important
When bringing up the network interfaces, the init script attempt to mount nfs
remotes fails, because statd previously failed to load. This is in turn due to
portmap failing to load.
The portmap script, as called during the attempt to s
5 matches
Mail list logo
