Diff & Named pipes in OSX?

previously I wrote about using named pipes to avoid temporary files when working from the CLI. The odd thing is that the following command seems to work on bash/linux but responds with an error message (curl: (23) Failed writing body) on bash/OSX

diff <(curl http://www.google.com) <(curl http://www.google.com?q=a)

I don’t really understand why this doesn’t work, but it seems that to the process the pipes differ from the default stdout where they shouldn’t. To bad, it would be useful!

update

While googling arround I found a page breaking down the problem. Greg Miller discovered that the actual problem is HFS+ (the filesystem) returning the same inode number for two different files; which since it isn’t inode base could be somehow correct.

Hopefully Apple will fix this in the near future, but I guess I’d better grab myself the sources and build my own version of diff.


0 Responses to “Diff & Named pipes in OSX?”

  1. No Comments

Leave a Reply





About

Welcome to the weblog of Peter Maas. Here you'll find various posts related to stuff I like (like my kids and espresso) and stuff I do (like developing software).

JavaOne 2008 Pictures

bonte specht IMG_6149 sfeervolverlichte boot Slippery Surface warm_en_koud sjoerd_met_koffer Stretched Limo IMG_4618.JPG War Room - Diagrams plant Cable Car line Danielle op de bruggen van Beeld en Geluid zed shaw tarte tatin of red unions espresso IMG_4684.JPG golden_gate_warning_sign italian_chef maan alcatraz
View more photos >

Categories



Meld u aan voor PayPal en begin direct met het accepteren van creditcardbetalingen.