Elfyn,
[EMAIL PROTECTED] wrote:
Hi,
I am getting the exact same results as you are Jari. I had a working
postgres install just before the return values were changed in cygipc
(1.12), but as i only use it rarely i did not notice the service starting
or not starting up. From what I can see it loo
Jason,
Jason Tishler wrote:
On Mon, Dec 09, 2002 at 12:05:16AM +0100, Dan Holmsand wrote:
I get a similar error:
IpcSemaphoreInitialize: semctl(id=2, 0, SETVAL, 0) failed: Invalid argument
The above is noted in the README:
2. It is recommended to delete all cygipc temporary files
Sergey Okhapkin wrote:
net start init
chkconfig rsync on
chkconfig rsync off
bluescreen... Win2000. I have no rsync installed.
I set system environment variable CYGWIN to "nontsec", restarted init
service and the problem went away...
I've seen this occasionally as well, but it doesn't stop the
Randall,
Randall R Schulz wrote:
Dan,
It seems most likely from this that the problem is in your file system.
When's the last time you ran CHKDSK? I seem to recall other reports that
were for some reason associated with accessing Cygwin's /etc. I cannot
explain this other than perhaps as simp
Pierre,
Pierre A. Humblet wrote:
AFAICT the handle is opened when starting cygwin and is inherited by
child processes. It is used in a WaitForSingleObject call.
The purpose is to rescan /etc/{passwd,goup} after changes.
It's unlikely to be a coincidence, given the previous e-mails!
That's extre
Pierre A. Humblet wrote:
AFAICT the handle is opened when starting cygwin and is inherited by
child processes. It is used in a WaitForSingleObject call.
The purpose is to rescan /etc/{passwd,goup} after changes.
It's unlikely to be a coincidence, given the previous e-mails!
That seems to be it!
t the code in
init_cygheap::etc_changed is to "blame"; it must trigger some obscure
windows bug that sometimes causes a bsod when files under /etc are accessed.
/dan
Dan Holmsand wrote:
That seems to be it! [touching wood]
I added a "return 0" at the top of init_cyghea
Danilo,
Danilo Turina wrote:
I also have a very similar problem (writing in /etc when X is running,
always cause a BSOD, regardless of antivirus packages), if I can have
that hacked cygwin1.dll I can try it on my systems and tell if it's the
same problem.
Sure. I'll send you one in private ma
Christopher Faylor wrote:
The latest snapshot should fix some /etc handling problems (thanks to
ideas and code from Pierre Humblet), like the dreaded BSOD. It may also
solve the "pipes are slow" problem. There are also all of the fixes
accumulated since 1.3.18, of course.
Indeed it does seem t
Dan Holmsand wrote:
Indeed it does seem to stop the BSODding on my machines. Thanks!
Still no BSOD.
However, now I'm having trouble with postgresql: the postmaster dies as
soon as I exit psql. Reverting to a cygwin1.dll built from cvs from four
days ago fixes the problem.
Here is wha
Robert Mecklenburg wrote:
I'm getting the following error in the x-enabled version of cygwin
emacs:
** ad-Orig-documentation called with 5 arguments, but accepts only 1-2
I think the problem is with the original documentation function itself,
not with advice.
M-x describe-function document
Joe,
Joe Buehler wrote:
I think this (long-running) problem has something to do with
the fact that emacs under Cygwin now has unexec(). If you roll
back to emacs 21.2-9 you will not have any problems.
I think I've found the problem: /usr/share/emacs/21.2/etc/DOC-21.2.1
seems to be missing a f
Joe Buehler wrote:
Dan Holmsand wrote:
I think I've found the problem: /usr/share/emacs/21.2/etc/DOC-21.2.1
seems to be missing a few lines (at line 2406, right before
Finvocation-name, to be precise).
Thank you! There does indeed seem to be a difference between
emacs and emac
Joe Buehler wrote:
GNU emacs 21.2-12 is available.
Actually, it seems to be only partially available. According to setup,
only the "emacs" package has been updated, not emacs-el and emacs-X11
(both still at 21.2-11).
/dan
--
Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple
B
14 matches
Mail list logo
