On Jul 19 12:36, Dr. Volker Zell wrote: > You are right. I just checked my XWin.log and it again said > > MIT-SHM extension disabled due to lack of kernel support > > also ipcs gives me > > Bad system call > > I start my cygserver as a service and a process listing shows that it's > still running, hmmmmmmm..... > > When I start cygserver after a reboot from a bash shell I get the > following (cygwin1.dll and cygserver both from the Jul 17 snapshot): > > 12:19 PM [505]> cygserver --version > cygserver: (cygwin) 1.10 > API version 1.5.11(0.116/4/1)-(3.0.0.2) 20040717 00:34:52SNP > Copyright 2001, 2002, 2003 Red Hat, Inc. > Compiled on Jul 17 2004 > Default configuration file is /etc/cygserver.conf > 12:21 PM [506]> cygserver -e -l 7 -d > cygserver: daemon starting up > cygserver: > /netrel/src/cygwin-snapshot-20040717-1/winsup/cygserver/threaded_queue.cc, line 112: > starting all queue submission loops > assertion "!_hThread" failed: file > "/netrel/src/cygwin-snapshot-20040717-1/winsup/cygserver/threaded_queue.cc", line 321
You're talking about two different problems here. The "Bad system call" is a result of either not having $CYGWIN set to contain the word "server", or a result of Cygserver not running. The failing assertion in Cygserver seems to be a problem of compiling Cygserver with a g++ version which has some weird bug. The latest snapshot still has that problem, apparently. I've just created a new snapshot, which contains a Cygserver which should work fine. At least I tried it and it runs w/o assertion *and* I don't see the above "MIT-SHM extension disabled due to lack of kernel support" message with that Cygserver. Corinna -- Corinna Vinschen Please, send mails regarding Cygwin to Cygwin Co-Project Leader mailto:[EMAIL PROTECTED] Red Hat, Inc. -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Problem reports: http://cygwin.com/problems.html Documentation: http://cygwin.com/docs.html FAQ: http://cygwin.com/faq/