patch for cygserver
Wed Aug 21 04:23:00 GMT 2002
"Joshua Daniel Franklin" <email@example.com> wrote:
> In my personal opinion, all of the exe's in the cygwin package
> should support (at a minimum) the GNU --help and --version
> With that in mind, here is a patch for cygserver.cc that
Thanks for the heads up Joshua, but your good work in this area
had already prompted me into action: the relevant changelog entry
2002-06-16 Conrad Scott <firstname.lastname@example.org>
(print_usage): New function.
(print_version): Ditto (tip of the hat to Joshua Daniel Franklin
for inspiration here).
(main): More argument checking. Add --help and --version
Note: all the current work on cygserver is happening on the
cygwin_daemon branch (and it's not really happening just now since
I've been fiddling around with the socket code for the last couple
of weeks) so this has yet to reach the real world.
> AFAIK there is absolutely
> no documentation (other than the mailing list) for cygserver. I
> happy to create some if someone could give me a good rundown of
> all is/is not supported at this time. Unfortunately my limited
> of IPC might make this more trouble than it is worth.
You're right about the documentation for cygserver: all I've seen
is from the mailing list. I'd imagine that there won't need to be
much documentation written for it (at least, not for the IPC
services) since the basic idea will be that if it is running, then
you get the SysV IPC services, and otherwise not. And it will
need to run under a privileged account and probably as a service
eventually for those who want it. Other than that, unless some
configuration is required, that is all there will be to it.
The cygipc package from Chuck Wilson is equivalent to the
cygserver (at least as far as IPC is concerned) and there is a
pretty full README file provided with that, so it might be a place
to look. For documentation of the IPC calls themselves, the
package includes a chunk of Linux documentation, which is close
enough (I use the SUSv3 documentation mostly) for all the msg*,
sem* and shm* system calls. There are also the ipcs and ipcrm
utilities that would need to be documented: the current (long
term) plan is for these to end up in the cygutils package.
My current idea is that the next merge of the cygserver code into
the mainline should be sufficient to replace the cygipc server; I
don't see any reason to take any half-steps before that. This
will require a full implementation of the SysV IPC services
sufficient to get all the current cygwin users of cygipc working
(i.e., postgresql). So sometime before that, documentation will
be needed along with a few other things.
More information about the Cygwin-patches