From owner-freebsd-current@FreeBSD.ORG Tue Oct 5 08:55:37 2010 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 2C4D8106566C; Tue, 5 Oct 2010 08:55:37 +0000 (UTC) (envelope-from daichi@ongs.co.jp) Received: from natial.ongs.co.jp (natial.ongs.co.jp [202.216.246.90]) by mx1.freebsd.org (Postfix) with ESMTP id E94888FC29; Tue, 5 Oct 2010 08:55:36 +0000 (UTC) Received: from parancell.ongs.co.jp (dullmdaler.ongs.co.jp [202.216.246.94]) by natial.ongs.co.jp (Postfix) with ESMTPSA id 2369412543B; Tue, 5 Oct 2010 17:55:36 +0900 (JST) Date: Tue, 5 Oct 2010 17:55:36 +0900 From: Daichi GOTO To: Garrett Cooper Message-Id: <20101005175536.a67998ae.daichi@ongs.co.jp> In-Reply-To: References: <20101004123725.65d09b9e.daichi@ongs.co.jp> <20101004144927.36822f07.daichi@ongs.co.jp> <20101005093826.17432b1e.daichi@ongs.co.jp> <20101005153410.598e4484.daichi@ongs.co.jp> Organization: ONGS Inc. X-Mailer: Sylpheed 3.0.3 (GTK+ 2.20.1; amd64-portbld-freebsd9.0) Mime-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit Cc: freebsd-fs@freebsd.org, freebsd-current@freebsd.org Subject: Re: fcntl always fails to delete lock file, and PID is always -6464 X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 05 Oct 2010 08:55:37 -0000 On Tue, 5 Oct 2010 01:23:02 -0700 Garrett Cooper wrote: > 2010/10/4 Daichi GOTO : > > Thanks nice test tool :)  And at last I got it excepting one mystery! > > > > On Mon, 4 Oct 2010 20:17:08 -0700 > > Garrett Cooper wrote: > >> Following through the same process on FreeBSD... > >> > >> Window 1: > >> $ ls -l /tmp/lockfile > >> ls: /tmp/lockfile: No such file or directory > >> $ ./test_fcntl > >> > >> Window 2: > >> > >> $ ls -l /tmp/lockfile > >> -rwsr-x---  1 garrcoop  wheel  0 Oct  4 20:14 /tmp/lockfile > >> $ ./test_fcntl > >> test_fcntl: fcntl: Resource temporarily unavailable > > > > Just my mystery is as follow: > > > > Windows 1: > > % ./test_fcntl > > My pid: 43490 > > > > Windows 2: > > % ls -l /tmp/lockfile > > -r-sr-x---  1 daichi  wheel  0 10月  5 15:02 /tmp/lockfile    <--- is it weird, isn't it? > > % ./test_fcntl > > test_fcntl: open: Permission denied > > % > > > > Oops... What's wrong... /tmp is as follow: > > > > % mount | grep tmp > > /dev/ada0s1f on /tmp (ufs, local, noatime, soft-updates) > > % dumpfs /tmp | grep journal > > flags   soft-updates+journal > > % > > > > And working scene: > > > > Windows 2: > > % chmod u+w /tmp/lockfile > > % ls -l /tmp/lockfile > > -rwsr-x---  1 daichi  wheel  0 10月  5 15:22 /tmp/lockfile > > % ./test_fcntl > > My pid: 43646 > > test_fcntl: fcntl[1]: Resource temporarily unavailable > > PID=43490 has the lock > > % > > What's your umask and what are the permissions on /tmp? % ll / | grep tmp drwxrwxrwt 14 root wheel 1024 10月 5 17:19 tmp % umask 022 % rm -f test % touch test % ll | grep test -rw-r--r-- 1 daichi wheel 0 10月 5 17:52 test %