From owner-freebsd-questions Thu Feb 14 9:10:23 2002 Delivered-To: freebsd-questions@freebsd.org Received: from dire.bris.ac.uk (dire.bris.ac.uk [137.222.10.60]) by hub.freebsd.org (Postfix) with ESMTP id 94B2837B416 for ; Thu, 14 Feb 2002 09:10:19 -0800 (PST) Received: from mail.ilrt.bris.ac.uk by dire.bris.ac.uk with SMTP-PRIV with ESMTP; Thu, 14 Feb 2002 17:10:08 +0000 Received: from cmjg (helo=localhost) by mail.ilrt.bris.ac.uk with local-esmtp (Exim 3.16 #1) id 16bPON-0003mV-00; Thu, 14 Feb 2002 17:09:55 +0000 Date: Thu, 14 Feb 2002 17:09:55 +0000 (GMT) From: Jan Grant X-X-Sender: cmjg@mail.ilrt.bris.ac.uk To: Steven Lake Cc: Douglas Egan , freebsd-questions Subject: Re: bind: permission denied In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-questions@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG On Thu, 14 Feb 2002, Steven Lake wrote: > Simple answer. Root owns the program, root owns the processes > it runs on, only root has permissions to execute it because of how it runs. > I've had the same thing with many programs, even ones assigned to my generic > user or owned by them, regardless if they're part of the wheel group or > not. It's a security thing. :) > > On Thu, 14 Feb 2002, Douglas Egan wrote: > > > I just installed ports/mail/sylpheed. I installed like I always install > > something from ports; as root, make; make install; > > > > I can execute the program from root, but cannot execute it as a normal > > user. I get: > > > > %sylpheed > > bind: Permission denied > > % > > > > The author of syplheed suggested looking at the /tmp permissions, but > > they were as suggested and as installed. > > > > drwxrwxrwt 8 root wheel 1024 Feb 14 03:23 tmp > > > > > > %uname -a > > FreeBSD porgy 4.4-STABLE FreeBSD 4.4-STABLE #0: Thu Dec 13 14:40:35 CST > > 2001 degan@porgy:/usr/obj/usr/src/sys/DOUG-AMD i386 > > % > > > > > > Any ideas? That explanation sounds a bit vague. The error message is probably being generated by a failed call to bind(2); the problem sounds like this: [EACCES] The requested address is protected, and the current user has inadequate permission to access it. So it's probably sylpheed trying to bind to a low-numbered port (1023 or less), which you need root privs to do. Alternatively, trying to open a unix-domain socket (ie, one in the filesystem) where you don't have sufficient FS privs to do so can also cause this. -- jan grant, ILRT, University of Bristol. http://www.ilrt.bris.ac.uk/ Tel +44(0)117 9287088 Fax +44 (0)117 9287112 RFC822 jan.grant@bris.ac.uk Usenet: The separation of content AND presentation - simultaneously. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-questions" in the body of the message