Bug#484861: nfs-common: rpc.statd --outgoing-port (-o) option broken

2011-04-14 Thread Harakiri
Upstream kindly explained that this is expected and harmless, the random
numbered port is used for internel kernel communitacion only and totally
unrelated to --outgoing-port.  Whatever causes your firewall issues, it
shouldn't be this.  The Ubuntu bug is also something different.

Unless something new turns up, I think this bug should be closed.

Could you kindly tell upstream that this is indeed broken - the package will 
use the heartbeat communication port because of the randomess of port 
assignment - please enable --outgoing-port

heartbeat: [28538]: ERROR: glib: ucast: error binding socket. Retrying: Address
already in use





-- 
To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Archive: http://lists.debian.org/30252.41968...@web130210.mail.mud.yahoo.com



Bug#484861: nfs-common: rpc.statd --outgoing-port (-o) option broken

2010-08-12 Thread Harakiri
So, 2 years and its fixed in ubuntu but not in debian - is the package 
maintainer aware of this problem? Can it please be fixed in the next upstream.


  



-- 
To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Archive: http://lists.debian.org/785979.49858...@web52208.mail.re2.yahoo.com