How to inspect named pipes in Unix and Windows?

The OpenOffice process can be started in two ways:

(1) Listening to a TCP socket
(2) Listening to a named pipe

The first method is very easy to inspect. In order to make sure that
things are correct, just use 'netstat -a' in both Unix and Windows.

My question pertains to the second method. The OpenOffice API has a
'Bootstrap' method which *presumably* starts the OO process in named
pipe mode (my guesstimate). How can I verify that such thing has
indeed occurred? I am told that Windows creates some '\\.\pipe' file.
Is is visible through the filesystem or only programmatically? How can
I see all the active (?) named pipes on a Unix and on a Windows
system?

TIA,

-Ramon

Ramon F Herrera wrote:
> The OpenOffice process can be started in two ways:
>
> (1) Listening to a TCP socket
> (2) Listening to a named pipe
>
> The first method is very easy to inspect. In order to make sure that
> things are correct, just use 'netstat -a' in both Unix and Windows.
>
> My question pertains to the second method. The OpenOffice API has a
> 'Bootstrap' method which *presumably* starts the OO process in named
> pipe mode (my guesstimate). How can I verify that such thing has
> indeed occurred? I am told that Windows creates some '\\.\pipe' file.
> Is is visible through the filesystem or only programmatically? How can
> I see all the active (?) named pipes on a Unix and on a Windows
> system?
>
> TIA,
>
> -Ramon
>

in Unix you can filter output from lsof
eg (in linux - read manual of lsof it can differ on different *Nix)

lsof -n -P | grep 'FIFO'

On Nov 24, 11:52 am, Ramon F Herrera <ra...@conexus.net> wrote:
> The OpenOffice process can be started in two ways:
>
> (1) Listening to a TCP socket
> (2) Listening to a named pipe
>
> The first method is very easy to inspect. In order to make sure that
> things are correct, just use 'netstat -a' in both Unix and Windows.
>
> My question pertains to the second method. The OpenOffice API has a
> 'Bootstrap' method which *presumably* starts the OO process in named
> pipe mode (my guesstimate). How can I verify that such thing has
> indeed occurred? I am told that Windows creates some '\\.\pipe' file.
> Is is visible through the filesystem or only programmatically? How can
> I see all the active (?) named pipes on a Unix and on a Windows
> system?
>
> TIA,
>
> -Ramon


System Information for Windows

http://www.gtopala.com/

-RFH