Problems with command line scratch files in zsh
cblack at securecrossing.com
Sun Jun 12 20:42:28 GMT 2005
Why not just 'cat /etc/motd | wc' ?
On Sun, 2005-06-12 at 03:31 -0500, Mike Meyer wrote:
> Since going to 5.x with devfd, I've noticed that some of the shell
> constructs used by zsh (and other shells - I know zsh didn't invent
> this) quit working. To wit:
> guru% wc <(cat /etc/motd)
> wc: /dev/fd/11: open: No such file or directory
> The <(...) construct runs the pipe in (), and replaces the <(...) with
> the name of the /dev/fd/ entry for the output of that pipe. The file
> exists for the shell process doing all this. But when the comm process
> tries to open the file to read the data, the file doesn't exist. This
> is pretty nasty.
> Anyone got any suggestions on how to fix this? A bug report with a
> patch, maybe (I couldn't find any such bug report)? Workarounds? Maybe
> this should go to hackers at freebsd.org?
Chief Security Engineer
22750 Woodward Suite 304 - Ferndale, MI 48220
Tel (800) 761-4299 | Direct (248) 658-6120
cblack at securecrossing.com | www.securecrossing.com
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Size: 187 bytes
Desc: This is a digitally signed message part
Url : http://lists.freebsd.org/pipermail/freebsd-questions/attachments/20050612/d2168eaa/attachment.bin
More information about the freebsd-questions