Re: Determining the size of a directory Part 2
Re: Determining the size of a directory Part 2
- Subject: Re: Determining the size of a directory Part 2
- From: Dominik Freyer <email@hidden>
- Date: Mon, 25 Oct 2004 15:48:24 +0200
- Resent-date: Mon, 25 Oct 2004 16:10:12 +0200
- Resent-from: Dominik Freyer <email@hidden>
- Resent-message-id: <email@hidden>
- Resent-to: email@hidden
Use the POSIX API?
@stephane: Can I simply call this method out of Cocoa?
@andreas:
Hi Dominik,
I guess you should connect the output file handle of 'fromPipe' (as
returned by fileHandleForWriting), and not its input file handle, to
the standard output of 'duTool'. Then you can use 'fromDu' to read
data from the pipe.
Ok, i changed it to this:
args = [NSArray arrayWithObjects:@"-ks",path,nil];
fromPipe=[NSPipe pipe];
// fromDu=[[NSFileHandle alloc]init];
fromDu=[fromPipe fileHandleForWriting];
NSTask *duTool=[[NSTask alloc]init];
Did you talk of this? And is the memory leak now repaired?
By the way you're leaking memory in the following code:
fromDu=[[NSFileHandle alloc]init];
fromDu=[fromPipe fileHandleForReading];
And releasing 'duTool' and 'poolForSize' after returning won't be very
helpful:
return (unsigned long long)output;
[duTool release];
[poolForSize release];
Ok, I put it before the return, hope this helps.
Anyway, I'm getting a *** Uncaught exception:
<NSFileHandleOperationException> *** -[NSConcreteFileHandle
readDataOfLength:]: Bad file descriptor
I'm now using readDataToEndOfFile
@Finley: I'm not using fts because I didn't know about it. :-) Do I
loose something when using du instead of fts?
Thanks for all your fast responses
Dominik
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Cocoa-dev mailing list (email@hidden)
Help/Unsubscribe/Update your Subscription:
This email sent to email@hidden