On Jan 27, 2006, at 10:55 AM, Stewart Midwinter wrote:

I've been able to isolate a problem with csh on cygwin running on
Windows Server 2003 on a Xeon.  The following script hangs after a
certain period of time ranging from a few minutes to a few hours.

---------------
#!/bin/csh

while (1)
        set year = `date +%y`
        set month = `date +%m`
        set day = `date +%d`
        set hour = `date +%H`
        set minute = `date +%M`
        set second = `date +%S`
        set stamp = "$year$month$day $hour : $minute : $second"
        echo $stamp
        sleep 2
end
------------

The equivalent script in bash doesn't hang even after a day or more.

-------------
#!/bin/bash

while [ 1 ]; do
        echo $(date +%Y%m%d.%H%M%S)
        sleep 2
done
-------------

This isn't the equivalent script. It's similar and the output is the same, but you only call date once here, while in the other you call it 6 times. Maybe that is way it seems to work for bash and not csh.


Has anyone else had problems with csh scripts on cygwin? Yes, I know
that some people don't recommend using csh (see "Csh programming
considered harmful",
http://www.faqs.org/faqs/unix-faq/shell/csh-whynot/), but I'm stuck
with a whole lot of csh scripts and don't have time to port them all
at the moment.
I have problems with bash/sh script hanging, but I haven't tried csh.

http://cygwin.com/ml/cygwin/2006-01/msg00549.html

Which I'm getting in 1.5.19-4 too, but I haven't tried the latest snapshot. Which reminds me. Could you read http://cygwin.com/ problems.html and provide the information that it says to provide?

Also were in the script does it hang. It you type ps -ef what do you see. What information does the /proc directory tell you. Can you ctrl-c out of the script?

Basically, provide as much information as possible.

Peter


--
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/

Reply via email to