Bug#391687: rpc-statd do not exit with error when not possible to bind

2006-10-10 Thread Steinar H. Gunderson
On Tue, Oct 10, 2006 at 09:31:11PM +0200, Jean Marc Lacroix wrote: > Ok about the severity for bug, but the bug exist, the exit code 0 is > reserved for success return only, otherwise it is not possible for calling > application to know if the service is ok or not. But the daemon forks and exits b

Bug#391687: rpc-statd do not exit with error when not possible to bind

2006-10-08 Thread Jean Marc Lacroix
Package: nfs-common Version: 1.0.10-1 Severity: |grave| When launching rpc.statd with dedicated port in file /etc/default/nfs-common for STATDOPTS="--port 126 --outgoing-port 124" for exemple, and IF the port are not available, then rpc-statd exit without error and no log so it is very hard to un