From owner-freebsd-ports@FreeBSD.ORG Mon May 20 16:45:09 2013 Return-Path: Delivered-To: freebsd-ports@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by hub.freebsd.org (Postfix) with ESMTP id 81981A0F for ; Mon, 20 May 2013 16:45:09 +0000 (UTC) (envelope-from sindrome@gmail.com) Received: from mail-ie0-x236.google.com (mail-ie0-x236.google.com [IPv6:2607:f8b0:4001:c03::236]) by mx1.freebsd.org (Postfix) with ESMTP id 505DE63D for ; Mon, 20 May 2013 16:45:09 +0000 (UTC) Received: by mail-ie0-f182.google.com with SMTP id a14so14249928iee.41 for ; Mon, 20 May 2013 09:45:09 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:x-received:in-reply-to:references:date:message-id :subject:from:to:cc:content-type; bh=jmJGQ9F8vYLJXzuh2MUQvwzap8CUjm9ssbs8GUJ1ODA=; b=ZLdvPdrcfjbp3cNJwKD/tNEXWXX+XtRVonhNw/NNzxfY3+5dkqdTie9vny8O3bTDxI 26bH/4PzwRETH2nvVZIbHzRj70BFCk3ruAplDr2KWa0uwUx6OXrna65s3EfTn/XEr1L3 MlO11r4O6hlCbC/O3m45QkwGim1EDpPqWc8fBiAlTsrSVE8He4v3R0uPecff0KjtuURO eVwRSJat0fxGMa1zJa+tcOrY+BCvYLXvWIFUihn5b0fJMrbmXW2Ol7+AzSIjUgj4lKLj nNJ9MvSPsOILCYTxwh12yNVykjBzuoKT+O0yfpVp2DyWIGr2+Adx9bwkrQ7BEM2N5PKQ 3QHA== MIME-Version: 1.0 X-Received: by 10.50.6.52 with SMTP id x20mr5672704igx.13.1369068309074; Mon, 20 May 2013 09:45:09 -0700 (PDT) Received: by 10.64.235.172 with HTTP; Mon, 20 May 2013 09:45:08 -0700 (PDT) In-Reply-To: References: <20130519115232.49f52d01@scorpio> <20130519195639.79464471@raksha.tavi.co.uk> <20130519151706.4d67afe5@scorpio> <20130519204753.GA47341@jmobile.jimmy.net> <20130519222232.13aa95c6@raksha.tavi.co.uk> <20130520122001.19368e34@X220.ovitrap.com> Date: Mon, 20 May 2013 11:45:08 -0500 Message-ID: Subject: Re: Why does Samba requires 777 permissions on /tmp From: sindrome To: Torfinn Ingolfsen Content-Type: text/plain; charset=ISO-8859-1 X-Content-Filtered-By: Mailman/MimeDel 2.1.14 Cc: FreeBSD Ports ML X-BeenThere: freebsd-ports@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: Porting software to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 20 May 2013 16:45:09 -0000 Clearly I'm not the only one with this problem. Something is amending onto the PATH and I'd like to get to the bottom of this. I'm sure it will help a lot of people. On Mon, May 20, 2013 at 11:39 AM, Torfinn Ingolfsen wrote: > On Mon, May 20, 2013 at 7:20 AM, Erich Dollansky > wrote: > > > > Could it be that we all got this message but did not bother because we > > get so many warnings during an upgrade? > > Nope. FWIW, portupgrade works without errors here. > > tingo@kg-v2$ uname -a > FreeBSD kg-v2.kg4.no 8.3-STABLE FreeBSD 8.3-STABLE #6: Fri Apr 27 > 23:50:55 CEST 2012 root@kg-v2.kg4.no:/usr/obj/usr/src/sys/GENERIC > amd64 > tingo@kg-v2$ portversion -v portupgrade* > portupgrade-2.4.10.5_1,2 = up-to-date with port > > HTH > -- > Regards, > Torfinn Ingolfsen > _______________________________________________ > freebsd-ports@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-ports > To unsubscribe, send any mail to "freebsd-ports-unsubscribe@freebsd.org" >