When updating from v1.0.0 Frontier to v1.0.1 Thawing, I can no longer connect via ipc. Is the file now created in a different location other than $datadir/geth.ipc`
$ geth.exe --datadir ./eth --ipcapi "eth,personal" --ipcpath './eth/geth.ipc'
...
$ Fatal: Error string IPC: Invalid pipe address '$datadir\geth.ipc'.
When not providing ipcpath:
$ geth.exe --datadir ./eth --ipcapi "eth,personal"
...
$ I0806 11:14:42.633121 16872 ipc_windows.go:696] IPC service started (\\.\pipe\geth.ipc)
$ geth.exe attach ipc:$datadir/geth.ipc
...
$ Fatal: Unable to attach to geth node - Invalid pipe address '$datadir\geth.ipc'.
Where is it? its not in $datapath/geth.ipc, but when do the following it works.
$ geth.exe attach ipc:\\.\pipe\geth.ipc
instance: Geth/v1.0.1/windows/go1.4.2
datadir: eth
coinbase: null
at block: 0 (1970-01-01 00:00:00)
modules: admin:1.0 db:1.0 debug:1.0 eth:1.0 miner:1.0 net:1.0 personal:1.0 shh:1.0 txpool:1.0 web3:1.0
>
Where is the geth.ipc file on a windows filesystem, relative to $datadir?
Wow:
web3.setProvider( new web3.providers.IpcProvider( '\\\\.\\pipe\\geth.ipc' ) )
^^^^^
Works now, but I'd like to understand where this file is, I can't find it.
It is a named pipe. There is no file.
See Wikipedia for more information about named pipes and the feature-laden support for them on Windows.
haha thanks :O
Most helpful comment
See Wikipedia for more information about named pipes and the feature-laden support for them on Windows.