Hi All, I'm attaching a bit of strace from a slow save here. I'm afraid I don't really know what I'm looking at. Does it suggest anything that might be wrong? thanks, Nigel On 25 February 2014 00:09, Ross Reedstrom <reedstrm@rice.edu> wrote: > Gimp does more disk work than most apps, in order to handle editting very > large images. It maintains a cache of blocks, usualy in the user's homedir, > so NFS issues are a likely target. strace is often your friend for this sort > of thing. > > Ross > -- > Ross Reedstrom > > > On Fri, Feb 21, 2014 at 12:12:23PM +0100, Petter Reinholdtsen wrote: >> [Nigel Barker] >> > Does anyone have a good suggestion? >> >> I would suggest running 'strace -p <pidofgimp>' to see what gimp is >> doing when gimp is slow to save, and 'tcptrace' to see if there is >> something network wise going on. No experience in what the problem >> could be. Perhaps it is NFS locking related? >> >> -- >> Happy hacking >> Petter Reinholdtsen >> >> >> -- >> To UNSUBSCRIBE, email to debian-edu-REQUEST@lists.debian.org >> with a subject of "unsubscribe". Trouble? Contact listmaster@lists.debian.org >> Archive: http://lists.debian.org/20140221111223.GA5766@diskless.uio.no >> >> > > > -- > To UNSUBSCRIBE, email to debian-edu-REQUEST@lists.debian.org > with a subject of "unsubscribe". Trouble? Contact listmaster@lists.debian.org > Archive: http://lists.debian.org/20140224150928.GA28302@rice.edu >
Attachment:
gimpstrace
Description: Binary data