Re: Problem with pty allocation code, race condition?

e give > it a try and report the results here. I'm sorry to report that the problem I described in <http://cygwin.com/ml/cygwin/2004-05/msg00596.html> (multiple xterms started in quick succession get the same PTY) still exists in the 20040519 snapshot. The output of "ps" af

Re: xemacs shell problem

Some old XEmacs (21.1 era) was handling this correctly, so I believe the problem is in XEmacs. I haven't had a chance to trace XEmacs code yet. I have been using the following work around. None of which is perfect. 1) Stick with an old XEmacs. 2) Do run /usr/local/bin/xemacs. You can searc

Problem with terminal escapes for manpages RESENT W/OUT ENCLOSURES

I thought I sent this several weeks back, but I don't see it on the list. My SWAG is that the attached zipfile caused it to be refused. If the attachments are needed for understanding, please, how can I post them? === ORIGINAL MESSAGE FOLLOWS === Background: everything up to date Terminal: rxvt

Re: FYI: GNU Smalltalk 2.1.5 on Cygwin

Brian Ford <[EMAIL PROTECTED]> wrote on 19-05-2004 21:34:37: > > No, AFAIK, -lsomelib should never be in an automake _DEPENDENCIES target. > That's a Makefile.am bug in GNU Smalltalk. Removing it from there should have > been all that was required. > You're absolutely right I tried again wit

Re: Anyone using bash shell in Japanese, Chinese, or Korean?

Your observation, Igor, is correct. The 0x5C character is the backslash and that is at the root of the problem, especially in a command like ls. We haven't run across the problem with 0x2F, but that may just be a matter of time. If Cygwin applications are handling the multibyte characters as a

Re: Unsufficient number of semaphores in a set

Corinna Vinschen wrote: > > In /usr/include/cygipc/sys one can find > > > > #define SEMMSL 32 /* <= 512 max num of semaphores per id */ > > > > It's obviously not the case. How can I have Cygwin allowing semaphore set > > of size 250? > > First question: Are you using cygipc or cygs

Re: FYI: GNU Smalltalk 2.1.5 on Cygwin

On Wed, 19 May 2004, tuin01 wrote: > > > libgst_la_DEPENDENCIES = $(top_builddir)/lib-src/library.la > $(LIBSIGSEGV) \ > > > ${top_builddir}/libltdl/libltdlc.la ${top_builddir} > > /snprintfv/snprintfv/libsnprintfvc.la -lreadline /lib/libgmp.la > > > > This should not be needed... What wa

Re: FYI: GNU Smalltalk 2.1.5 on Cygwin

> > changed following files. > > 1. smalltalk-2.1.5/i18n/i18n.c > > - added #include > > I'm assuming this was for some typedefs or macros. If they are standard > POSIX ones that are present in the Linux headers but missing in the Cygwin > ones, it'd be interesting to know. > This w

Re: FYI: GNU Smalltalk 2.1.5 on Cygwin

On Wed, 19 May 2004, tuin01 wrote: > Concerning Cygwin dll: 1.5.9 (Complete install may 16, 2004) > GNU Smalltalk version 2.1.5 > Windows XP (v 5.1) Professional SP1. > > In directory where I've unpacked the smalltalk source package. > ./configure > > changed following files. > 1. smalltalk-2.1.5

Re: Question concerning SSHD on CYGWIN

Wrong list. Please see for details. In the meantime, I've redirected this to the correct one. Please remove cygwin-patches from further discussion on this topic unless you actually submit a patch to Cygwin. Igor On Wed, 19 May 2004, Kleinert

Re: tail and win file handling

Larry Hall wrote: > the file deleted by "rm" isn't deleted really until it's closed, which > won't happen until 'tail' ends. This is the way Windows works. There's > not much to be done about it (at least not in Cygwin). Believe me, > we've tried. Here is a really ugly kludge to deal with a re

Re: mutt and ssmtp on Cygwin on Windows Server 2003 'child exited 127'

[EMAIL PROTECTED] wrote: Somehow I do not succeed in configuring mutt or ssmtp with Cygwin on a Windows 2003 server. As an example of what happens: $ echo hallo | mutt -s new_test [EMAIL PROTECTED] Error sending message, child exited 127 (Exec error.). Could not send the message. The error is exac

RE: mutt and ssmtp on Cygwin on Windows Server 2003 'child exited 127'

