> On 22 Jul 2016, at 9:22 AM, Uli Kusterer wrote:
>
> On 21 Jul 2016, at 17:20, Graham Cox wrote:
>> One of my apps uses NSTask to wrap a command line utility that is embedded
>> in the same app’s resources. This utility writes files to disk - I have no
>> knowledge of which APIs it uses to d
> On 22 Jul 2016, at 8:22, Uli Kusterer wrote:
>
> On 21 Jul 2016, at 17:20, Graham Cox wrote:
>> One of my apps uses NSTask to wrap a command line utility that is embedded
>> in the same app’s resources. This utility writes files to disk - I have no
>> knowledge of which APIs it uses to do t
On 21 Jul 2016, at 17:20, Graham Cox wrote:
> One of my apps uses NSTask to wrap a command line utility that is embedded in
> the same app’s resources. This utility writes files to disk - I have no
> knowledge of which APIs it uses to do this. If the task has ended (and I can
> see that the act
Do you have any NSPipes or NSFileHandles set on the NSTask’s I/O channels?
(standardOutput, standardError, and standardInput)
Dan
> On Jul 21, 2016, at 8:20 AM, Graham Cox wrote:
>
> One of my apps uses NSTask to wrap a command line utility that is embedded in
> the same app’s resources. This
That’s strange. I would use the `lsof` tool to figure out which process has
that file open. You can also use `fs_usage` while the tool is running to
monitor all the filesystem activity on that file.
—Jens
___
Cocoa-dev mailing list (Cocoa-dev@lists.ap
One of my apps uses NSTask to wrap a command line utility that is embedded in
the same app’s resources. This utility writes files to disk - I have no
knowledge of which APIs it uses to do this. If the task has ended (and I can
see that the actual instance of the running command line tool has dis
