[c-nsp] Copying new IOS to 7600 resulting in IPC logs

[frnkblk at iname.com]

While SCPing a new IOS release to our 7609-S (RSP720C) yestseday morning I
was getting alerts about high CPU and SNMP was occasionally timing out, but
last night when I copied files over from disk0 to other locations
(supbootdisk, etc) I got some of these log entries:

Apr 27 22:36:11 199.120.69.254 65663987: Apr 27 22:36:10.875 CDT:
%IPC-5-WATERMARK: 834 messages pending in rcv for the port (2150000.0) from
source seat 10000,
Apr 27 22:36:11 199.120.69.254 65663988:        
Apr 27 22:36:41 199.120.69.254 65664004: Apr 27 22:36:40.951 CDT:
%IPC-5-WATERMARK: 953 messages pending in rcv for the port (2150000.0) from
source seat 10000,
Apr 27 22:36:41 199.120.69.254 65664005:        
Apr 27 22:37:11 199.120.69.254 65664024: Apr 27 22:37:11.039 CDT:
%IPC-5-WATERMARK: 1033 messages pending in rcv for the port (2150000.0) from
source seat 10000,
Apr 27 22:37:11 199.120.69.254 65664025:        
Apr 27 22:37:41 199.120.69.254 65664041: Apr 27 22:37:41.231 CDT:
%IPC-5-WATERMARK: 1171 messages pending in rcv for the port (2150000.0) from
source seat 10000,
Apr 27 22:37:41 199.120.69.254 65664042:        
Apr 27 22:38:11 199.120.69.254 65664061: Apr 27 22:38:11.347 CDT:
%IPC-5-WATERMARK: 1248 messages pending in rcv for the port (2150000.0) from
source seat 2010000,
Apr 27 22:38:11 199.120.69.254 65664062:        
Apr 27 22:38:41 199.120.69.254 65664080: Apr 27 22:38:41.491 CDT:
%IPC-5-WATERMARK: 1368 messages pending in rcv for the port (2150000.0) from
source seat 10000,
Apr 27 22:38:41 199.120.69.254 65664081:        
Apr 27 22:39:12 199.120.69.254 65664101: Apr 27 22:39:11.502 CDT:
%IPC-5-WATERMARK: 1472 messages pending in rcv for the port (2150000.0) from
source seat 10000,
Apr 27 22:39:12 199.120.69.254 65664102:        
Apr 27 22:39:42 199.120.69.254 65664117: Apr 27 22:39:41.574 CDT:
%IPC-5-WATERMARK: 1560 messages pending in rcv for the port (2150000.0) from
source seat 10000,
Apr 27 22:39:42 199.120.69.254 65664118:        

Is there any way to "nice" the copy process so it doesn't impact the system
so much?

Frank