From owner-freebsd-ports@FreeBSD.ORG Mon May 20 15:53:31 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 E92ACBE8 for ; Mon, 20 May 2013 15:53:31 +0000 (UTC) (envelope-from sindrome@gmail.com) Received: from mail-ia0-x22b.google.com (mail-ia0-x22b.google.com [IPv6:2607:f8b0:4001:c02::22b]) by mx1.freebsd.org (Postfix) with ESMTP id BBC531FF for ; Mon, 20 May 2013 15:53:31 +0000 (UTC) Received: by mail-ia0-f171.google.com with SMTP id m19so1440091iah.16 for ; Mon, 20 May 2013 08:53:31 -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=eOAr0besXxI90y93JYiH0onGrIRco9ZYxGgW3Ae1s6U=; b=CUMJVECMSidULiz+nCvhSrxdrCvzDs32/5Mem+4AOC8iglSPyGZAwUIEikoQ/3A/DM tUUs7T6Tnveor65n/Xu8ClkOkIR+l3XXEnwoXYRQyiQ/Y6mFp8khxZA0BLeOCdyFiRHh PGhn4Bm5Y7cwuDwNKGxDRplO1jtksdFj9eFM1SBuM8BUL9RFEcSI6W0/SngCSFJs7P28 DdTeitXsanR48VjUdonUOXW9DRterIMZAbvU5OQqK3DIGWtyMePYah1m/q+rO42yLOa9 uw10EXBPgV9E+iIEfToB2ZLwzQxi8kx9clHuG8SC1j9m7JUAeL3MK8yGDkEmxCc+qsaB 3DBA== MIME-Version: 1.0 X-Received: by 10.42.196.202 with SMTP id eh10mr13738831icb.44.1369065211398; Mon, 20 May 2013 08:53:31 -0700 (PDT) Received: by 10.64.235.172 with HTTP; Mon, 20 May 2013 08:53:31 -0700 (PDT) In-Reply-To: <20130520221927.0a2e37b9@X220.ovitrap.com> References: <8661yedqyy.wl%poyopoyo@puripuri.plala.or.jp> <20130520143853.79242743@raksha.tavi.co.uk> <20130520221927.0a2e37b9@X220.ovitrap.com> Date: Mon, 20 May 2013 10:53:31 -0500 Message-ID: Subject: Re: Why does Samba requires 777 permissions on /tmp From: sindrome To: Erich Dollansky Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable X-Content-Filtered-By: Mailman/MimeDel 2.1.14 Cc: Bob Eager , FreeBSD Mailing List 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 15:53:32 -0000 echo $PATH /bin:/usr/lib:/sbin:/usr/bin:/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/= local/lib32/compat:/usr/X11R6/bin:/home/sindrome/.gnupg:/home/sindrome/bin:= /home/sindrome/docs:/home/sindrome/docs/info:/home/sindrome/docs/config:/sb= in:/bin:/etc:/usr/local/etc::/usr/bin:/usr/games:/usr/local/sbin:/usr/local= /bin:/usr/X11R6/bin:. On Mon, May 20, 2013 at 10:19 AM, Erich Dollansky < erichsfreebsdlist@alogt.com> wrote: > Hi, > > On Mon, 20 May 2013 14:38:53 +0100 > Bob Eager wrote: > > > On Mon, 20 May 2013 08:03:09 -0500 > > sindrome wrote: > > > > > Looks like a step in the right direction. How do I troubleshoot to > > > figure out what application is appending/changing the value of PATH? > > > > Nothing is. As far as I can see. > > > > What I think is happening is that portupgrade is building and running > > shell scripts in /tmp. It's running them with (in ruby): > > > the error message comes from a line like this: > > > system('/tmp/script') [roughly] > > > I do not know Ruby. But I am sure that there is somebody here who is > able to tell the original writer what to insert to get the command to > be executed to be printed. Then we will see what it is. > > Erich > _______________________________________________ > 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" >