Re: fcntl always fails to delete lock file, and PID is always -6464

2010-10-11 Thread Daichi GOTO
Sent from my iPad On Oct 11, 2010, at 5:50 PM, John Baldwin 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? Or kee

Re: fcntl always fails to delete lock file, and PID is always -6464

2010-10-11 Thread John Baldwin
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.

Re: fcntl always fails to delete lock file, and PID is always -6464

2010-10-07 Thread Daichi GOTO
On Oct 5, 2010, at 7:09 PM, Garrett Cooper wrote: > On Tue, Oct 5, 2010 at 8:58 AM, Garrett Cooper wrote: >> On Tue, Oct 5, 2010 at 7:52 AM, Garrett Cooper wrote: >>> On Tue, Oct 5, 2010 at 1:55 AM, Daichi GOTO wrote: On Tue, 5 Oct 2010 01:23:02 -0700 Garrett Cooper wrote: > 2010/

Re: fcntl always fails to delete lock file, and PID is always -6464

2010-10-07 Thread Daichi GOTO
On Oct 5, 2010, at 4:52 PM, Garrett Cooper wrote: > On Tue, Oct 5, 2010 at 1:55 AM, Daichi GOTO wrote: >> 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 201

Re: fcntl always fails to delete lock file, and PID is always -6464

2010-10-05 Thread Garrett Cooper
On Tue, Oct 5, 2010 at 8:58 AM, Garrett Cooper wrote: > On Tue, Oct 5, 2010 at 7:52 AM, Garrett Cooper wrote: >> On Tue, Oct 5, 2010 at 1:55 AM, Daichi GOTO wrote: >>> On Tue, 5 Oct 2010 01:23:02 -0700 >>> Garrett Cooper wrote: 2010/10/4 Daichi GOTO : > Thanks nice test tool :)  And a

Re: fcntl always fails to delete lock file, and PID is always -6464

2010-10-05 Thread Garrett Cooper
On Tue, Oct 5, 2010 at 7:52 AM, Garrett Cooper wrote: > On Tue, Oct 5, 2010 at 1:55 AM, Daichi GOTO wrote: >> 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 O

Re: fcntl always fails to delete lock file, and PID is always -6464

2010-10-05 Thread Garrett Cooper
On Tue, Oct 5, 2010 at 1:55 AM, Daichi GOTO wrote: > 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: >> >> Follow

Re: fcntl always fails to delete lock file, and PID is always -6464

2010-10-05 Thread Daichi GOTO
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:

Re: fcntl always fails to delete lock file, and PID is always -6464

2010-10-05 Thread Garrett Cooper
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

Re: fcntl always fails to delete lock file, and PID is always -6464

2010-10-04 Thread Daichi GOTO
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 wrote: > test_fcntl

Re: fcntl always fails to delete lock file, and PID is always -6464

2010-10-04 Thread 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: >

Re: fcntl always fails to delete lock file, and PID is always -6464

2010-10-04 Thread Garrett Cooper
On Mon, Oct 4, 2010 at 5:38 PM, Daichi GOTO wrote: > On Mon, 4 Oct 2010 07:19:45 -0700 > Garrett Cooper 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. >> >>     Pro

Re: fcntl always fails to delete lock file, and PID is always -6464

2010-10-04 Thread Daichi GOTO
On Mon, 4 Oct 2010 07:19:45 -0700 Garrett Cooper 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 and the >

Re: fcntl always fails to delete lock file, and PID is always -6464

2010-10-04 Thread Garrett Cooper
On Sun, Oct 3, 2010 at 10:05 PM, Garrett Cooper wrote: > On Sun, Oct 3, 2010 at 8:37 PM, Daichi GOTO 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".

Re: fcntl always fails to delete lock file, and PID is always -6464

2010-10-04 Thread Garrett Cooper
On Sun, Oct 3, 2010 at 8:37 PM, Daichi GOTO 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: >    http://code.google.com/p/mozc/issue

Re: fcntl always fails to delete lock file, and PID is always -6464

2010-10-04 Thread Daichi GOTO
On Sun, 3 Oct 2010 22:05:12 -0700 Garrett Cooper wrote: > On Sun, Oct 3, 2010 at 8:37 PM, Daichi GOTO 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 "moz

fcntl always fails to delete lock file, and PID is always -6464

2010-10-03 Thread Daichi GOTO
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 9.0-