Hi Corinna,
Please test the latest snapshot from http://cygwin.com/snapshots/
I'm rather confident that it solves your problem.
Sorry for delay, but I returned from a journey today. You are right, my
installation works like charm again. Thank you very, very much!
Regards,
Oliver
--
Anyway, it could also be a permissions problem: maybe because its a
restricted user, the child process is in some way prevented from accessing
the object created by the parent and it can't notify it. But that's just
guesswork. I think your next most informative option might be to use
Original Message
From: Oliver Vecernik
Sent: 15 April 2005 09:57
Anyway, it could also be a permissions problem: maybe because its a
restricted user, the child process is in some way prevented from
accessing the object created by the parent and it can't notify it. But
that's just
On Apr 14 11:40, Oliver Vecernik wrote:
Hi,
I'm not sure what happened, but if I start Cygwin for a certain
restricted user I receive the following message:
9 [main] bash 3624 fork_parent: child 2756 died waiting for
longjmp before initialization
bash: fork: Bad file descriptor
Hi,
I'm not sure what happened, but if I start Cygwin for a certain
restricted user I receive the following message:
9 [main] bash 3624 fork_parent: child 2756 died waiting for
longjmp before initialization
bash: fork: Bad file descriptor
bash-2.05b$
Everything worked fine, nothing was
I'm not sure what happened, but if I start Cygwin for a certain
restricted user I receive the following message:
9 [main] bash 3624 fork_parent: child 2756 died waiting for
longjmp before initialization
bash: fork: Bad file descriptor
bash-2.05b$
Everything worked fine, nothing
Original Message
From: Oliver Vecernik
Sent: 14 April 2005 10:41
Hi,
I'm not sure what happened, but if I start Cygwin for a certain
restricted user I receive the following message:
9 [main] bash 3624 fork_parent: child 2756 died waiting for
longjmp before initialization
7 matches
Mail list logo
