Named Pipe is not created – Listener example missing in documentation

[TorbenHammes]

I am experiencing an issue when using named pipes with the interprocess library. In my code, I define the pipe as follows:

const PIPE_NAME: &str = r"\\.\pipe\netcommander_pipe";

let listener = PipeListenerOptions::new()
    .path(PIPE_NAME)
    .create::<pipe_mode::Bytes, pipe_mode::Bytes>()
    .expect("Failed to create the named pipe");

However, when starting the service, I receive the error:
Os { code: 2, kind: NotFound, message: "The system cannot find the file specified." }

Problem
I suspect that the error might be related to permission issues or timing problems during the initialization of the pipe. I have limited experience with named pipes, so I haven’t found much useful information on this topic. Additionally, I noticed that the example for the listener in the interprocess documentation is currently empty and is only planned for version 2.3.

Questions / Expected Assistance

• Are there any known limitations or common issues when creating named pipes in a Windows service context?
• How can I ensure that the pipe server is fully initialized before clients attempt to connect?
• Are there any workarounds or alternative libraries that provide better support for this scenario?
• Could adjusting security attributes or running the service with elevated privileges resolve this issue?

I appreciate any guidance or solutions, as I am currently stuck due to my limited experience with named pipes.

Thank you in advance!

Best regards,
Torben

[rgbav]

I also ran into this issue

[TorbenHammes]

I managed to get it to run as a Windows service. It was due to the authorizations of the service. Unfortunately, I can't access it with a programme that runs as a scheduled task (same error). This may not necessarily belong here, but as I am not really familiar with the authorisations, perhaps you can help me.

[kotauskas]

The example is now present as of 79ac92c. Not sure what the deal is with the security attributes, though. You can use the .security_descriptor() method to create the named pipe with non-default permissions.