This is the mail archive of the
mailing list for the Cygwin project.
Re: Curious behavior of CYGSERVER
"David A. Cobb" <firstname.lastname@example.org> wrote:
> *And really nice if there were at least a
> /usr/doc/cygwin/cygserver.readme* Nothing fancy, just tell what we
> should expect and what to be wary of.
As I just mentioned in a different thread and as I kept forgetting to
mention earlier in this thread, cygserver (at the moment) does
(effectively) nothing (the entry points for the IPC calls are
deliberately missing from the DLL export list). I could (and probably
should) write a README to that effect. (Watch this space etc.)
Which brings me to the question: why are you running cygserver at all?
In another message in this thread, you mention that the configure ran
more quickly with cygserver than without. This is probably due to the
/tmp/cygdaemo socket file I mentioned in another thread. If you run
cygserver and then kill it, it leaves this file behind, which causes all
cygwin processes to pause for a second (or so). So, if you've run
cygserver and are no longer running it, find and remove the
/tmp/cygdaemo file. Don't remove it if you are currently running
Of course, the main advice is just not to run cygserver at all right
now, since it doesn't provide any functionality.
As for your other point about stdout redirection problems when running
cygserver, I find it hard to see how this has anything to do with
cygserver especially since you say the redirection file doesn't even get
created. The file is created by the shell itself and for this not to
happen indicates that something wierd and wonderful is happening.
In any case, as I mentioned before, I need to see the
`cygcheck -s -v -r' output from your machine before we can get any
further with this.
Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple
Bug reporting: http://cygwin.com/bugs.html