i just noticed this today after i updated my base cygwin yesterday.
if i use putty to establish a ssh session and just hit the X to close
(instead of typing 'exit'), the server leaves a copy of bash running
till i go in an manually end process.
i've tried reinstalling everything and still have th
Hi all,
First of all, thank you everyone for the hard work, as always.
After updating to the recently released cygwin-1.5.24, fetchmail,
runing in daemon mode, started to show dos-window with /bin/sh.exe
whenever it tries to start mda, procmail in my case, which is very
very annoying.
Reverting
Tim Hanson wrote:
Larry Hall (Cygwin cygwin.com> writes:
Your line-endings are CRNLs. The best thing to do is to run d2u on the
scripts in question. Read any recent Cygwin bash announcements for other
options to resolve this situation and further details.
thanks. much appreciated.
No pr
Reini Urban (quoting Sam Steingold at the issue tracker
page [1]) wrote:
The original problem is best solved by a
(setq *default-file-encoding* :unix)
in ~/.clisprc.lisp
As mentioned in an earlier post, that doesn't work for
*standard-output*, presumably because it's already :dos
before .cli
Dave Korn wrote on Tuesday, January 30, 2007 12:30 PM:
> On 30 January 2007 15:50, Eramo, Mark wrote:
>
>> As part of this multiplatform installer it generates a setup.sh
>> script from information in the Installshield jars. When the setup.sh
>> is produced, all the lines are terminated with a "^
Daniel Brockman spicetrader.net> writes:
> Eric, I am glad there are people like you, knowledgable and deeply
> interested.
> Clearly you have given much thought to the consistency and efficiency of
> Cygwin/
> Linux. All of us benefit from your valuable efforts. I'm sincerely grateful.
I appr
Eric Blake byu.net> writes:
>
> According to Daniel Brockman on 1/30/2007 12:18 AM:
> > A blank line in the script file produces err msg
Eric, I am glad there are people like you, knowledgable and deeply interested.
Clearly you have given much thought to the consistency and efficiency of Cygw
On 30 January 2007 15:50, Eramo, Mark wrote:
> As part of this multiplatform installer it generates a setup.sh script
> from information in the Installshield jars. When the setup.sh is
> produced, all the lines are terminated with a "^M"
That'll be the bug then. Report it upstream to the Ant m
Good morning,
Christopher Faylor wrote:
On Tue, Jan 30, 2007 at 08:21:39AM -0800, Glenn Serre wrote:
bash -c /bin/pwd
appears to cause the problem. I have attached strace.out.bz2 that was
created like this:
C:\cygwin\bin>strace bash -c /bin/pwd > strace.out
using the snapshot cygwin1-2006
On 30 January 2007 14:33, Andrew Louie wrote:
>>> Thanks for the info. It's interesting to know. What I still don't get,
>>> however, is the fact that the same statement does not waste memory on
>>> the x86 Linux Perl 5.8.5, but does on the x86 Cygwin Perl 5.8.7 and the
>>> x86_64 Linux 5.8.8.
Hello everybody...
I uploaded last (as of yesterday) version of cygwin..
Then I tried compiling some of my libraries...
Here is the result on one dealing with sockets :
cc -Wall -D_POSIX_SOURCE -D__rtems__ -mno-cygwin -mwindows -I../include/
-I/usr/include -c MyBase.c
In file included f
On Tue, Jan 30, 2007 at 08:21:39AM -0800, Glenn Serre wrote:
>bash -c /bin/pwd
>
>appears to cause the problem. I have attached strace.out.bz2 that was
>created like this:
>
>C:\cygwin\bin>strace bash -c /bin/pwd > strace.out
>
>using the snapshot cygwin1-20061211.dll version of cygwin1.dll.
>
>P
Good morning,
Christopher Faylor wrote:
On Tue, Jan 30, 2007 at 07:12:02AM -0800, Glenn Serre wrote:
Good morning,
Lev Bishop wrote:
On 1/30/07, Glenn Serre wrote:
I have no working patch, I was going to use this problem as an
opportunity for
my first attempt to build and debug the cygwin D
On Tue, Jan 30, 2007 at 07:12:02AM -0800, Glenn Serre wrote:
>Good morning,
>
>Lev Bishop wrote:
>>On 1/30/07, Glenn Serre wrote:
>>>I have no working patch, I was going to use this problem as an
>>>opportunity for
>>>my first attempt to build and debug the cygwin DLL (while maybe even
>>>chargi
Hello,
I have been struggling for some time trying to resolve the dreaded
CR/LF Problem.
I am running Ant 1.6.2 builds on Windows XP SP 2 using Cygwin version
1.5.24-1 and Bash version 3.2.9-11. The Ant builds are running an
Installshield 11.5 command line interface to create a multiplatform
i
Good morning,
Lev Bishop wrote:
On 1/30/07, Glenn Serre wrote:
I have no working patch, I was going to use this problem as an
opportunity for
my first attempt to build and debug the cygwin DLL (while maybe even
charging a
client for it) but it looked to me as if it may already be being
addre
On Tue, 30 Jan 2007, Jared Silva wrote:
> Eric Blake wrote:
> > You can also try debugging it yourself. At the command line, turn on
> > the options 'set -xv', then when you hit TAB, you will see what bash
> > is trying to do during the tab completion. I don't personally use
> > svn, so I'm not
On Tue, 30 Jan 2007, Rick Anderson wrote:
> Hi
>
> I am trying to run the following shell script in cygwin:
>
> >#! /bin/sh
> >
> >if [ $# -ne 1 ]; then
> >echo 1>&2 Usage: $0 certificate.p12
> >exit 127
> >fi
> >
> >java -classpath ${AHECLIENT_HOME}/lib/org.mortbay.jetty.
Eric Blake wrote:
You can also try debugging it yourself. At the command line, turn on the
options 'set -xv', then when you hit TAB, you will see what bash is trying
to do during the tab completion. I don't personally use svn, so I'm not
the best candidate to help you fix the _svn() helper func
> Thanks for the info. It's interesting to know. What I still don't get,
> however, is the fact that the same statement does not waste memory on
> the x86 Linux Perl 5.8.5, but does on the x86 Cygwin Perl 5.8.7 and the
> x86_64 Linux 5.8.8. So it has been introduced only in later versions?
> An
Eric Blake wrote:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
According to Norton Allen on 1/29/2007 8:00 PM:
PID=`cat $PIDFILE`
No, this is a text mount:
That's the answer. You are creating PIDFILE with \r\n line endings, but
cat always reads in binary mode.
Try PI
On 1/30/07, Glenn Serre wrote:
I have no working patch, I was going to use this problem as an opportunity for
my first attempt to build and debug the cygwin DLL (while maybe even charging a
client for it) but it looked to me as if it may already be being addressed.
Looking again, I see that this
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
According to Daniel Brockman on 1/30/2007 12:18 AM:
> A blank line in the script file produces err msg
>
> : command not found
>
> I can't figure out a way to make the new version of sh.exe work. Imho, it's
> broken.
...
>
> I found this in the archiv
Hello.
> When I start Cygwin I get bash prompt but whenever I type a command and
> press enter, cygwin exits immediately.
> I'm using Windows XP x64 (all patches).
This issue is currently discussed under the topics :
- "Newly-installed bash 3.2.9-10 (cygwin 1.5.24-1) exits when I try to execute
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
According to Daniel Brockman on 1/30/2007 12:20 AM:
>>
>> I installed a new version of cygwin yesterday, and find that bash starts up
> and
>> builtins seem to execute, but when I try the first command, cygwin exits
>> silently.
>> [...]
>> Any hint
>java -classpath ${AHECLIENT_HOME}/lib/org.mortbay.jetty.jar
org.mortbay.util.PKCS12Import $1 ${AHECLIENT_HOME}/conf/aheclient.ks
>
>keytool -keystore ${AHECLIENT_HOME}/conf/aheclient.ks -import -alias rootca
-file ${AHECLIENT_HOME}/lib/certs/cacert.pem -trustcacerts
"cygpath -w some_dir"
will
Hello
I just installed cygwin 1.5.24-1 from two different mirrors
(mirrors.dotsrc.org, ftp.funet.fi) with the default selected packages.
When I start Cygwin I get bash prompt but whenever I type a command and
press enter, cygwin exits immediately.
I'm using Windows XP x64 (all patches).
I have
Hi
I am trying to run the following shell script in cygwin:
>#! /bin/sh
>
>if [ $# -ne 1 ]; then
>echo 1>&2 Usage: $0 certificate.p12
>exit 127
>fi
>
>java -classpath ${AHECLIENT_HOME}/lib/org.mortbay.jetty.jar
>org.mortbay.util.PKCS12Import $1 ${AHECLIENT_H
Hello again
Sorry to ask for explainations, but since English is not my mother tongue, I
think I may be misunderstanding the point you made :
> 4a. For a single affected script, add this line just after the she-bang:
> (set -o igncr) 2>/dev/null && set -o igncr; # comment is needed
> 4b. For a s
29 matches
Mail list logo
