On Tuesday, October 05, 2010 2:39:26 am Daichi GOTO wrote:
Next step discussion engaged from this research I guess.
Should we do change FreeBSD's fcntl(2) to return correct l_pid
when called with F_SETLK? Or keep current behavior??
I want to hear other developers ideas and suggetions.
Sent from my iPad
On Oct 11, 2010, at 5:50 PM, John Baldwin j...@freebsd.org wrote:
On Tuesday, October 05, 2010 2:39:26 am Daichi GOTO wrote:
Next step discussion engaged from this research I guess.
Should we do change FreeBSD's fcntl(2) to return correct l_pid
when called with F_SETLK?
On Oct 5, 2010, at 4:52 PM, Garrett Cooper wrote:
On Tue, Oct 5, 2010 at 1:55 AM, Daichi GOTO dai...@ongs.co.jp wrote:
On Tue, 5 Oct 2010 01:23:02 -0700
Garrett Cooper gcoo...@freebsd.org wrote:
2010/10/4 Daichi GOTO dai...@ongs.co.jp:
Thanks nice test tool :) And at last I got it excepting
On Oct 5, 2010, at 7:09 PM, Garrett Cooper wrote:
On Tue, Oct 5, 2010 at 8:58 AM, Garrett Cooper gcoo...@freebsd.org wrote:
On Tue, Oct 5, 2010 at 7:52 AM, Garrett Cooper gcoo...@freebsd.org wrote:
On Tue, Oct 5, 2010 at 1:55 AM, Daichi GOTO dai...@ongs.co.jp wrote:
On Tue, 5 Oct 2010 01:23:02
Thanks nice test tool :) And at last I got it excepting one mystery!
On Mon, 4 Oct 2010 20:17:08 -0700
Garrett Cooper gcoo...@freebsd.org wrote:
Following through the same process on FreeBSD...
Window 1:
$ ls -l /tmp/lockfile
ls: /tmp/lockfile: No such file or directory
$ ./test_fcntl
Next step discussion engaged from this research I guess.
Should we do change FreeBSD's fcntl(2) to return correct l_pid
when called with F_SETLK? Or keep current behavior??
I want to hear other developers ideas and suggetions.
On Mon, 4 Oct 2010 20:17:08 -0700
Garrett Cooper gcoo...@freebsd.org
2010/10/4 Daichi GOTO dai...@ongs.co.jp:
Thanks nice test tool :) And at last I got it excepting one mystery!
On Mon, 4 Oct 2010 20:17:08 -0700
Garrett Cooper gcoo...@freebsd.org wrote:
Following through the same process on FreeBSD...
Window 1:
$ ls -l /tmp/lockfile
ls: /tmp/lockfile: No
On Tue, 5 Oct 2010 01:23:02 -0700
Garrett Cooper gcoo...@freebsd.org wrote:
2010/10/4 Daichi GOTO dai...@ongs.co.jp:
Thanks nice test tool :) And at last I got it excepting one mystery!
On Mon, 4 Oct 2010 20:17:08 -0700
Garrett Cooper gcoo...@freebsd.org wrote:
Following through the
On Tue, Oct 5, 2010 at 1:55 AM, Daichi GOTO dai...@ongs.co.jp wrote:
On Tue, 5 Oct 2010 01:23:02 -0700
Garrett Cooper gcoo...@freebsd.org wrote:
2010/10/4 Daichi GOTO dai...@ongs.co.jp:
Thanks nice test tool :) And at last I got it excepting one mystery!
On Mon, 4 Oct 2010 20:17:08 -0700
On Tue, Oct 5, 2010 at 7:52 AM, Garrett Cooper gcoo...@freebsd.org wrote:
On Tue, Oct 5, 2010 at 1:55 AM, Daichi GOTO dai...@ongs.co.jp wrote:
On Tue, 5 Oct 2010 01:23:02 -0700
Garrett Cooper gcoo...@freebsd.org wrote:
2010/10/4 Daichi GOTO dai...@ongs.co.jp:
Thanks nice test tool :) And at
On Tue, Oct 5, 2010 at 8:58 AM, Garrett Cooper gcoo...@freebsd.org wrote:
On Tue, Oct 5, 2010 at 7:52 AM, Garrett Cooper gcoo...@freebsd.org wrote:
On Tue, Oct 5, 2010 at 1:55 AM, Daichi GOTO dai...@ongs.co.jp wrote:
On Tue, 5 Oct 2010 01:23:02 -0700
Garrett Cooper gcoo...@freebsd.org wrote:
On Sun, 3 Oct 2010 22:05:12 -0700
Garrett Cooper gcoo...@freebsd.org wrote:
On Sun, Oct 3, 2010 at 8:37 PM, Daichi GOTO dai...@ongs.co.jp wrote:
It looks very strange. fcntl() always fails to delete lock file
and command.l_pid is always -6464. This issue is disclosed in
porting Google's
On Sun, Oct 3, 2010 at 10:05 PM, Garrett Cooper gcoo...@freebsd.org wrote:
On Sun, Oct 3, 2010 at 8:37 PM, Daichi GOTO dai...@ongs.co.jp wrote:
It looks very strange. fcntl() always fails to delete lock file
and command.l_pid is always -6464. This issue is disclosed in
porting Google's
On Sun, Oct 3, 2010 at 8:37 PM, Daichi GOTO dai...@ongs.co.jp wrote:
It looks very strange. fcntl() always fails to delete lock file
and command.l_pid is always -6464. This issue is disclosed in
porting Google's Japanese input system called mozc.
details follow:
On Mon, 4 Oct 2010 07:19:45 -0700
Garrett Cooper gcoo...@freebsd.org wrote:
issues that might be occurring with the software, as per my copy of
SUSv4 (see the ERRORS section of fcntl). I would print out the
strerror for that case.
Providing a backtrace of the application's execution
On Mon, Oct 4, 2010 at 5:38 PM, Daichi GOTO dai...@ongs.co.jp wrote:
On Mon, 4 Oct 2010 07:19:45 -0700
Garrett Cooper gcoo...@freebsd.org wrote:
issues that might be occurring with the software, as per my copy of
SUSv4 (see the ERRORS section of fcntl). I would print out the
strerror for
It looks very strange. fcntl() always fails to delete lock file
and command.l_pid is always -6464. This issue is disclosed in
porting Google's Japanese input system called mozc.
details follow:
http://code.google.com/p/mozc/issues/detail?id=40
% uname -a
FreeBSD parancell.ongs.co.jp
17 matches
Mail list logo