Sorry for the noise. -Original Message- From: Luc Hermitte [mailto:[EMAIL PROTECTED] Sent: Wednesday, May 19, 2004 10:09 AM To: [EMAIL PROTECTED] Subject: Re: mutt and ssmtp on Cygwin on Windows Server 2003 'child exited 127' * On Wed, May 19, 2004 at 09:16:11AM -0400, Buchbinder, Barry

libtool dll linking problem

Hallo cygwin, Libtool tries to link: sh ./libtool --mode=link g++ -avoid-version -rpath /usr/lib -no-undefined -o libdbxml-1.2.la ANTLRUtil.lo ASTFactory.lo ASTNULLType.lo ASTRefCount.lo BaseAST.lo BitSet.lo CharBuffer.lo CharScanner.lo CommonAST.lo CommonASTWithHiddenTokens.lo Co

Re: mutt and ssmtp on Cygwin on Windows Server 2003 'child exited 127'

On Wed, 19 May 2004, gert_de_boer wrote: > Somehow I do not succeed in configuring mutt or ssmtp with Cygwin on a > Windows 2003 server. > > As an example of what happens: > > $ echo hallo | mutt -s new_test [EMAIL PROTECTED] > Error sending message, child exited 127 (Exec error.). > Could not sen

Re: mutt and ssmtp on Cygwin on Windows Server 2003 'child exited 127'

* On Wed, May 19, 2004 at 09:16:11AM -0400, Buchbinder, Barry (NIH/NIAID) <[EMAIL PROTECTED]> wrote: > If I remember correctly (I have not played with mutt for quite a > while), mutt can connect directly to a IMAP or POP server. So might > you be able to eliminate the use of ssmtp and have mutt s

Re: [OT] RE: Problems listing tasks under cygwin.

On Wed, 19 May 2004, Brian Dessent wrote: > Although I'd still like to know why using ProcExp to list the handles* Nope, it is DLLs. > of any running Cygwin process causes the CPU to peg to 100%, and not > come down until cygwin1.dll is unloaded, i.e. kill all running cygwin > tasks and services

RE: mutt and ssmtp on Cygwin on Windows Server 2003 'child exited 127'

If I remember correctly (I have not played with mutt for quite a while), mutt can connect directly to a IMAP or POP server. So might you be able to eliminate the use of ssmtp and have mutt send mail directly to the place that ssmtp sends it? -Original Message- From: [EMAIL PROTECTED] [mai

mutt and ssmtp on Cygwin on Windows Server 2003 'child exited 127'

Somehow I do not succeed in configuring mutt or ssmtp with Cygwin on a Windows 2003 server. As an example of what happens: $ echo hallo | mutt -s new_test [EMAIL PROTECTED] Error sending message, child exited 127 (Exec error.). Could not send the message. The error is exactly the same as whe

RE: Cygwin's chmod +X

> I noticed while creating a bash script to backup my parents outlook & > mydocuments folers, that WindowsXP does not recognize a "superuser" as > being allowed access to a users folders! You can only access a folder if you have been given permission (in the ACL) unless you open it in backup mode.

FYI: GNU Smalltalk 2.1.5 on Cygwin

Concerning Cygwin dll: 1.5.9 (Complete install may 16, 2004) GNU Smalltalk version 2.1.5 Windows XP (v 5.1) Professional SP1. In directory where I've unpacked the smalltalk source package. ./configure changed following files. 1. smalltalk-2.1.5/i18n/i18n.c - added #include 2. libgst/M

Re: tcsh 4k problem

On May 19 10:59, Kai Tomerius wrote: > Hi, > > I just encountered a problem with tcsh scripts with a size >4k. > Admittedly, I don't run the latest version of tcsh, but I've searched > the archives and didn't see this problem being fixed. Sorry if I missed > something ... Known problem if the

Re: [OT] RE: Problems listing tasks under cygwin.

Dave Korn wrote: > [ObCygwin] Sysinternals' tools are invaluable for diagnosing cygwin > problems just as much as windoze problems. Trouble with access perms for > your cron daemon service? See what's going on with tokenmon. Trouble with > file access? Filemon will show you what files are inv

[OT] RE: Problems listing tasks under cygwin.

> -Original Message- > From: cygwin-owner On Behalf Of Brian Dessent > Sent: 18 May 2004 19:34 > Dave Korn wrote: > > > Actually, SYSTEM has higher privileges in general than > root. It may well > > be impossible to kill some tasks belonging to system > because they may not > > allow

tcsh 4k problem

Hi, I just encountered a problem with tcsh scripts with a size >4k. Admittedly, I don't run the latest version of tcsh, but I've searched the archives and didn't see this problem being fixed. Sorry if I missed something ... Cheers, Kai The following script does pretty much nothing except for pr

Re: Unsufficient number of semaphores in a set

On May 19 02:08, Krzysztof Duleba wrote: > Hello > > I expreience strange Cygwin behaviour when I try to create a big semaphore > set. I wrote a simple test case as following: > [...] > My Cygwin returns: > > $ echo 59|./semtest > ok > > $ echo 60|./semtest > ok > > $ echo 61|./semtest > 22; In