[Michael Prokop]
> * Petter Reinholdtsen [Don Feb 25, 2010 at 07:01:43 +0100]:
> > I suspect this issue was solved when portmap version 6.0.0-2, but am
> > unsure if it is true. Please test and see if the issue is solved.
>
> Nope it's not fully solved yet.
>
> Executing "dpkg-reconfigure portm
* Petter Reinholdtsen [Don Feb 25, 2010 at 07:01:43 +0100]:
> I suspect this issue was solved when portmap version 6.0.0-2, but am
> unsure if it is true. Please test and see if the issue is solved.
Nope it's not fully solved yet.
Executing "dpkg-reconfigure portmap" in interactive mode and
ans
I suspect this issue was solved when portmap version 6.0.0-2, but am
unsure if it is true. Please test and see if the issue is solved.
Happy hacking,
--
Petter Reinholdtsen
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact
severity 317358 serious
tags 317358 - unreproducible - moreinfo
thanks
* Adam Woodworth [20091228 11:06]:
> When I did a recent "aptitude dist-upgrade", I saw the portmap question
> about binding to loopback or not. I chose "Yes" (bind to loopback), but I
> noticed that /etc/default/portmap isn
Package: portmap
Version: 5-14
When I did a recent "aptitude dist-upgrade", I saw the portmap question
about binding to loopback or not. I chose "Yes" (bind to loopback), but I
noticed that /etc/default/portmap isn't correctly updated. It should have
the OPTIONS="-i 127.0.0.1" line uncommented i
5 matches
Mail list logo