Skip site navigation (1)Skip section navigation (2)
Date:      Fri, 17 Jul 2009 10:20:33 -0400 (EDT)
From:      Rick Macklem <rmacklem@uoguelph.ca>
To:        Kostik Belousov <kostikbel@gmail.com>
Cc:        Anonymous <swell.k@gmail.com>, Rick Macklem <rmacklem@freebsd.org>, freebsd-current@freebsd.org
Subject:   Re: [newnfs/client] SIGINFO aborts transfer and produces `permission denied'
Message-ID:  <Pine.GSO.4.63.0907171016450.28363@muncher.cs.uoguelph.ca>
In-Reply-To: <20090717081105.GQ55190@deviant.kiev.zoral.com.ua>
References:  <86zlb45px8.fsf@gmail.com> <Pine.GSO.4.63.0907162013570.9851@muncher.cs.uoguelph.ca> <20090717081105.GQ55190@deviant.kiev.zoral.com.ua>

next in thread | previous in thread | raw e-mail | index | archive | help


On Fri, 17 Jul 2009, Kostik Belousov wrote:

> On Thu, Jul 16, 2009 at 08:15:29PM -0400, Rick Macklem wrote:
>>
>>
>> On Fri, 17 Jul 2009, Anonymous wrote:
>>
>>> Let's populate /blah with 50Mb files and send SIGINFO to cp(1) process
>>> while
>>> copying it over nfsv3.
>>>
>>> # uname -vm
>>> FreeBSD 8.0-BETA1 #0: Sat Jul 4 03:55:14 UTC 2009
>>> root@almeida.cse.buffalo.edu:/usr/obj/usr/src/sys/GENERIC i386
>>>
Ah, my commit related to blocking signals (cloned from the regular
nfs client) didn't go into head until Jul 12 (r195642), so I think
this might be fixed by that.

If you still see it when running a post-r195642 kernel, please let
me know, rick

>>>
>> Kostik recently checked in some changes related to signal handling,
>> but I haven't yet had time to clone that for the experimental client.
> The changes I did should only affect SIGSTOP.
>
Yea, I knew that;-) But didn't think of it when I replied the first
time, rick




Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?Pine.GSO.4.63.0907171016450.28363>