This is the mail archive of the
mailing list for the Cygwin project.
Re: Patch to pass file descriptors
> "Corinna Vinschen" <firstname.lastname@example.org> wrote:
> > Basically, I don't like that sshd might depend on a running
> > If the implementation only works with a server process as for SysV
> > memory, that's ok. But if it's possible to get that working w/o
> > cygserver, I'd prefer that.
"Robert Collins" <email@example.com> wrote:
> Ahh, well what about doing both, like we do with the tty handle
> code. A secure version for when cygserver is running, and the
> version for when cygserver isn't running.
Corinna's point raises the issue of what the future of cygserver is
expected to be in Cygwin. Is it going to be installed by default, with
programs being able to rely on it without question? or, as seems to be
the attitude at the moment, is it going to remain an optional add-on,
only run by those who need its "special" services?
I can see that it might well raise the complexity level of the setup
program (apart from anything else) if Cygwin installs a service as
part of the default installation (i.e. setup then has to stop the
service before updating the DLL and then has to re-start the service
or prompt the user to re-start their machine). But are there any other
reasons why we wouldn't want cygserver to be a standard part of every