From owner-freebsd-questions@FreeBSD.ORG Sat Mar 25 01:16:15 2006 Return-Path: X-Original-To: freebsd-questions@freebsd.org Delivered-To: freebsd-questions@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 01B0A16A400 for ; Sat, 25 Mar 2006 01:16:15 +0000 (UTC) (envelope-from chris@vindaloo.com) Received: from corellia.vindaloo.com (corellia.vindaloo.com [64.51.148.100]) by mx1.FreeBSD.org (Postfix) with ESMTP id AB49043D45 for ; Sat, 25 Mar 2006 01:16:14 +0000 (GMT) (envelope-from chris@vindaloo.com) Received: from yavin.vindaloo.com (yavin.vindaloo.com [172.24.144.34]) by corellia.vindaloo.com (Postfix) with ESMTP id EC7BF12969 for ; Fri, 24 Mar 2006 20:16:13 -0500 (EST) Received: from endaba.vindaloo.com (endaba.vindaloo.com [172.24.145.66]) by yavin.vindaloo.com (Postfix) with ESMTP id 76ED424C4D; Fri, 24 Mar 2006 20:16:13 -0500 (EST) From: Christopher Sean Hilton To: freebsd-questions@freebsd.org Content-Type: text/plain Date: Fri, 24 Mar 2006 20:16:39 -0500 Message-Id: <1143249399.4085.5.camel@endaba.vindaloo.com> Mime-Version: 1.0 X-Mailer: Evolution 2.2.2 FreeBSD GNOME Team Port Content-Transfer-Encoding: 7bit Subject: Cups startup problem on NFS client (w/resolution) X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 25 Mar 2006 01:16:15 -0000 This afternoon I had an interesting problem. Cups failed to startup on my machine and threw the error: cupsd: Child exited with status 48 or somesuch. The short story is that rpc.statd had grabbed port 631 on my machine and that blocked cups from working. Normally this would be harmless except the printer server box on my network sends out cups broadcasts on udp:631 which hosed up the rpc.statd until I had to reboot the box. Is there some way to tell rpc.statd and any other rpc daemons not to use a particular port. I didn't see such a switch in the man page. -- Chris