Re: [newnfs/client] SIGINFO aborts transfer and produces `permission denied'

From: Rick Macklem <rmacklem_at_uoguelph.ca>
Date: Fri, 17 Jul 2009 10:20:33 -0400 (EDT)
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_at_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
Received on Fri Jul 17 2009 - 12:17:34 UTC

This archive was generated by hypermail 2.4.0 : Wed May 19 2021 - 11:39:52 UTC