Egor's daemon

Robert Collins
Wed Sep 12 15:24:00 GMT 2001

On Thu, 2001-09-13 at 02:13, Christopher Faylor wrote:
> On Thu, Sep 13, 2001 at 01:59:29AM +1000, Robert Collins wrote:
> >On Thu, 2001-09-13 at 01:55, Christopher Faylor wrote:
> >> On Wed, Sep 12, 2001 at 09:52:14PM +1000, Robert Collins wrote:
> >> >Attached is a slightly reworked daemon that will not impact 95 in speed
> >> >(well at dll load for non-forked process's it will, but not after that
> >> >first request).
> >> >
> >> >Egors original message with changelogs describing this beast is
> >> >available
> >> > here.
> >> >
> >> >I've altered the layout slightly - I consider the daemon more core than
> >> >(say) cygcheck, so I placed it all in cygwin.
> >> 
> >> I don't recall the original layout but if it created a new directory then
> >> that is correct.  This shouldn't be in the cygwin directory.  I made a concerted
> >> effort to make it one directory per "thing" a while ago.  cygserver is another
> >> "thing".
> >
> >The original layout put it in utils, which didn't really fit either.
> >
> >Ok, I'll move it out. Do you wnat the shared functions (like
> >set_os_type) duplicated;put into a convenience library; or link straight
> >to the .o in the cygwin directory?
> I'm not sure since set_os_type is undergoing a radical rewrite in 1.3.4.
> It sounds like cygserver needs its own directory.
> If it is using non-exported functions from cygwin then we have to design
> how the two entities communicate with each other.

It's more that until the two entities are in communication with each
other, they have to come to some common conclusions. Picking the OS
(what comms channels will be available) and security (attempt to
negotiate security, or don't bother) are the key things.

I had moved set_os_type to, which made sense to me,
and then just linked with host_dependent.o. Likewise for smallprint
(used by That was it though.

Te point being that unlike (say) mount.exe, cygserver is actually part
of cygwin, so cannot be _fully_ dependent on cygwin1.dll. I do link
cygserver.exe to cygwin1.dll, so there's no reason that I cannot use
exlusively exported functions. (The cygwin1 loaded into cygservers
address space will behave as though there is no daemon).


More information about the Cygwin-patches mailing list