From owner-freebsd-questions@FreeBSD.ORG Tue Jul 22 01:02:45 2003 Return-Path: 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 5D72E37B401 for ; Tue, 22 Jul 2003 01:02:45 -0700 (PDT) Received: from www20.networkshosting.com (www20.networkshosting.com [66.96.128.119]) by mx1.FreeBSD.org (Postfix) with SMTP id 514DC43F85 for ; Tue, 22 Jul 2003 01:02:44 -0700 (PDT) (envelope-from brad@perfectcircle.ca) Received: (qmail 29493 invoked from network); 22 Jul 2003 08:02:22 -0000 Received: from unknown (HELO kthx) (142.179.102.195) by www20.fatcow.com with SMTP; 22 Jul 2003 08:02:22 -0000 Message-ID: <001f01c35027$a09853f0$c366b38e@kthx> From: "Brad" To: Date: Tue, 22 Jul 2003 01:02:40 -0700 MIME-Version: 1.0 X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 6.00.2800.1158 X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1165 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable X-Content-Filtered-By: Mailman/MimeDel 2.1.1 Subject: Make Permission errors! Most odd. X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 22 Jul 2003 08:02:45 -0000 I've been experiencing permission errors with make intermittently. It's = happening with quite a few users on the box but it's just random. It's = never a certain application or a certain user/group so it's been very = hard to pinpoint what the problem is, hence why I'm posting here. What is happening is basically a user will untar a file and type "make" = after a ./configure and get "make: Permission denied". When I first = encountered this I believe I chmod -R 777 * in the directory that the = file was untared in and that worked for me, but for some of my users who = are less experienced with freeBSD won't know how and don't know how to = resolve this and it shouldn't be happening in the first place. Other = users say they have gotten the error and simply logged out and back in = and resolved it. Anyone have any ideas what is causing this and how to fix it? Thanks -Brad