Re: Strange-Dangerous behaviour in Cygwin

[Igor Pechtchanski]

On Tue, 10 May 2005, Christopher Faylor wrote:

> On Tue, May 10, 2005 at 06:56:10AM -0600, Eric Blake wrote:
> >Now my question - why can't cygwin have sane defaults for the tty, so that
> >this question doesn't continue to pop up?
>
> Because we hate everyone and want them to suffer?

Hmm, BWHEAWTTS?  Nah,  is *so* much more
succinct...
Igor
-- 
http://cs.nyu.edu/~pechtcha/
  |\  _,,,---,,_[EMAIL PROTECTED]
ZZZzz /,`.-'`'-.  ;-;;,_[EMAIL PROTECTED]
 |,4-  ) )-,_. ,\ (  `'-'   Igor Pechtchanski, Ph.D.
'---''(_/--'  `-'\_) fL a.k.a JaguaR-R-R-r-r-r-.-.-.  Meow!

"The Sun will pass between the Earth and the Moon tonight for a total
Lunar eclipse..." -- WCBS Radio Newsbrief, Oct 27 2004, 12:01 pm EDT

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

RE: problems in Perl process management

[Sonam Chauhan]

Christopher - 

> Yes, if you send a "kill -9" to a pid that shows up in ps but is
> associated with a non-cygwin process, it should work.  

So what me and Jurgen were discussing works, and you were wrong. Thanks for
revisiting your point after your earlier rudeness.

Regards,
Sonam Chauhan
-- 
Electronic Commerce, Corporate Express Australia Ltd.
Phone: +61-2-9335-0725, Email: [EMAIL PROTECTED]

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

Re: base-files patch (atn: Eric Blake)

[Igor Pechtchanski]

On Mon, 9 May 2005, Eric Blake wrote:

> According to John Morrison on 5/8/2005 1:52 AM:
> > On Fri, March 25, 2005 8:26 pm, Eric Blake said:
> >
> >>True enough.  And that points out another bug - echo "$0" may fail if $0
> >>starts with -, it should be echo -- "$0".  Isn't portable shell
> >>programming fun?
> >
> > Sorry that this has taken so long, but I'm just getting around to adding
> > all the fixes emailed wrt /etc/profile.  I tried the above, and it broke
> > so I checked the man pages,
>
> Serves me right for thinking that echo was standard when I typed my
> original message, rather than me actually testing at the command line.
> Yes indeed, POSIX requires that echo must interpret -- as a string
> operand, rather than the standard interpretation of being an argument
> separator.
>
> > so, I'm afraid that echo -- "${0}" won't work.
>
> This will work instead:
> case `printf %s "$0" | /usr/bin/tr '[:upper:]' '[:lower:]'` in
> bash | -bash | */bash )
> [..]

Or, of course, the standard "portable scripting" trick:

case "`echo "_$0" | /usr/bin/tr '[:upper:]' '[:lower:]'`" in
_bash | _-bash | _*/bash )
[..]

(or, if you don't mind a slightly longer command:
case "`echo "_$0" | /usr/bin/tr '[:upper:]' '[:lower:]' | /usr/bin/sed 
'/s/^_//'`" in
bash | -bash | */bash )
[..])
Igor
-- 
http://cs.nyu.edu/~pechtcha/
  |\  _,,,---,,_[EMAIL PROTECTED]
ZZZzz /,`.-'`'-.  ;-;;,_[EMAIL PROTECTED]
 |,4-  ) )-,_. ,\ (  `'-'   Igor Pechtchanski, Ph.D.
'---''(_/--'  `-'\_) fL a.k.a JaguaR-R-R-r-r-r-.-.-.  Meow!

"The Sun will pass between the Earth and the Moon tonight for a total
Lunar eclipse..." -- WCBS Radio Newsbrief, Oct 27 2004, 12:01 pm EDT

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

RE: Help !!! - Problem running Cygwin in Remote Desktop session with non-admin privileges

[Moghe, Jayant]

Larry:

Thank you for your help.

Best regards,
Jayant Moghe
===
Texas Instruments (I) Pvt. Ltd.
Bagmane Tech Park, CV Raman Nagar, Byrasandra
Bangalore - India 560 093
Office Phone: - +91- 80 - 25048295
[EMAIL PROTECTED]


"Fools you are... to say you learn by your experience  I prefer to
profit by other's mistakes and avoid the price of my own."
-Otto von Bismarck, 19th Century Prussian Chancellor.



-Original Message-
From: Larry Hall [mailto:[EMAIL PROTECTED] 
Sent: Tuesday, May 10, 2005 9:59 PM
To: Moghe, Jayant; cygwin@cygwin.com
Subject: RE: Help !!! - Problem running Cygwin in Remote Desktop session
with non-admin privileges

At 08:24 AM 5/10/2005, you wrote:
>I want to download Cygwin 1.5.16.
>
>Please let me know which mirror site hosts this version.
>
>Thanks.


Any mirror sites offered by 'setup.exe' are all considered to be active 
mirrors.  If your favorite one doesn't have the update you want, please
check to make sure your mirror still shows up in the list 
().  If it doesn't, choose another.  If
it does, you can choose to wait a little while and see if it gets
updated 
(though it really should be by now if the mirror is indeed active) or
pick
another mirror site off the list.




--
Larry Hall  http://www.rfk.com
RFK Partners, Inc.  (508) 893-9779 - RFK Office
838 Washington Street   (508) 893-9889 - FAX
Holliston, MA 01746 



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

Re: problems in Perl process management

[Christopher Faylor]

On Tue, May 10, 2005 at 11:22:49PM -0400, Christopher Faylor wrote:
>On Wed, May 11, 2005 at 01:19:14PM +1000, Sonam Chauhan wrote:
>>Hi Christopher - 
>>your response to Jurgen had mentioned:
>>> ActiveState perl is a windows program.  You can't send cygwin (aka unix)
>>> signals to a windows proram.
>>This should be possible if the ActiPerl Windows executable was executed from
>>a Cygwin terminal -- 'ps' shows it running and 'kill -9' should kill it.
>
>I guess I forgot my signature.

Actually, let me clarify without being flip.

Yes, if you send a "kill -9" to a pid that shows up in ps but is associated
with a non-cygwin process, it should work.  Other non-terminating signals will
not work, and a blockable terminating signal like SIGTERM won't work.  If you
try to send any kind of signal to the windows pid, it won't work.

I'm sorry that I wasn't entirely clear in my original reply.
--
Christopher Faylor  spammer? -> [EMAIL PROTECTED]
Cygwin Co-Project Leader[EMAIL PROTECTED]
TimeSys, Inc.

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

Re: problems in Perl process management

[Christopher Faylor]

On Wed, May 11, 2005 at 01:19:14PM +1000, Sonam Chauhan wrote:
>Hi Christopher - 
>your response to Jurgen had mentioned:
>> ActiveState perl is a windows program.  You can't send cygwin (aka unix)
>> signals to a windows proram.
>This should be possible if the ActiPerl Windows executable was executed from
>a Cygwin terminal -- 'ps' shows it running and 'kill -9' should kill it.

I guess I forgot my signature.
--
Christopher Faylor  spammer? -> [EMAIL PROTECTED]
Cygwin Co-Project Leader[EMAIL PROTECTED]
TimeSys, Inc.

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

RE: problems in Perl process management

[Sonam Chauhan]

Hello to Reini Urban and Yitzchak Scott-Thoennes if you're seeing this. 

Reine, Yitzchak - Back in Feb, you had a discussion:
http://sourceware.org/ml/cygwin/2005-02/msg00224.html 
Do you think the issue below is related to it? Also, at that time Yitzchak
had proposed a patch - do you know what the status of that is? 

Jurgen - I think this is not a Windows problem but a Perl/Cygwin problem.
Our experiences may be related. How do you determine the grandchild PID -
was it returned by fork, or did you use the Proc::Killfam and
Proc::ProcessTable Perl modules? I use these modules for convenience and
some debug code showed that they simply do not recognize the grandchildren
as sub-children of the parent PID. The reason is probably the issue
mentioned in the URL -- ProcessTable wrongly showing WINPIDs as Cygwin PIDs.

Hi Christopher - 
your response to Jurgen had mentioned:
> ActiveState perl is a windows program.  You can't send cygwin (aka unix)
> signals to a windows proram.
This should be possible if the ActiPerl Windows executable was executed from
a Cygwin terminal -- 'ps' shows it running and 'kill -9' should kill it.

Regards,
Sonam Chauhan
-- 
Electronic Commerce, Corporate Express Australia Ltd.
Phone: +61-2-9335-0725, Email: [EMAIL PROTECTED]
 

> -Original Message-
> From: Jurgen Defurne [mailto:[EMAIL PROTECTED]
> Sent: Tuesday, 10 May 2005 9:12 PM
> To: Sonam Chauhan
> Cc: cygwin@cygwin.com
> Subject: Re: problems in Perl process management
> 
> I also would like to know if it is possible.
> 
> However, it could be that it has nothing to do with Cygwin. I have
> a Perl script which forks several children and monitors their output.
> 
> If a child fails, then it has no use to run all forked processes further
> and I kill them with the perl 'kill' command. However, I also notice that
> deeper forked processes (grandchildren) refuse to die. This
> script is only run using ActiveState Perl.
> 
> I think it is really a serious Windows problem, because using
> the task manager it also seems not really possible to kill a complete
> process hierarchy.
> 
> Regards,
> 
> Jurgen Defurne
> 
> 
> 
> 
> 
> 
> 
> 
> 
> Sonam Chauhan <[EMAIL PROTECTED]>
> Sent by:
> [EMAIL PROTECTED]
> 2005-05-10 10:41 AM
> 
> To: "'cygwin@cygwin.com'" 
> cc: (bcc: Jurgen Defurne/BRG/CE/PHILIPS)
> Subject:problems in Perl process management
> Classification:
> 
> 
> 
> 
> Hello -
> 
> I'd appreciate help with problems doing process management in Cygwin/Perl.
> 
> 
> I have a Perl application that creates child processes - I need it to kill
> processes that exceed a certain timeout. I am trying to use the
> Proc::ProcessTable and Proc::Killfam CPAN modules for this.
> 
> I ran into two problems:
> 
> The first problem was a "can't stat /dev" error message produced when
> calling Proc::Killfam. This problem was fixed by a script I found that
> populated entries under /dev.
> 
> To understand the next probem, have a look at the simple test script
> attached. The script forks a child process, which runs `sleep` in a third
> process. The parent process then tries to kill both children on expiry of
> a
> timeout. The script behaves perfectly on Linux -- it works as expected and
> kills the fork-ed child Perl process, as well it's `sleep` child process.
> However, on Cygwin/Perl it only kills the fork-ed Perl child - it cannot
> kill the `sleep`-ing child.
> 
> The problem seems to be that the process table data returned by
> Proc::ProcessTable seems to differ from the data returned 'ps'.
> Specifically, Proc::ProcessTable returns the WINPID of a process as the
> PID
> for the backticked `sleep` process.
> 
> The closest issue I found in the list archives is this one:
> http://sourceware.org/ml/cygwin/2005-02/msg00224.html
> It does not seem to have been resolved.
> 
> I'm running Perl on Cygwin on Windows XP SP2. Running 'cygcheck -c' gives
> the following package status for cygwin and Perl:
> --
> cygwin  1.5.16-1   OK
> perl5.8.6-4OK
> --
> 
> Can anyone help?
> 
> Regards,
> Sonam Chauhan
> --
> Electronic Commerce, Corporate Express Australia Ltd.
> Phone: +61-2-9335-0725, Email: [EMAIL PROTECTED]
> 
> 
> 
> --
> 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/

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

Re: how to kill windows process from bash shell?

[Christopher Faylor]

On Tue, May 10, 2005 at 10:18:15PM -0400, John R Larsen wrote:
>In my installation the path is "/usr/bin/kill" Do a "which kill" to
>find the path.

Um, no.  /bin/kill will work just fine in a standard cygwin
installation.  It's less typing.

cgf

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

Re: how to kill windows process from bash shell?

[John R Larsen]

In my installation the path is "/usr/bin/kill"  Do a "which kill" to find the 
path.

On 10 May 2005 at 18:18, Christopher Faylor wrote:

Date sent:  Tue, 10 May 2005 18:18:49 -0400
From:   Christopher Faylor <[EMAIL PROTECTED]>
To: cygwin@cygwin.com
Subject:Re: how to kill windows process from bash shell?
Send reply to:  cygwin@cygwin.com

[ Double-click this line for list subscription options ] 

On Tue, May 10, 2005 at 03:07:40PM -0700, David Fong wrote:
>Hi,
>I need some help.
>I have one windows process (WinXP)  that is running
>from one cygwin window.
> 
>The process is hanging and I want to kill the process
>from another cygwin window.
>There is a separate spawned process from my program
>C:\windows\system32\dwwin.exe
>and it has a process number displayed when I run
>ps -W in a separate cygwin process.
> 
>2480 1172 2480 2480 con 11293 13:14:32
>/cygdriver/c/hw/destination/rundump.bat
>2816 0 0 2816 ? 0 13:41:32 C:\windows\system32\cmd.exe
>2652 0 0 2652 ? 0 13:41:32
>C:\hw\destination\cmodel\player\Player.exe
>3412 0 0 3412 ? 0 13:41:32
>C:\windows\system32\dwwin.exe
>The dos batch file (rundump.bat) runs cmd.exe which
>calls Player.exe which calls this dwwin.exe when error
>occurs
>which has message of
> 
>Player.exe has encountered a problem and needs to
>close.
>We are sorry for the inconvenience.
>
>Please tell Microsoft about this problem.
>
>Send Error Report  Don't Send
> 
>As an example, it is process number 3412.
>When I type
>$ kill -9 3412
>in the cygwin windows, it replies that the process
>bash: kill: (3412) - No such process
>or when I type
>$ kill -f 3412
>bash: kill: f: invalid signal specification
> 
>I'm not familiar with usage of kill -f, only kill -9
>so I'm confused on what is the appropriate usage
>to kill process 3412.  Also, trying to kill 2652 does
>not work with same message.
>I don't want to kill the original calling batch file
>because I want to let it continue.
>I only want to kill the hanging windows process.

You need to run the program "/bin/kill" rather than the bash
builtin "kill": /bin/kill -f 3412

cgf



--
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/
___
John R Larsen <[EMAIL PROTECTED]>
http://larsen-family.us

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

Re: cygwin and gmail problems? Remote host said: 530 5.7.0 Must issue a STARTTLS command first

[Matt Wilkie]

Okay, thanks for the responses.

-matt

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

RE: "ls" finds file1 but "ls file1" does not

[Gary R. Van Sickle]

> -Original Message-
> From: [EMAIL PROTECTED] 
> [mailto:[EMAIL PROTECTED] On Behalf Of Ross Smith
> Sent: Tuesday, May 10, 2005 4:33 PM
> To: cygwin@cygwin.com
> Subject: Re: "ls" finds file1 but "ls file1" does not
> 
> Charles D. Russell wrote:
> > Eric Blake wrote:
> > 
> >>  mv -v "$f" " ` echo $f | tr A-Z a-z ` "
> > 
> > EVIL - you are moving "FOO" to " foo " (Windows strips trailing 
> > spaces, but not leading spaces, so it is really moving to " foo").  
> > YOU ARE ADDING SPACES to the filename.  Fix your script so 
> that there 
> > are no spaces between "` and `".
> > _
> > 
> > Thought it was clever of me to make that little ` visible 
> to my old eyes.
> 
> I always use $(...) instead; it's equivalent to `...` and 
> much easier to read.
> 

... And suffers from far fewer nesting problems.

-- 
Gary R. Van Sickle


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

[ANNOUNCEMENT] Updated: unison2.10.2-2.10.2-2

[Schulman . Andrew]

A new version of the unison2.10.2 package is available in the Cygwin 
distribution.  Unison is a file synchronizer for Unix and Windows. It 
allows two replicas of a collection of files and directories to be stored 
on different hosts (or different disks on the same host), modified 
separately, and then brought up to date by propagating the changes in each 
replica to the other.

Changes in version 2.10.2-2:
* Fixed a bug in the -fastcheck option, that caused slow updates after the 
change to daylight savings time, unless archive files were deleted and 
rebuilt (http://groups.yahoo.com/group/unison-users/message/3821).

Andrew E. Schulman


***


To update your installation, click on the "Install Cygwin now" link on
the http://cygwin.com/ web page.  This downloads setup.exe to your
system.  Then, run setup and answer all of the questions.

  *** CYGWIN-ANNOUNCE UNSUBSCRIBE INFO ***

If you want to unsubscribe from the cygwin-announce mailing list, look
at the "List-Unsubscribe: " tag in the email header of this message.
Send email to the address specified there.  It will be in the format:

[EMAIL PROTECTED] 

If you need more information on unsubscribing, start reading here: 

http://sources.redhat.com/lists.html#unsubscribe-simple

Please read *all* of the information on unsubscribing that is available
starting at this URL.


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

[ANNOUNCEMENT] Updated: autossh-1.3-2

[Schulman . Andrew]

A new version of the autossh package is available in the Cygwin 
distribution.  autossh is a program to start an instance of ssh and 
monitor it, restarting it if it should die or stop passing traffic.

Changes in version 1.3-2:
* Clarify the documentation for running autossh as an NT system service.

Andrew E. Schulman


***


To update your installation, click on the "Install Cygwin now" link on
the http://cygwin.com/ web page.  This downloads setup.exe to your
system.  Then, run setup and answer all of the questions.

  *** CYGWIN-ANNOUNCE UNSUBSCRIBE INFO ***

If you want to unsubscribe from the cygwin-announce mailing list, look
at the "List-Unsubscribe: " tag in the email header of this message.
Send email to the address specified there.  It will be in the format:

[EMAIL PROTECTED] 

If you need more information on unsubscribing, start reading here: 

http://sources.redhat.com/lists.html#unsubscribe-simple

Please read *all* of the information on unsubscribing that is available
starting at this URL.


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

Re: how to kill windows process from bash shell?

[Christopher Faylor]

On Tue, May 10, 2005 at 03:07:40PM -0700, David Fong wrote:
>Hi,
>I need some help.
>I have one windows process (WinXP)  that is running
>from one cygwin window.
> 
>The process is hanging and I want to kill the process
>from another cygwin window.
>There is a separate spawned process from my program
>C:\windows\system32\dwwin.exe
>and it has a process number displayed when I run
>ps -W in a separate cygwin process.
> 
>2480 1172 2480 2480 con 11293 13:14:32
>/cygdriver/c/hw/destination/rundump.bat
>2816 0 0 2816 ? 0 13:41:32 C:\windows\system32\cmd.exe
>2652 0 0 2652 ? 0 13:41:32
>C:\hw\destination\cmodel\player\Player.exe
>3412 0 0 3412 ? 0 13:41:32
>C:\windows\system32\dwwin.exe
>The dos batch file (rundump.bat) runs cmd.exe which
>calls Player.exe which calls this dwwin.exe when error
>occurs
>which has message of
> 
>Player.exe has encountered a problem and needs to
>close.
>We are sorry for the inconvenience.
>
>Please tell Microsoft about this problem.
>
>Send Error Report  Don't Send
> 
>As an example, it is process number 3412.
>When I type
>$ kill -9 3412
>in the cygwin windows, it replies that the process
>bash: kill: (3412) - No such process
>or when I type
>$ kill -f 3412
>bash: kill: f: invalid signal specification
> 
>I'm not familiar with usage of kill -f, only kill -9
>so I'm confused on what is the appropriate usage
>to kill process 3412.  Also, trying to kill 2652 does
>not work with same message.
>I don't want to kill the original calling batch file
>because I want to let it continue.
>I only want to kill the hanging windows process.

You need to run the program "/bin/kill" rather than the bash
builtin "kill": /bin/kill -f 3412

cgf



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

how to kill windows process from bash shell?

[David Fong]

Hi,
I need some help.
I have one windows process (WinXP)  that is running
from one cygwin window.
 
The process is hanging and I want to kill the process
from another cygwin window.
There is a separate spawned process from my program
C:\windows\system32\dwwin.exe
and it has a process number displayed when I run
ps -W in a separate cygwin process.
 
2480 1172 2480 2480 con 11293 13:14:32
/cygdriver/c/hw/destination/rundump.bat
2816 0 0 2816 ? 0 13:41:32 C:\windows\system32\cmd.exe
2652 0 0 2652 ? 0 13:41:32
C:\hw\destination\cmodel\player\Player.exe
3412 0 0 3412 ? 0 13:41:32
C:\windows\system32\dwwin.exe
The dos batch file (rundump.bat) runs cmd.exe which
calls Player.exe which calls this dwwin.exe when error
occurs
which has message of
 
Player.exe has encountered a problem and needs to
close.
We are sorry for the inconvenience.

Please tell Microsoft about this problem.

Send Error Report  Don't Send
 
As an example, it is process number 3412.
When I type
$ kill -9 3412
in the cygwin windows, it replies that the process
bash: kill: (3412) - No such process
or when I type
$ kill -f 3412
bash: kill: f: invalid signal specification
 
I'm not familiar with usage of kill -f, only kill -9
so I'm confused on what is the appropriate usage
to kill process 3412.  Also, trying to kill 2652 does
not work with same message.
I don't want to kill the original calling batch file
because I want to let it continue.
I only want to kill the hanging windows process.
 
David
 




__ 
Do you Yahoo!? 
Yahoo! Small Business - Try our new resources site!
http://smallbusiness.yahoo.com/resources/ 

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

Can we download teTeX 3.00-3?

[Angelo Graziosi]

Jan,

Have you read  ?

Can we download 3.00-3 suite or we have to wait for 3.00-4?

WHY in teTeX 3.00-2 the directory .texmf is created in the $HOME directory
of the user who installed the packages of teTeX?

The others users?

angelo.


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

Re: Permissions problem mounting NFS shares from Cygwin sshd

[Chip Olson]

Quoth Larry Hall:
>At 03:03 PM 5/10/2005, you wrote:
> 
>
> 
>  I read in the archives that logging in with public-key authentication
>  can cause problems like this, and indeed, if I log in via ssh with -o
>  PubKeyAuthentication=no, the mount works fine (and reports my user's
>  UID and GID, not 0 for both as when I mount from the desktop).
> 
>  I have another machine here that mounts just fine from a public-key
>  ssh session. Unfortunately, the person who configured it is no longer
>  with the company. :-(
> 
>See the FAQ entry:
> 
>Why don't my services work (or access network shares)?
>< http://cygwin.com/faq/faq_toc.html#TOC33>

After reading the FAQ entry, the referenced cygrunsrv README and
http://cygwin.com/cygwin-ug-net/ntsec.html, I made the following
changes to my configuration, independently of each other:

- Changed the group IDs of Administrator and my user account from 513
(None) to 544 (Administrators). This had no effect.

- Reinstalled sshd so as to log in as Administrator, as follows: 

cygrunsrv --install sshd -u Administrator -w mypasswd -p /usr/sbin/sshd.exe

When I subsequently ran cygrunsrv --start sshd, I got: 
cygrunsrv: Error starting a service:  QueryServiceStatus: Win32 error 1053:
The service did not respond to the start or control request in a timely fashion.

sshd was then hung in "starting" state, according to Service Manager,
and I had to reboot to clear it.

-- 
-Chip Olson | [EMAIL PROTECTED] | "And the sands will roll out a carpet of 
gold / For your weary toes to be a-touchin' / And the ship's wise men 
will remind you once again / The whole wide world is watchin'"  
 -Bob Dylan, "When The Ship Comes In"

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

Re: "ls" finds file1 but "ls file1" does not

[Ross Smith]

Charles D. Russell wrote:
Eric Blake wrote:
 mv -v "$f" " ` echo $f | tr A-Z a-z ` "
EVIL - you are moving "FOO" to " foo " (Windows strips trailing spaces, 
but not leading spaces, so it is really moving to " foo").  YOU ARE 
ADDING SPACES to the filename.  Fix your script so that there are no 
spaces between "` and `".
_

Thought it was clever of me to make that little ` visible to my old eyes.
I always use $(...) instead; it's equivalent to `...` and much easier to 
read.

--
Ross Smith .. Pharos Systems, Auckland, New Zealand
"Carelessly planned projects take three times longer to complete than
expected. Carefully planned projects take four times longer to
complete than expected, mostly because the planners expect their
planning to reduce the time it takes." -- Anon.
--
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/

Re: memory for large fortran arrays: problem fixed

[Mark Hadfield]

Charles D. Russell wrote:
The following seems important enough to fortran users
> to be indexed by an appropriate subject header.

 I am reluctant to upgrade because the use of large static
 fortran arrays with cygwin/g77 seems to be a fragile issue
 and my current installation is now working (but only with
>>  -mno-cygwin).
 That one is *well-and-truely* fixed, solved, sorted,
straightened out, banged on the head, put to bed, laid to rest,
and otherwise dealt with! Really!  I'm not sure if the fix was
in 1.5.16 or if you'd need to use a recent snapshot,
The fix was in a post-1.5.16 snapshot, ca 29 April. See
  http://cygwin.com/ml/cygwin/2005-04/msg01309.html
  http://cygwin.com/ml/cygwin/2005-04/msg01337.html
> but the underlying problem is *completely* gone
Thanks for confirming that.
and will not be returning any time soon.
Now that's just tempting fate...
--
Mark Hadfield"Ka puwaha te tai nei, Hoea tatou"
[EMAIL PROTECTED]
National Institute for Water and Atmospheric Research (NIWA)
--
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/

Re: Help with error in vi and man

[Corinna Vinschen]

On May 10 10:41, Trevor Osatchuk wrote:
>  One thing that I am still curious is /lib/terminfo.  This is a sym
> link to a nonexistant directory.  Is this an error in the install?  It
> doesn't seem to affect my current install but I wonder if it breaks
> something that I don't currently use.

Try `ls -l /usr/lib/terminfo' ;-)

If you look into /etc/postinstall/terminfo.sh.done you get a description.


Corinna

-- 
Corinna Vinschen  Please, send mails regarding Cygwin to
Cygwin Project Co-Leader  mailto:cygwin@cygwin.com
Red Hat, Inc.

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

Problem with ls and EACCESS

[Mark Paulus]

I have been trying out the ext2 read/write IFS driver
for WinXP, and it seems to work nicely.  However, I 
have noticed this one issue.

In /, I have a couple of symbolic links to kernels.  When
I look at them in a windows command prompt, I see the link as a 
file:  
08/12/2004  05:45 AM20 vmlinuz.knoppix
and if I try to look inside, 
L:\>type vmlinuz.knoppix
Access is denied.

So far, all is good.

However, when I try to look at the directory under cygwin:
$ ls /cygdrive/l/vmlinuz.knoppix
ls: /cygdrive/l/vmlinuz.knoppix: No such file or directory

I have pulled an strace of this, and it looks like someone
is skipping the error EACCESS or ignoring it, and somehow
is transmuting the EACCESS into ENOENT.

   37  116938 [main] ls 2268 normalize_posix_path: src 
/cygdrive/l/vmlinuz.knoppix
   37  116975 [main] ls 2268 normalize_posix_path: /cygdrive/l/vmlinuz.knoppix 
=  normalize_posix_path (/cygdrive/l/vmlinuz.knoppix)
   37  117012 [main] ls 2268 mount_info::conv_to_win32_path: 
conv_to_win32_path(/cygdrive/l/vmlinuz.knoppix)
   38  117050 [main] ls 2268 mount_info::cygdrive_win32_path: src 
'/cygdrive/l/vmlinuz.knoppix', dst 'l:\vmlinuz.knoppix'
   37  117087 [main] ls 2268 set_flags: flags: binary (0x2)
   35  117122 [main] ls 2268 mount_info::conv_to_win32_path: src_path 
/cygdrive/l/vmlinuz.knoppix, dst l:\vmlinuz.knoppix, flags 0x2A, rc 0
  172  117294 [main] ls 2268 symlink_info::check: GetFileAttributes 
(l:\vmlinuz.knoppix) failed
   44  117338 [main] ls 2268 geterrno_from_win_error: windows error 5 == errno 
13
  122  117460 [main] ls 2268 symlink_info::check: GetFileAttributes 
(l:\vmlinuz.knoppix.exe) failed
   41  117501 [main] ls 2268 geterrno_from_win_error: windows error 2 == errno 
2  
121  117622 [main] ls 2268 symlink_info::check: GetFileAttributes 
(l:\vmlinuz.knoppix.exe.lnk) failed
   93  117715 [main] ls 2268 geterrno_from_win_error: windows error 2 == errno 2
  124  117839 [main] ls 2268 symlink_info::check: GetFileAttributes 
(l:\vmlinuz.knoppix.lnk) failed
   40  117879 [main] ls 2268 geterrno_from_win_error: windows error 2 == errno 2
   34  117913 [main] ls 2268 symlink_info::check: 0 = symlink.check 
(l:\vmlinuz.knoppix, 0x22E5D0) (0x2A)



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

Re: Help with error in vi and man

[Trevor Osatchuk]

On 5/10/05, Christopher Faylor <[EMAIL PROTECTED]> wrote:
> On Mon, May 09, 2005 at 10:20:55AM -0600, Trevor Osatchuk wrote:
> >On 5/7/05, Christopher Faylor <[EMAIL PROTECTED]> wrote:
> >> On Sat, May 07, 2005 at 06:27:59PM -0600, Trevor Osatchuk wrote:
> >> >On 5/7/05, Christopher Faylor <[EMAIL PROTECTED]> wrote:
> >> >> On Fri, May 06, 2005 at 10:59:22PM -0600, Trevor Osatchuk wrote:
> >> >> >When starting up vi/vim I get the following error:
> >> >> >
> >> >> >E558: Terminal entry not found in terminfo
> >> >> >'cygwin' not known. Available builtin terminals are:
> >> >> >builtin_ansi
> >> >> >builtin_xterm
> >> >> >builtin_iris-ansi
> >> >> >builtin_dumb
> >> >> >defaulting to ansi
> >> >> >
> >> >> >Help does not work for vim I get the error:
> >> >> >
> >> >> >E433: No tags file
> >> >> >E149: Sorry, no help for help.txt
> >> >> >
> >> >> >Also when I type in the man command, man ls for example, all I get is
> >> >> >(END) and no man page.  Like it paged to the end.  I don't currently
> >> >> >have a pager environment variable.  My manpath is correct.
> >> >> >
> >> >> >Any ideas?
> >> >>
> >> >> Run the cygwin version of vim, i.e., /usr/bin/vim?  You're obviously
> >> >> running some other version.  "which vim" would probably show which
> >> >> version you're running.
> >> >>
> >> >Obviously is a strong word!  Which vim yeilds /usr/bin/vim.  I have
> >> >seen these symtoms in other posts, though no solutions.
> >>
> >> Ok.  Perhaps your terminfo installation is screwed up or nonexistent.
> >>
> >> If you're scouring old posts then maybe you've come across the concept
> >> of following the instructions at http://cygwin.com/problems.html , as
> >> has already been sugested.  These instructions would help you send
> >> problems in such a way that we wouldn't have to guess about things like
> >> what version of vim you're running or whether you even have terminfo
> >> installed.
> >>
> >I apologize for not sending the expected information and format.  LART 
> >accepted.
> >
> >I am running CYGWIN_NT-5.1, I got that from uname.
> >
> >I think that terminfo may in fact be the correct diagnosis.  I found a
> >symlink of terminfo in /lib where terminfo was pointing to
> >../share/terminfo.  There is no /share directory.  If you look in my
> >cygcheck.out you will find that terminfo 5.4_20041009-1 is listed as
> >installed.  So, is my installation of terminfo broken?  What do  I
> >need to do to fix it?
> 
> Install terminfo.
> 
I did install and reinstall terminfo to no avail.  I also did a
reinstall of Base to no avail.  I just finished a complete reinstall
and now it all works.  I must have screwed something up along the way.
 One thing that I am still curious is /lib/terminfo.  This is a sym
link to a nonexistant directory.  Is this an error in the install?  It
doesn't seem to affect my current install but I wonder if it breaks
something that I don't currently use.

Thanks for all of the suggestions.

fybar

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

Re: Strange-Dangerous behaviour in Cygwin

[Angelo Graziosi]

I have not changed anything in configuration (I have not "touched" any
thing in " /etc/profile " etc.)

Until some days ago all worked fine. With some upgrades or i do not know
"what" the BACKSPACE does not work correctly in answering at command like
rm -i: it works as a LEFT arrow key. This happens in standard
(cygwin.bat) bash shell and in xterm but NO in RXVT or in DOS box
(CMD.EXE) with c:\cygwin\bin in PATH (i.e. using rm -i in DOS box).

As I wrote, I have reinstalled cygwin using only BASE packages to verify
the strange behaviour.

My settings:


$ stty -a
speed 38400 baud; rows 25; columns 80; line = 0;
intr = ^C; quit = ^\; erase = ^?; kill = ^U; eof = ^D; eol = ;
eol2 = ; swtch = ^Z; start = ^Q; stop = ^S; susp = ^Z; rprnt = ^R;
werase = ^W; lnext = ^V; flush = ^O; min = 1; time = 0;
-parenb -parodd cs8 -hupcl -cstopb cread -clocal -crtscts
-ignbrk brkint -ignpar -parmrk -inpck -istrip -inlcr -igncr icrnl ixon
-ixoff
-iuclc -ixany -imaxbel
opost -olcuc -ocrnl onlcr -onocr -onlret -ofill -ofdel nl0 cr0 tab0 bs0
vt0 ff0
isig icanon iexten echo -echoe -echok -echonl -noflsh -tostop -echoctl
-echoke

I get the previous output in standard bash shell, in RXVT and xterm (and
I noted erase=^?).

In standard bash shell:

$ echo $TERM
cygwin

In RXVT and xterm:
$ echo $TERM
xterm

If I type BACKSPACE at prompt (bash, RXVT, xterm) I get a "beep"

If I type 

$rm -i foo.txt
rm: remove regular file `foo.txt'?yBAKSPACEn

the cursor is moved left on "y" (or under "y" in standard bash
shell): it does not delete the "y"; then the "n" overwrite the "y" but the
command (rm -i) read the first character typed, so the file 'foo.txt' is
deleted.

I have discovered this strange behaviour with the lost of some (not
important, fortunately) files. 


If I type

$ [CTRL-v]BACKSPACE

I get

$ ^H

If I type (using copy paste from your mail)

$ stty erase ^H

then the BACKSPACE work fine (in answering e.g. rm -i)

but 

$ stty
speed 38400 baud; line = 0;
-imaxbel
-echoe -echok -echoctl -echoke

Where is "erase = ..."?

closing the shell, the next time I have the previous wrong behaviour of
BACKSPACE!

Should I reimpost "stty erase ..." every time?

However the questions are:

There is a bug in Cygwin?

Have I inadvertently changed something?

How can I adjust?

I have read the replays but I am confused.

Thanks,
angelo.


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

Re: Static destructors not running

[William M. (Mike) Miller]

On 5/10/05, Christopher Faylor <[EMAIL PROTECTED]> wrote:
> On Tue, May 10, 2005 at 03:27:02PM -0400, William M. (Mike) Miller wrote:
> >On 5/10/05, Christopher Faylor <[EMAIL PROTECTED]> wrote:
> >> Previous to 1.5.16, static destructors were always called via a
> >> gcc "atexit" mechanism.  This meant that there were scenarios where
> >> destructors would not be called at all so I made cygwin's exit call
> >> the destructors explicitly.   I just forgot to make cygwin do the right
> >> thing when returning from main rather than exiting.  This will be
> >> fixed in the next snapshot.
> >
> >Sorry, one more question.  I thought from the above that
> >reinstalling 1.5.15 would restore the previous behavior for static
> >destructors.  According to cygcheck, I now have cygwin 1.5.15-1
> >installed, but I still don't see the static destructor output.  Is there
> >something else I need to revert while waiting for the fix?
> 
> Install the snapshot:  http://cygwin.com/snapshots/

Yep, fixed.  Thanks again.

-- 
William M. (Mike) Miller | Edison Design Group
[EMAIL PROTECTED]

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

Re: Strange-Dangerous behaviour in Cygwin [ATTN base-file maintainer]

[Corinna Vinschen]

On May 10 18:53, John Morrison wrote:
> On Tue, May 10, 2005 6:25 pm, Corinna Vinschen said:
> > Can we stop this discussion and just do it right in /etc/profile by
> > just not setting it?
> 
> Humm, sorry I've just started reading this thread, does the
> /etc/skel/.inputrc have any (appologies for the pun) input into this?  I'm
> willing to fix this - but I need somebody to tell me what's needed done :)

Nothing to do.  Backspace isn't handled in .inputrc.


Corinna

-- 
Corinna Vinschen  Please, send mails regarding Cygwin to
Cygwin Project Co-Leader  mailto:cygwin@cygwin.com
Red Hat, Inc.

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

Re: Today I "overinstalled" Cygwin!

[Larry Hall]

At 02:02 PM 5/10/2005, you wrote:
>see attached screenshot:
>
>Cygwin Setup at 146% !!
>


Congratulations!  You're certainly a Cygwin over-achiever! ;-)


--
Larry Hall  http://www.rfk.com
RFK Partners, Inc.  (508) 893-9779 - RFK Office
838 Washington Street   (508) 893-9889 - FAX
Holliston, MA 01746 


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

Re: postgresql and sockets

[Krzysztof Duleba]

Corinna Vinschen wrote:

> No more debugging necessary.  I found the cause of the problem.  At one
> point the file attributes were not correctly stored for socket files and
> when postgres touches the socket file (which it does every 5 minutes),
> the correct file attributes got lost.  Especially the system bit got
lost,
> which is important to recognize the file as a socket.
>
> I've applied a patch to CVS which will show up in the next developers
> snapshot on http://cygwin.com/snapshots/

I've downloaded the snapshot and everything seems fine now. Thanks for
fixing that!

Regards
Krzysztof Duleba



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

Re: Static destructors not running

[Christopher Faylor]

On Tue, May 10, 2005 at 03:27:02PM -0400, William M. (Mike) Miller wrote:
>On 5/10/05, Christopher Faylor <[EMAIL PROTECTED]> wrote:
>> Previous to 1.5.16, static destructors were always called via a
>> gcc "atexit" mechanism.  This meant that there were scenarios where
>> destructors would not be called at all so I made cygwin's exit call
>> the destructors explicitly.   I just forgot to make cygwin do the right
>> thing when returning from main rather than exiting.  This will be
>> fixed in the next snapshot.
>
>Sorry, one more question.  I thought from the above that
>reinstalling 1.5.15 would restore the previous behavior for static
>destructors.  According to cygcheck, I now have cygwin 1.5.15-1
>installed, but I still don't see the static destructor output.  Is there
>something else I need to revert while waiting for the fix?

Install the snapshot:  http://cygwin.com/snapshots/

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

Re: Static destructors not running

[William M. (Mike) Miller]

On 5/10/05, Christopher Faylor <[EMAIL PROTECTED]> wrote:
> Previous to 1.5.16, static destructors were always called via a
> gcc "atexit" mechanism.  This meant that there were scenarios where
> destructors would not be called at all so I made cygwin's exit call
> the destructors explicitly.   I just forgot to make cygwin do the right
> thing when returning from main rather than exiting.  This will be
> fixed in the next snapshot.

Sorry, one more question.  I thought from the above that
reinstalling 1.5.15 would restore the previous behavior for static
destructors.  According to cygcheck, I now have cygwin 1.5.15-1
installed, but I still don't see the static destructor output.  Is there
something else I need to revert while waiting for the fix?

Thanks again.

-- 
William M. (Mike) Miller
[EMAIL PROTECTED]

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

Permissions problem mounting NFS shares from Cygwin sshd

[Chip Olson]

For reasons too complicated to explain, I need to configure a Windows
2000 machine to mount NFS shares from a Cygwin sshd session. The NFS
mounting part of this is taken care of by Windows Services for Unix,
and I have User Name Mapping set up so that my Windows user account
mounts as its Unix counterpart. If I run the SFU mount command from a
bash shell on the Windows desktop, all is peachy, and it mounts with
UID and GID both 0. If I mount from an SSH login, however, it mounts
with UID and GID both -2, aka nobody, and I don't have write access on
the NFS share.

I'm pretty sure that what I need to do is configure the Cygwin sshd
service to log in as Administrator, rather than as "local
user". However, when I configure it that way and restart the sshd
service, it fails to start. In the error log, I get "...starting
service `sshd' failed: execv: 128, Transport endpoint is not
connected". On one or two occasions, I got "permission denied" errors
from either starting sshd or writing to its logfile.

I read in the archives that logging in with public-key authentication
can cause problems like this, and indeed, if I log in via ssh with -o
PubKeyAuthentication=no, the mount works fine (and reports my user's
UID and GID, not 0 for both as when I mount from the desktop). 

I have another machine here that mounts just fine from a public-key
ssh session. Unfortunately, the person who configured it is no longer
with the company. :-(

The really irritating aspect of this is that, when sshd fails to
start, it is now stuck in state "starting", and the usual stop, start
etc. buttons are greyed out. It appears the only way to get it out of
that state is Windows Troubleshooting Procedure Number 1, aka
reboot. (Number 2 is, of course, reinstall the operating system).

Many thanks for any hints.

-- 
-Chip Olson | [EMAIL PROTECTED] | "And the sands will roll out a carpet of 
gold / For your weary toes to be a-touchin' / And the ship's wise men 
will remind you once again / The whole wide world is watchin'"  
 -Bob Dylan, "When The Ship Comes In"

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

Re: cygwin and gmail problems? Remote host said: 530 5.7.0 Must issue a STARTTLS command first

[Jim Drash]

> gmail doesn't seem to like messages from the cygwin mailing list
> today. Did anybody else get a notice like this?
> 

gmail has no problems with cygwin mail at all. I read you post and am
writing this reply using gmail right now

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

memory for large fortran arrays: problem fixed

[Charles D. Russell]

The following seems important enough to fortran users to be indexed by 
an appropriate subject header.

 I am reluctant to upgrade because the use of large static fortran
 arrays with cygwin/g77 seems to be a fragile issue and my current
 installation is now working (but only with -mno-cygwin).
 

 That one is *well-and-truely* fixed, solved, sorted, straightened out,
banged on the head, put to bed, laid to rest, and otherwise dealt with!
Really!  I'm not sure if the fix was in 1.5.16 or if you'd need to use a
recent snapshot, but the underlying problem is *completely* gone and will
not be returning any time soon.  I would deeply urge you not to let any
worries about it hold you back from upgrading.
 Oh, and even better, you won't need "-mno-cygwin" any more.  Here, let me
quote this testimonial from a satisfied customer:
"  Yeaaah, boy!  That got it!  Using cygwin1-20050428.dll,
I can now run g77 executables having a static array up to about
1.5 GiB.  [ ... ] But still, this meets my needs, and I don't need
that silly -Wl,--stack,8388608 workaround anymore.  Job well done,
both you and Corinna! "
[ With apologies to the nameless OP for quoting from a private email, but
hey, it's not exactly intimate or personal! ]
   cheers,
 DaveK
--
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/

Re: "ls" finds file1 but "ls file1" does not

[Charles D. Russell]

Eric Blake wrote:
 mv -v "$f" " ` echo $f | tr A-Z a-z ` "
EVIL - you are moving "FOO" to " foo " (Windows strips trailing spaces, 
but not leading spaces, so it is really moving to " foo").  YOU ARE 
ADDING SPACES to the filename.  Fix your script so that there are no 
spaces between "` and `".
_

Thought it was clever of me to make that little ` visible to my old eyes.
___
Also, as mentioned elsewhere, `ls -q' or `ls -Q' would have made this 
apparent.
__

ls -Q does, if invoked as "ls -Q" and not as "ls -Q as*"
Thanks for the help, and sorry for an inquiry that turned out to be 
off-topic.
_

I am reluctant to upgrade because the use of large static
 fortran arrays with cygwin/g77 seems to be a fragile issue and my
 current installation is now working (but only with -mno-cygwin).

 
Dave Korn wrote:
 That one is *well-and-truely* fixed, solved, sorted, straightened out,
banged on the head, put to bed, laid to rest, and otherwise dealt with!
___
Many thanks to the cygwin folks.  I thought that fix would have to 
await the impending replacement of g77 with gfortran.

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

Windows XP 5.1.2600/Rsync freezes and does not copy any files

[David Secret]

I was trying to tunnel a file transfer via SSH from a Windows XP 
5.1.2600 machine to a Windows 2003 machine, it seemed SSH was freezing 
but after further testing rsync seems completely incapable of 
operation.  Doing a simple:

$ ls /tmp/a
a.txt b.txt c.txt
cd /tmp
rsync -r -v a b
cmd= machine= user= path=b
cmd=. b
(rsync then does NOTHING for hours.)
(Hitting ^C results in:)
_exit_cleanup(code=20, file=/home/lapo/packaging/tmp/rsync-2.6.3/rsync.c 
line=231): entered
rsync error: received SIGUSR1 or SIGINT (code 20) at 
/home/lapo/packaging/tmp/rsync-2.6.3/rsync.c(231)
_exit_cleanup(code=20, file=/home/lapo/packaging/tmp/rsync-2.5.3/rsync.c 
line=231: about to call exit(20)_exit_cleanup(code=20, 
file=/home/lapo/packaging/tmp/rsync-2.6.3/main.c, line=965): entered
..

Any ideas what is going on?  It won't even copy a simple 3 file 
directory where the files are around 10 bytes each.  This works GREAT 
under Windows 2003, and Windows 2000... If you have any ideas of how to 
debug this, or where to look it would be greatly appreciated.  Please 
cc: my email address on any replies :)

--David

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

Today I "overinstalled" Cygwin!

[Marco Lechner]

see attached screenshot:

Cygwin Setup at 146% !!

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

Re: Strange-Dangerous behaviour in Cygwin [ATTN base-file maintainer]

[John Morrison]

On Tue, May 10, 2005 6:25 pm, Corinna Vinschen said:
> On May 10 11:18, Warren Young wrote:
>> Corinna Vinschen wrote:
>>
>> >Can anybody tell me what the `stty erase' setting is good for in
>> >/etc/profile?  I'm using tcsh, so I'm not bothered by this stuff...
>>
>> This is fine as long are you're within your shell, or another program
>> that is tolerant of the two different ways of saying 'backspace'.
>>
>> If your 'erase' stty variable isn't set correctly, a number of things
>> fail to deal with backspace correctly.  For just one example, password
>> entry when ssh'ing to another machine requires a correct 'erase'
>> setting.
>
> Yes.  Did you notice what I said?  It's set automatically correctly for
> rxvt and the cygwin console and xterm if you *don't* touch it in
> /etc/profile.
>
> Can we stop this discussion and just do it right in /etc/profile by
> just not setting it?

Humm, sorry I've just started reading this thread, does the
/etc/skel/.inputrc have any (appologies for the pun) input into this?  I'm
willing to fix this - but I need somebody to tell me what's needed done :)

J.


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

RE: Building GCC-4.0-20050430

[Anh Vo]

There is a bug preventing from using MinGW/MSYS to build it successfully. Of 
course, this bug has reported by folks at MinGW.

I am in agreement that Ada compiler is not complete if run-time tasking is not 
supported. Is there any plan to support it in the future?

AV 

>>> "Williams, Gerald S (Jerry)" <[EMAIL PROTECTED]> 05/10/05 6:02 AM >>>
OT for this list, but you may be interested to know that the
MINGW version supports Ada tasking.

I haven't delved into it, but the GNAT manual indicates that
Ada tasking support is pretty simple if you have a minimal
amount of POSIX support. Of course, you discovered that it
doesn't quite work OOTB. Since I was just toying around when
I ran into this, I found it easier to just install MINGW.
Personally, I don't see the point in supporting Ada if you
don't support tasking, but maybe that's just me. :-)



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

Re: Static destructors not running

[William M. (Mike) Miller]

On 5/10/05, Christopher Faylor <[EMAIL PROTECTED]> wrote:
> On Tue, May 10, 2005 at 11:54:45AM -0400, William M. (Mike) Miller wrote:
> >Yes, the output does appear when I call exit instead of returning
> >from main().  Unfortunately, that's not an option.  For one thing,
> >this is shared code that works just fine on other systems (and
> >under Cygwin until I updated last Friday).  For another, the
> >semantics of calling exit in main() are not exactly the same as
> >returning from main() -- local automatic objects in main() are not
> >destroyed by the exit() call, which is something some of this
> >code that is now failing relies on.
> 
> I was trying to figure out the problem, not suggest that you should
> change all of your code.

Sorry, my misunderstanding.

> Previous to 1.5.16, static destructors were always called via a
> gcc "atexit" mechanism.  This meant that there were scenarios where
> destructors would not be called at all so I made cygwin's exit call
> the destructors explicitly.   I just forgot to make cygwin do the right
> thing when returning from main rather than exiting.  This will be
> fixed in the next snapshot.

Great!  Thanks very much.

-- 
William M. (Mike) Miller | Edison Design Group
[EMAIL PROTECTED]

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

Re: Strange-Dangerous behaviour in Cygwin [ATTN base-file maintainer]

[Corinna Vinschen]

On May 10 11:18, Warren Young wrote:
> Corinna Vinschen wrote:
> 
> >Can anybody tell me what the `stty erase' setting is good for in
> >/etc/profile?  I'm using tcsh, so I'm not bothered by this stuff...
> 
> This is fine as long are you're within your shell, or another program 
> that is tolerant of the two different ways of saying 'backspace'.
> 
> If your 'erase' stty variable isn't set correctly, a number of things 
> fail to deal with backspace correctly.  For just one example, password 
> entry when ssh'ing to another machine requires a correct 'erase' setting.

Yes.  Did you notice what I said?  It's set automatically correctly for
rxvt and the cygwin console and xterm if you *don't* touch it in
/etc/profile.

Can we stop this discussion and just do it right in /etc/profile by
just not setting it?


Corinna

-- 
Corinna Vinschen  Please, send mails regarding Cygwin to
Cygwin Project Co-Leader  mailto:cygwin@cygwin.com
Red Hat, Inc.

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

Re: Strange-Dangerous behaviour in Cygwin [ATTN base-file maintainer]

[Warren Young]

Corinna Vinschen wrote:
Can anybody tell me what the `stty erase' setting is good for in
/etc/profile?  I'm using tcsh, so I'm not bothered by this stuff...
This is fine as long are you're within your shell, or another program 
that is tolerant of the two different ways of saying 'backspace'.

If your 'erase' stty variable isn't set correctly, a number of things 
fail to deal with backspace correctly.  For just one example, password 
entry when ssh'ing to another machine requires a correct 'erase' setting.

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

Re: cygwin and gmail problems? Remote host said: 530 5.7.0 Must issue a STARTTLS command first

[Christopher Faylor]

On Tue, May 10, 2005 at 10:04:23AM -0700, Matt Wilkie wrote:
>gmail doesn't seem to like messages from the cygwin mailing list
>today. Did anybody else get a notice like this?

This is not an issue for the cygwin mailing list and it is actually
unlikely to be an issue for sourceware.org.  It seems like gmail was
having problems.  You should contact them.

cgf

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

Re: Strange-Dangerous behaviour in Cygwin [ATTN base-file maintainer]

[Eric Blake]

> I get ^H in a cmd window, an rxvt window, and an xterm window.
> 

Hmm, it's been more than 1.5 years since I got cygwin working how I like it, so 
I don't remember exactly what I did, but these lines in /etc/profile are 
helpful:

# Consistent BackSpace and Delete Configuration:
#   http://www.ibb.net/~anne/keyboard.html


Trying this:

$ for term in cygwin xterm rxvt ; do
> infocmp cygwin | grep kbs
> done

shows that my terminfo database still claims the backspace key is currently ^H 
for all three terminals, even though I seem to recall trying to change kbs=^? 
at one point.

Ahah - I think I found it - in my ~/.Xdefaults, I added
Rxvt*backspacekey: \177
*VT100.Translations: #override \
  BackSpace: string(0x7f)\n\
  Delete: string("\033[3~")
*ttyModes: erase ^?


At any rate, setting `stty erase '^?'' when backspace generates ^H is the wrong 
thing to do.  And if it is possible, it would be much nicer if cygwin could 
distinguish between [ctrl-h] and [backspace], so that the two keys can be 
distinguished (it is nice to have [ctrl-h] be help, and [backspace] be a 
deletion command, in terminal-based emacs).  And it would be really nice if the 
terminfo and termcap databases accurately reflected the true nature of the 
cygwin terminal, as to which sequences are needed to affect the screen and 
which sequences should pass through to the application.

--
Eric Blake



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

cygwin and gmail problems? Remote host said: 530 5.7.0 Must issue a STARTTLS command first

[Matt Wilkie]

Hi All,

gmail doesn't seem to like messages from the cygwin mailing list
today. Did anybody else get a notice like this?

-matt

-- Forwarded message --
From: [EMAIL PROTECTED] <[EMAIL PROTECTED]>
Date: 10 May 2005 16:48:06 -
Subject: ezmlm warning
To: [EMAIL PROTECTED]


Hi! This is the ezmlm program. I'm managing the
cygwin@cygwin.com mailing list.

Messages to you from the cygwin mailing list seem to
have been bouncing. I've attached a copy of the first bounce
message I received.

If this message bounces too, I will send you a probe. If the probe bounces,
I will remove your address from the cygwin mailing list,
without further notice.

I've kept a list of which messages from the cygwin mailing list have
bounced from your address.

Copies of these messages may be in the archive.
To retrieve a set of messages 123-145 (a maximum of 100 per request),
send an empty message to:
   <[EMAIL PROTECTED]>

To receive a subject and author list for the last 100 or so messages,
send an empty message to:
   <[EMAIL PROTECTED]>

Here are the message numbers:

   106908
   106909
   106910
   106911
   106912
   106913
   106914

--- Enclosed is a copy of the bounce message I received.

Return-Path: <>
Received: (qmail 22555 invoked for bounce); 28 Apr 2005 23:28:08 -
Date: 28 Apr 2005 23:28:08 -
From: [EMAIL PROTECTED]
To: [EMAIL PROTECTED]
MIME-Version: 1.0
Content-Type: multipart/mixed; boundary="1114711286sourceware.org1412055"
Subject: failure notice

Hi. This is the qmail-send program at sourceware.org.
I'm afraid I wasn't able to deliver your message to the following addresses.
This is a permanent error; I've given up. Sorry it didn't work out.

<[EMAIL PROTECTED]>:
Connected to 64.233.171.109 but sender was rejected.
Remote host said: 530 5.7.0 Must issue a STARTTLS command first



-- 
-matt

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

Re: Strange-Dangerous behaviour in Cygwin [ATTN base-file maintainer]

[Christopher Faylor]

[responding to no one in particular]
On Cygwin when you hit Backspace you get a ^H.  Cygwin has been doing
this for many years and it is duly recorded in terminfo and termcap that
way.  Changing this would require updating terminfo and termcap not just
on cygwin but on every system which has a cygwin terminfo entry.

So, while the choice by Cygwin's founders was regrettable, we're not
going to be changing it.  And, there is no bug here that I can see
other than my previous buggy email reading.

cgf

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

Re: Strange-Dangerous behaviour in Cygwin [ATTN base-file maintainer]

[Corinna Vinschen]

On May 10 15:47, Eric Blake wrote:
> /etc/profile (actually etc/defaults/etc/profile) needs to be updated like so, 
> to match the current default behavior of the cygwin terminal settings:
> 
> --- /etc/defaults/etc/profile.orig  2005-03-25 08:50:00.003125000 -0700
> +++ /etc/defaults/etc/profile1  2005-05-10 09:40:05.474375000 -0600
> @@ -1,4 +1,4 @@
> -# base-files version 3.2-1
> +# base-files version 3.2-1 -*- sh -*-
>  
>  # WARNING
>  #
> @@ -101,7 +101,12 @@
>  $ '
>  
> if tty --quiet ; then
> -   stty erase '^?'
> +   case "$TERM" in
> +   cygwin ) stty erase ^H ;;
> +   xterm* | rxvt* ) stty erase '^?' ;;
> +   * ) # unknown terminal type, don't set erase
> +   ;;
> +   esac
> fi
> ;;
>  ksh* | -ksh* | */ksh* | \

Can anybody tell me what the `stty erase' setting is good for in
/etc/profile?  I'm using tcsh, so I'm not bothered by this stuff, but
setting it looks entirely unnecessary.  The stty settings are fine
automatically if you don't set them, in the Cygwin console as well as
in rxvt.


Corinna

-- 
Corinna Vinschen  Please, send mails regarding Cygwin to
Cygwin Project Co-Leader  mailto:cygwin@cygwin.com
Red Hat, Inc.

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

Re: Strange-Dangerous behaviour in Cygwin [ATTN base-file maintainer]

[David Rothenberger]

On 5/10/2005 8:47 AM, Eric Blake wrote:
I think I may have a culprit.  When I run bash in a cmd window:
$ [ctrl-v][backspace]
^H
$ echo $TERM
cygwin
When I run it in an rxvt or xterm window:
$ [ctrl-v][backspace]
^?
$ echo $TERM
xterm
I get ^H in a cmd window, an rxvt window, and an xterm window.
--
David Rothenbergerspammer? -> [EMAIL PROTECTED]
GPG/PGP: 0x7F67E734, C233 365A 25EF 2C5F C8E1 43DF B44F BA26 7F67 E734
Never offend people with style when you can offend them with substance.
-- Sam Brown, "The Washington Post", January 26, 1977
--
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/

RE: Help !!! - Problem running Cygwin in Remote Desktop session with non-admin privileges

[Larry Hall]

At 08:24 AM 5/10/2005, you wrote:
>I want to download Cygwin 1.5.16.
>
>Please let me know which mirror site hosts this version.
>
>Thanks.


Any mirror sites offered by 'setup.exe' are all considered to be active 
mirrors.  If your favorite one doesn't have the update you want, please
check to make sure your mirror still shows up in the list 
().  If it doesn't, choose another.  If
it does, you can choose to wait a little while and see if it gets updated 
(though it really should be by now if the mirror is indeed active) or pick
another mirror site off the list.




--
Larry Hall  http://www.rfk.com
RFK Partners, Inc.  (508) 893-9779 - RFK Office
838 Washington Street   (508) 893-9889 - FAX
Holliston, MA 01746 


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

RE: "ls" finds file1 but "ls file1" does not

[Dave Korn]

Original Message
>From: Charles D. Russell
>Sent: 10 May 2005 16:54

> __
> I am attaching cygcheck in case you can find something obvious.
> However,I am reluctant to upgrade because the use of large static
> fortran arrays with cygwin/g77 seems to be a fragile issue and my
> current installation is now working (but only with -mno-cygwin).
> 


  That one is *well-and-truely* fixed, solved, sorted, straightened out,
banged on the head, put to bed, laid to rest, and otherwise dealt with!
Really!  I'm not sure if the fix was in 1.5.16 or if you'd need to use a
recent snapshot, but the underlying problem is *completely* gone and will
not be returning any time soon.  I would deeply urge you not to let any
worries about it hold you back from upgrading.

  Oh, and even better, you won't need "-mno-cygwin" any more.  Here, let me
quote this testimonial from a satisfied customer:


"  Yeaaah, boy!  That got it!  Using cygwin1-20050428.dll,
I can now run g77 executables having a static array up to about
1.5 GiB.  [ ... ] But still, this meets my needs, and I don't need
that silly -Wl,--stack,8388608 workaround anymore.  Job well done,
both you and Corinna! "


[ With apologies to the nameless OP for quoting from a private email, but
hey, it's not exactly intimate or personal! ]

cheers,
  DaveK
-- 
Can't think of a witty .sigline today


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

Re: "ls" finds file1 but "ls file1" does not

[Eric Blake]

>   mv -v "$f" " ` echo $f | tr A-Z a-z ` "

EVIL - you are moving "FOO" to " foo " (Windows strips trailing spaces, but not 
leading spaces, so it is really moving to " foo").  YOU ARE ADDING SPACES to 
the filename.  Fix your script so that there are no spaces between "` and `".

Also, as mentioned elsewhere, `ls -q' or `ls -Q' would have made this apparent.

--
Eric Blake



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

Re: Static destructors not running

[Christopher Faylor]

On Tue, May 10, 2005 at 11:54:45AM -0400, William M. (Mike) Miller wrote:
>On 5/10/05, Christopher Faylor <[EMAIL PROTECTED]> wrote:
>> On Tue, May 10, 2005 at 09:06:36AM -0400, William M. (Mike) Miller wrote:
>> >I'm still left with the problem of figuring out what changed to cause
>> >this result.  Until I ran the "setup" application last Friday, I was
>> >seeing output from static destructors, and now I don't.  It would
>> >save me a lot of work to be able to restore the old behavior, but I
>> >don't know what was responsible for this change.
>> 
>> Just as a wild guess, does explicitly calling exit help at all?
>
>Yes, the output does appear when I call exit instead of returning
>from main().  Unfortunately, that's not an option.  For one thing,
>this is shared code that works just fine on other systems (and
>under Cygwin until I updated last Friday).  For another, the
>semantics of calling exit in main() are not exactly the same as
>returning from main() -- local automatic objects in main() are not
>destroyed by the exit() call, which is something some of this
>code that is now failing relies on.

I was trying to figure out the problem, not suggest that you should
change all of your code.

Previous to 1.5.16, static destructors were always called via a
gcc "atexit" mechanism.  This meant that there were scenarios where
destructors would not be called at all so I made cygwin's exit call
the destructors explicitly.   I just forgot to make cygwin do the right
thing when returning from main rather than exiting.  This will be
fixed in the next snapshot.

cgf

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

RE: Strange-Dangerous behaviour in Cygwin [ATTN base-file maintainer]

[Eric Blake]

> > Actually, it would be nicer if $TERM of cygwin could treat [backspace] as
> > ^? [0x255] (ASCII delete) 
> 
> 
>   ITYM 0x7f

[/me blushes] yep - thanks for spotting my typo

--
Eric Blake



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

[ANNOUNCEMENT] Updated: tetex-3.0.0-3

[Jan Nieuwenhuizen]

I have updated the tetex suite to version 3.0.0-3.  This is a bugfix
release.

It fixes 3rd party linking to the libkpathsea dll, two configuration
problems, and a packaging bug.

Enjoy,
Jan.


To update your installation, click on the "Install Cygwin now" link on
the http://cygwin.com/ web page.  This downloads setup.exe to your
system.  Then, run setup and answer all of the questions.


*** CYGWIN-ANNOUNCE UNSUBSCRIBE INFO ***

If you want to unsubscribe from the cygwin-announce mailing list, look
at the "List-Unsubscribe: " tag in the email header of this message.
Send email to the address specified there.  It will be in the format:


[EMAIL PROTECTED]

If you need more information on unsubscribing, start reading here:

http://sources.redhat.com/lists.html#unsubscribe-simple

Please read *all* of the information on unsubscribing that is available
starting at the above URL.


-- 
Jan Nieuwenhuizen <[EMAIL PROTECTED]> | GNU LilyPond - The music typesetter
http://www.xs4all.nl/~jantien   | http://www.lilypond.org


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

[ANNOUNCEMENT] Updated: guile-1.6.7-1

[Jan Nieuwenhuizen]

I have updated Guile to the new upstream version 1.6.7.  This is a
bugfix release, which fixes several problems with the garbage
collector.

Also available, in the test distribution, is a 1.7.2 CVS snapshot.
Guile CVS has, amongst other things, gmp rationals and a new garbage
collector, which is most helpful for development, esp. debugging.

Enjoy,
Jan.


To update your installation, click on the "Install Cygwin now" link on
the http://cygwin.com/ web page.  This downloads setup.exe to your
system.  Then, run setup and answer all of the questions.


*** CYGWIN-ANNOUNCE UNSUBSCRIBE INFO ***

If you want to unsubscribe from the cygwin-announce mailing list, look
at the "List-Unsubscribe: " tag in the email header of this message.
Send email to the address specified there.  It will be in the format:


[EMAIL PROTECTED]

If you need more information on unsubscribing, start reading here:

http://sources.redhat.com/lists.html#unsubscribe-simple

Please read *all* of the information on unsubscribing that is available
starting at the above URL.

-- 
Jan Nieuwenhuizen <[EMAIL PROTECTED]> | GNU LilyPond - The music typesetter
http://www.xs4all.nl/~jantien   | http://www.lilypond.org


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

Re: Static destructors not running

[William M. (Mike) Miller]

On 5/10/05, Christopher Faylor <[EMAIL PROTECTED]> wrote:
> On Tue, May 10, 2005 at 09:06:36AM -0400, William M. (Mike) Miller wrote:
> >I'm still left with the problem of figuring out what changed to cause
> >this result.  Until I ran the "setup" application last Friday, I was
> >seeing output from static destructors, and now I don't.  It would
> >save me a lot of work to be able to restore the old behavior, but I
> >don't know what was responsible for this change.
> 
> Just as a wild guess, does explicitly calling exit help at all?

Yes, the output does appear when I call exit instead of returning
from main().  Unfortunately, that's not an option.  For one thing,
this is shared code that works just fine on other systems (and
under Cygwin until I updated last Friday).  For another, the
semantics of calling exit in main() are not exactly the same as
returning from main() -- local automatic objects in main() are not
destroyed by the exit() call, which is something some of this
code that is now failing relies on.

Thanks for the suggestion, though.

-- 
William M. (Mike) Miller | Edison Design Group
[EMAIL PROTECTED]

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

Re: "ls" finds file1 but "ls file1" does not

[Charles D. Russell]

Eric Blake wrote:
What version of coreutils are you using?  Attach the output of `cygcheck 
-svr' as described in cygwin.com/problems.html, then consider upgrading. 
__
I am attaching cygcheck in case you can find something obvious. 
However,I am reluctant to upgrade because the use of large static 
fortran arrays with cygwin/g77 seems to be a fragile issue and my 
current installation is now working (but only with -mno-cygwin).

On further reflection, this is not a problem I can safely ignore, since 
I use cygwin scripts for my backup routines.  I tried rebooting and 
chkdsk to no avail, then tried to reproduce the problem, and found that 
I can reproduce it with the following script. (Which in fact I used 
before, but forgot about.)  It is a newly written script, thus a likely 
suspect for the newly encountered problem.

Sorry about appending cygcheck.out as well as attaching it.  Must have 
hit a wrong button.

#! /usr/bin/sh
# rename_lc.sh
# rename - change filenames to lower case (to restore after MS unzip)
# for all files in default directory
echo rename to lower case
echo for all files in default directory
echo operating on directory $PWD
#trial run for approval
for f in ` ls `
do
 echo "$f" " ` echo $f | tr A-Z a-z ` "
done
#approve
echo type y to proceed
read PROCEED
echo $PROCEED
if test $PROCEED != y
then
   exit 0
fi
#execute
for f in ` ls `
do
 echo renaming $f
 mv -v "$f" " ` echo $f | tr A-Z a-z ` "
done
--
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/

RE: Strange-Dangerous behaviour in Cygwin [ATTN base-file maintainer]

[Dave Korn]

Original Message
>From: Eric Blake
>Sent: 10 May 2005 16:47

> Actually, it would be nicer if $TERM of cygwin could treat [backspace] as
> ^? [0x255] (ASCII delete) 


  ITYM 0x7f


cheers,
  DaveK
-- 
Can't think of a witty .sigline today


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

stdout closed before static destructors run

[William M. (Mike) Miller]

I thought I should repost this under a more accurate title, since
Dave Korm pointed out that I had misdiagnosed the problem in
my original posting.

I updated my installation last Friday.  As a result, printf calls
in destructors for static objects in C++ code no longer produce
any output.  Dave kindly did some debugging and determined
that the problem is that stdout has been closed by the time the
static destructor calls printf.  Reid Thompson also pointed out
that calling exit() explicitly causes the output to be successful,
even though returning from main() should be exactly the same
as calling exit() (except that calling exit() doesn't run the
destructors for automatic objects in main()).

I don't know what it was in the update on Friday that resulted
in this changed behavior; before Friday, output from destructors
was appearing just fine.  If anyone has an idea of what version
of which library I need to revert to, or if there is a setting
somewhere that would delay closing stdout until after static
destructors have run, I would be very grateful for the information.

Per approved posting guidelines, I've attached the output of
cygcheck so people can tell what's in my current installation.
Thanks for any help.

-- wmm

Cygwin Configuration Diagnostics
Current System Time: Mon May 09 18:33:24 2005

Windows XP Professional Ver 5.1 Build 2600 Service Pack 2

Path:   .\
C:\cygwin\usr\local\bin
C:\cygwin\bin
C:\cygwin\bin
C:\cygwin\usr\X11R6\bin
c:\WINDOWS\system32
c:\WINDOWS
c:\WINDOWS\System32\Wbem
c:\progra~1\window~1\accessories
c:\xerces\xerces-c-src_2_5_0\lib
c:\xalan\xml-xalan\c\bin
c:\xalan\xml-xalan\c\lib
c:\progra~1\mia4c6~1\bin

Output from C:\cygwin\bin\id.exe (nontsec)
UID: 500(Administrator) GID: 513(None)
0(root) 513(None)   544(Administrators)
545(Users)

Output from C:\cygwin\bin\id.exe (ntsec)
UID: 500(Administrator) GID: 513(None)
0(root) 513(None)   544(Administrators)
545(Users)

SysDir: C:\WINDOWS\system32
WinDir: C:\WINDOWS

HOME = `C:\cygwin\home\Administrator'
PWD = `/c/tmp'
USER = `Administrator'

ALLUSERSPROFILE = `C:\Documents and Settings\All Users'
APPDATA = `C:\Documents and Settings\Administrator\Application Data'
ARCH = `WinXP'
BASE_PATH = `. /usr/local/bin /usr/bin /bin /usr/X11R6/bin
/c/WINDOWS/system32 /c/WINDOWS /c/WINDOWS/System32/Wbem
/c/progra~1/window~1/accessories /c/xerces/xerces-c-src_2_5_0/lib
/c/xalan/xml-xalan/c/bin /c/xalan/xml-xalan/c/lib'
COMMONPROGRAMFILES = `C:\Program Files\Common Files'
COMPUTERNAME = `xxx'
COMSPEC = `C:\WINDOWS\system32\cmd.exe'
DISPLAY = `127.0.0.1:0.0'
EDITOR = `emacs'
ENSCRIPT = `-j -b "$n|%W|[$% of $=]" -M Letter --mark-wrapped-lines=arrow'
FP_NO_HOST_CHECK = `NO'
GROUP = `None'
HOMEDRIVE = `C:'
HOMEPATH = `\Documents and Settings\Administrator'
HOST = `xxx'
HOSTTYPE = `i386'
INCLUDE = `c:/progra~1/mia4c6~1/include;e:/msvc71/vc7/platformsdk/include'
LESS = `-a -C -y0 -i -M -Q'
LIB = `c:/progra~1/mia4c6~1/lib;e:/msvc71/vc7/platformsdk/lib'
LOGNAME = `Administrator'
LOGONSERVER = `\\xxx'
MACHTYPE = `i386'
MANPATH = `:/usr/ssl/man'
NUMBER_OF_PROCESSORS = `1'
OS = `Windows_NT'
OSTYPE = `posix'
PAGER = `less'
PATHEXT = `.COM;.EXE;.BAT;.CMD;.VBS;.VBE;.JS;.JSE;.WSF;.WSH'
PRINTER = `Dell Laser MFP 1600n'
PROCESSOR_ARCHITECTURE = `x86'
PROCESSOR_IDENTIFIER = `x86 Family 6 Model 9 Stepping 5, GenuineIntel'
PROCESSOR_LEVEL = `6'
PROCESSOR_REVISION = `0905'
PROGRAMFILES = `C:\Program Files'
SESSIONNAME = `Console'
SHLVL = `1'
SYSTEMDRIVE = `C:'
SYSTEMROOT = `C:\WINDOWS'
TEMP = `C:\DOCUME~1\ADMINI~1\LOCALS~1\Temp'
TERM = `cygwin'
TMP = `C:\DOCUME~1\ADMINI~1\LOCALS~1\Temp'
TZ = `EST5EDT4,M4.1.0/2,M10.5.0/2'
USERDOMAIN = `xxx'
USERNAME = `Administrator'
USERPROFILE = `C:\Documents and Settings\Administrator'
VCTOOLKITINSTALLDIR = `C:\Program Files\Microsoft Visual C++ Toolkit 2003\'
VENDOR = `intel'
WINDIR = `C:\WINDOWS'
POSIXLY_CORRECT = `1'

HKEY_CURRENT_USER\Software\Cygnus Solutions
HKEY_CURRENT_USER\Software\Cygnus Solutions\Cygwin
HKEY_CURRENT_USER\Software\Cygnus Solutions\Cygwin\mounts v2
HKEY_CURRENT_USER\Software\Cygnus Solutions\Cygwin\Program Options
HKEY_LOCAL_MACHINE\SOFTWARE\Cygnus Solutions
HKEY_LOCAL_MACHINE\SOFTWARE\Cygnus Solutions\Cygwin
HKEY_LOCAL_MACHINE\SOFTWARE\Cygnus Solutions\Cygwin\mounts v2
  (default) = `/'
  cygdrive flags = 0x002a
HKEY_LOCAL_MACHINE\SOFTWARE\Cygnus Solutions\Cygwin\mounts v2\/
  (default) = `C:\cygwin'
  flags = 0x000a
HKEY_LOCAL_MACHINE\SOFTWARE\Cygnus Solutions\Cygwin\mounts v2\/usr/bin
  (default) = `C:\cygwin/bin'
  flags = 0x000a
HKEY_LOCAL_MACHINE\SOFTWARE\Cygnus Solutions\Cygwin\mounts v2\/usr/lib
  (default) = `C:\cygwin/lib'
  flags = 0x000a
HKEY_LOCAL_MACHINE\SOFTWARE\Cygnus Solutions\Cygwin\mounts
v2\/usr/X11R6/lib/X11/fonts
  (default) = `C:\cygwin\usr\X11R6\lib\X11\fonts'
  flags = 0x000a
HKEY_LOCAL_MACH

Re: Strange-Dangerous behaviour in Cygwin [ATTN base-file maintainer]

[Eric Blake]

> > Now my question - why can't cygwin have sane defaults for the tty, so that
> > this question doesn't continue to pop up?
> 
> What's a sane setting?  When I open a standard bash console window, this
> simply doesn't happen.  Is $TERM set to "cygwin"?  That's the default
> setting and, as noted, backspace works as expected here.  I tried it with
> `rm -i' but the file didn't get removed when entering "y\bn".  So what?
> 

I think I may have a culprit.  When I run bash in a cmd window:
$ [ctrl-v][backspace]
^H
$ echo $TERM
cygwin

When I run it in an rxvt or xterm window:
$ [ctrl-v][backspace]
^?
$ echo $TERM
xterm

/etc/profile (actually etc/defaults/etc/profile) needs to be updated like so, 
to match the current default behavior of the cygwin terminal settings:

--- /etc/defaults/etc/profile.orig  2005-03-25 08:50:00.003125000 -0700
+++ /etc/defaults/etc/profile1  2005-05-10 09:40:05.474375000 -0600
@@ -1,4 +1,4 @@
-# base-files version 3.2-1
+# base-files version 3.2-1 -*- sh -*-
 
 # WARNING
 #
@@ -101,7 +101,12 @@
 $ '
 
if tty --quiet ; then
-   stty erase '^?'
+   case "$TERM" in
+   cygwin ) stty erase ^H ;;
+   xterm* | rxvt* ) stty erase '^?' ;;
+   * ) # unknown terminal type, don't set erase
+   ;;
+   esac
fi
;;
 ksh* | -ksh* | */ksh* | \


Actually, it would be nicer if $TERM of cygwin could treat [backspace] as ^? 
[0x255] (ASCII delete) like xterm does, since both cygwin and xterm treat 
[delete] as ^[[3~ [ESC - [ - 3 - ~] rather than ^?.  That way, even a cygwin 
terminal could see the difference between [ctrl-h] and [backspace], which is a 
MUST for `emacs -nw'.  But I don't know where to look in the cygwin1.dll source 
code to make that sort of change.


--
Eric Blake



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

Re: SIGSEGV address with SA_SIGINFO

[Christopher Faylor]

On Tue, May 10, 2005 at 02:03:50PM +0200, Marcus Crestani wrote:
>I found in the archives that some "limited implementation of sigaction" was 
>done in 2004. What is the state of the SA_SIGINFO functionality in current 
>cygwin? 

"currently unimplemented"  That's why it was a "limited implementation".

cgf

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

Re: problems in Perl process management

[Christopher Faylor]

On Tue, May 10, 2005 at 01:12:05PM +0200, Jurgen Defurne wrote:
>I also would like to know if it is possible.
>
>However, it could be that it has nothing to do with Cygwin. I have
>a Perl script which forks several children and monitors their output.
>
>If a child fails, then it has no use to run all forked processes further
>and I kill them with the perl 'kill' command. However, I also notice that
>deeper forked processes (grandchildren) refuse to die. This
>script is only run using ActiveState Perl.

ActiveState perl is a windows program.  You can't send cygwin (aka unix)
signals to a windows proram.

>I think it is really a serious Windows problem, because using
>the task manager it also seems not really possible to kill a complete
>process hierarchy.

XP has an option for killing the process hierarchy.  Just right click on
the process.

cgf

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

Re: Static destructors not running

[Christopher Faylor]

On Tue, May 10, 2005 at 09:06:36AM -0400, William M. (Mike) Miller wrote:
>On 5/9/05, Dave Korn <[EMAIL PROTECTED]> wrote:
>> Original Message
>> >From: William M. (Mike) Miller
>> > The output "In dtor." is missing.
>> 
>>  That's because stdout is already closed by the time your dtor runs.  I
>> stepped right into it, it does the printf call but somewhere down in the dll
>> it checks the flags field in the stdout FILE object for read/write and finds
>> it's not open for either, so it's at eof.  Grep 'cantwrite' if you really
>> want to find it.
>> 
>>  Anyway, your dtor is called.
>
>You're absolutely right -- the destructor is being called.  I should
>have checked that myself, rather than assuming that the absence
>of its output meant that it was not being executed.  Thanks for
>investigating.
>
>I'm still left with the problem of figuring out what changed to cause
>this result.  Until I ran the "setup" application last Friday, I was
>seeing output from static destructors, and now I don't.  It would
>save me a lot of work to be able to restore the old behavior, but I
>don't know what was responsible for this change.

Just as a wild guess, does explicitly calling exit help at all?

cgf

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

Re: Bug in the /dev/ttySx handling code?

[Christopher Faylor]

On Tue, May 10, 2005 at 01:16:56PM +0200, Martin Koegler wrote:
>On Mon, May 09, 2005 at 10:35:26PM +0200, Martin Koegler wrote:
>>At least, I understand, why stty -F /dev/ttyS0 under cygwin return 0
>>baud: tcgetattr returns 0 baud, if DTR is not set, which is different
>>to the behaviour of Linux.
>>
>>I would like to track the problem down, but as the use of stty (and cat
>>for doing IO) does not work, I have no idea, how to do it.
>
>After some testing, I found the problem: Cygwin stores the baud rate in
>c_ospeed of the termios struct, whereas Linux stores them in c_cflag.
>Therefore all code storing the baud rate in c_cflag is not working on
>cygwin.  Posix suggest using cfsetispeed() and cfsetospeed() to set the
>baud rate in the termios structure, as the location for the baud rate
>is not specified.

Hmm, linux does have c_ispeed and c_ospeed elements in the termios
structure.

cgf

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

RE: "ls" finds file1 but "ls file1" does not

[Dave Korn]

Original Message
>From: Ross b
>Sent: 10 May 2005 16:17

> 
> I'm wondering if something else happened in the renaming
> script.  Is it possible there is a space (or some other
> non-printable character) as the first character of the file
> names?  The output on a couple of messages leads me to
> believe so.  When I do an "ls -l", there is only one space
> between the date and the file name, in Charles's output,
> there are two.  I'd be interested to see the output of:
> 
> ls \ *


"ls -q" is the way to detect non-printing chars in filenames.  But I'm not
convinced it's very likely.


cheers,
  DaveK
-- 
Can't think of a witty .sigline today


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

Re: Strange-Dangerous behaviour in Cygwin

[Christopher Faylor]

On Tue, May 10, 2005 at 06:56:10AM -0600, Eric Blake wrote:
>Now my question - why can't cygwin have sane defaults for the tty, so that
>this question doesn't continue to pop up?

Because we hate everyone and want them to suffer?

cgf

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

Re: JNI and cygwin.

[Christopher Faylor]

On Mon, May 09, 2005 at 12:31:22PM -0700, Venkatesh Gopal wrote:
>I assume that the cygwin/JNI combination has still not been fixed in
>the latest version.  I need to make use of the cygwin libraries to get
>TERMinal support.  Any workarounds?  Any other libraries supporting
>curses and TERMinal operations for Windows would also be useful.

Please check out http://cygwin.com/problems.html and pay particular
attention to http://cygwin.com/problems.html#the-problem .

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

RE: Experiencing problems with OpenGL

[André Bleau]

Julian Moorsm wrote:
Hi everybody,
?
Hi Julian,
Welcome to the Cygwin list.
First and foremost I have to say that I am so happy with the concept of
Cygwin and to the Cygwin volunteers ?Keep up with the good work. It is
so much appreciated?. I am having a little problem with compiling an
OpenGL sourcefile.
?
Here's what I've done so far:
?
Installed Cygwin using setup.exe to c:\cygwin using default settings
onto Windows XP SP 2 OS.
Installed make, g++ and nano by running setup.exe again.
Read the readme file located under /usr/share/opengl1-1-0.
Little confused about what switches I should use when compiling .cpp
file and whether to use a makefile or not.
Ran the OpenGL examples to test if it?s possible to run the .exe files
compiled and linked under Cygwin. All examples ran successfully.
Tried to compile the following .cpp file whilst using -lglu32 -lopengl32
switches with g++:
So, you have done some homework; that's good. Now, it would have been easier 
to help you if you had written in your help request the _exact command line_ 
you had typed to invoke g++, along with the _exact error messages_ you 
received.

...
An example program
...
This .cpp source file compiles perfectly under Visual Studio 6.0, but as
I don?t have it anymore I?m unable to compile it now. Is there anyway I
can compile this source under Cygwin or will I have to rewrite it and
make use of the GLUI and GLUX libraries. If so could you explain this
process for me with compile/linker command line switches. Thanks for
your help.
Julian
I just copied your example code to a file I named julian.cpp and compiled 
and linked it with:

g++ -o julian julian.cpp -lglu32 -lopengl32 -lgdi32
I got 3 warnings but no error. julian.exe is runable. While it is true that 
most people developing Windows native OpenGL applications with Cygwin use a 
toolkit such as GLUT or GLUI, it is certainly possible to do without; just 
add -lgdi32 at the end of your command line to resolve calls to the M$ 
Graphics Device Interface library. If you use other functions from M$ libs, 
you will have to add the approriate -l arguments. See /usr/lib/w32api to see 
what's available.

Regards,
André Bleau,
Cygwin's OpenGL package maintainer.
_
Des mécanismes de contrôle parental puissants permettent à votre enfant de 
découvrir tout ce qu’Internet a à offrir. 
http://join.msn.com/?pgmarket=fr-ca&page=features/parental Commencez dès 
maintenant à profiter de tous les avantages de MSN Premium et obtenez les 
deux premiers mois GRATUITS*.

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

Re: Fixing strace and cygcheck so that they work with mount -X

[Christopher Faylor]

On Mon, May 09, 2005 at 09:19:14PM +0200, Michael Schaap wrote:
>On 9-May-2005 19:22, David Rothenberger wrote:
>
>> On 5/8/2005 7:26 PM, Christopher Faylor wrote:
>>
>>> On Sun, May 08, 2005 at 08:21:26PM -0400, Christopher Faylor wrote:
>>>
 Ultimately, I just have to make strace and cygcheck understand the
 cygwin arguments and environment variables. Then we won't need this.
>>>
>>>
>>> I would appreciate it if people would check out the latest snapshot to
>>> verify if I actually got this working in all scenarios (directories
>>> mounted with -X, -x, not mounted at all, or mounted without -X and -x).
>>
>>
>> Does cygstart also need to be fixed? I've found that it doesn't
>> propagate the full Cygwin environment when /bin is mounted in cygexec
>> mode.
>>
>> % cygstart -- /bin/rxvt -e bash -c "'env; read x'"
>>
>> prints out a small set of environment variables when /bin is mounted
>> in cygexec. When /bin is mounted normally, it gets the full environment.
>>
>Well, cygstart is a proper Cygwin executable. However, it does use a
>Windows API call (ShellExecute, see "cygstart --reference") to execute
>whatever needs to be started, so I can see how it might depend on a
>properly synchronized Windows environment.
>
>If anyone can tell me how to do this, I'll be happy to make the change
>to cygstart.

This shows what I did to cygcheck:

http://sources.redhat.com/cgi-bin/cvsweb.cgi/winsup/utils/cygcheck.cc.diff?cvsroot=uberbaum&r1=1.65&r2=1.66

It's possible that the environment code may just work.  Otherwise,
you'll have to grab the environment from cygwin and build a new
environment block, I assume.

cgf

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

Re: Strange-Dangerous behaviour in Cygwin

[Corinna Vinschen]

On May 10 06:56, Eric Blake wrote:
> According to Angelo Graziosi on 5/9/2005 1:50 PM:
> > 
> > WHY an "xterm setup" if, as I wrote, the problems are present in standard
> > bash shell, i.e. that launched with cygwin.bat.
> 
> Chris apologized for misreading your email and misleading this
> conversation: http://sources.redhat.com/ml/cygwin/2005-05/msg00393.html
> 
> > 
> > I have reinstalled Cygwin, installing only the BASE category: NO "xterm",
> > NO XORG, NO RXVT. ONLY BASE PACKAGES.
> > 
> > The problems are PRESENT in any case!!!
> 
> What are your stty settings?  What gets sent to the terminal when you type
> backspace?  I have the following:
> 
> $ [ctrl-v][backspace]^H[ctrl-c]
> $ stty erase ^H
> $ stty
> speed 38400 baud; line = 0;
> erase = ^H;
> - -imaxbel
> - -echoe -echok -echoctl -echoke
> 
> To test that setting your stty erase character to the same as the
> backspace character, try:
> $ stty erase ^H
> $ cat > foo # When all stty settings are correct,
> y[backspace]n
> [ctrl-d]
> $ cat -A foo# then backspace consumes y before output appears
> n$
> $ stty erase ^? # When the erase setting is wrong for the terminal,
> $ cat > foo
> y[backspace]n
> [ctrl-d]
> $ cat -A foo
> y^Hn$   # the backspace appears on the output
> 
> Now my question - why can't cygwin have sane defaults for the tty, so that
> this question doesn't continue to pop up?

What's a sane setting?  When I open a standard bash console window, this
simply doesn't happen.  Is $TERM set to "cygwin"?  That's the default
setting and, as noted, backspace works as expected here.  I tried it with
`rm -i' but the file didn't get removed when entering "y\bn".  So what?


Corinna

-- 
Corinna Vinschen  Please, send mails regarding Cygwin to
Cygwin Project Co-Leader  mailto:cygwin@cygwin.com
Red Hat, Inc.

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

RE: "ls" finds file1 but "ls file1" does not

[Ross Boulet]

> >> [etc]  Did your ash script go wrong and rename all
> those files with
> actual
> >> asterisks on the end ?
> 
> > The * in the listing just indicates that the file is
> executable (an ls
> > option that I use by default).
> 
> 
>   Hey, just wondered.  It happened to me once
> 
> 

I'm wondering if something else happened in the renaming
script.  Is it possible there is a space (or some other
non-printable character) as the first character of the file
names?  The output on a couple of messages leads me to
believe so.  When I do an "ls -l", there is only one space
between the date and the file name, in Charles's output,
there are two.  I'd be interested to see the output of:

ls \ *

Ross



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

GDB win-32 port developmer needed

[Clax Clinton]

Is there anyone with knowledge about the win32
debug interface, perhaps some gdb-on-cygwin maintainer
that is interested in doing some work on a similiar 
(but comercial) project?
Then please answer to [EMAIL PROTECTED]

regads,
Clax


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

Re: Help with error in vi and man

[Christopher Faylor]

On Mon, May 09, 2005 at 10:20:55AM -0600, Trevor Osatchuk wrote:
>On 5/7/05, Christopher Faylor <[EMAIL PROTECTED]> wrote:
>> On Sat, May 07, 2005 at 06:27:59PM -0600, Trevor Osatchuk wrote:
>> >On 5/7/05, Christopher Faylor <[EMAIL PROTECTED]> wrote:
>> >> On Fri, May 06, 2005 at 10:59:22PM -0600, Trevor Osatchuk wrote:
>> >> >When starting up vi/vim I get the following error:
>> >> >
>> >> >E558: Terminal entry not found in terminfo
>> >> >'cygwin' not known. Available builtin terminals are:
>> >> >builtin_ansi
>> >> >builtin_xterm
>> >> >builtin_iris-ansi
>> >> >builtin_dumb
>> >> >defaulting to ansi
>> >> >
>> >> >Help does not work for vim I get the error:
>> >> >
>> >> >E433: No tags file
>> >> >E149: Sorry, no help for help.txt
>> >> >
>> >> >Also when I type in the man command, man ls for example, all I get is
>> >> >(END) and no man page.  Like it paged to the end.  I don't currently
>> >> >have a pager environment variable.  My manpath is correct.
>> >> >
>> >> >Any ideas?
>> >>
>> >> Run the cygwin version of vim, i.e., /usr/bin/vim?  You're obviously
>> >> running some other version.  "which vim" would probably show which
>> >> version you're running.
>> >>
>> >Obviously is a strong word!  Which vim yeilds /usr/bin/vim.  I have
>> >seen these symtoms in other posts, though no solutions.
>> 
>> Ok.  Perhaps your terminfo installation is screwed up or nonexistent.
>> 
>> If you're scouring old posts then maybe you've come across the concept
>> of following the instructions at http://cygwin.com/problems.html , as
>> has already been sugested.  These instructions would help you send
>> problems in such a way that we wouldn't have to guess about things like
>> what version of vim you're running or whether you even have terminfo
>> installed.
>> 
>I apologize for not sending the expected information and format.  LART 
>accepted.
>
>I am running CYGWIN_NT-5.1, I got that from uname.
>
>I think that terminfo may in fact be the correct diagnosis.  I found a
>symlink of terminfo in /lib where terminfo was pointing to
>../share/terminfo.  There is no /share directory.  If you look in my
>cygcheck.out you will find that terminfo 5.4_20041009-1 is listed as
>installed.  So, is my installation of terminfo broken?  What do  I
>need to do to fix it?

Install terminfo.

cgf

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

Error during upgrade/X11 install

[David Balažic]

Hi!

I had a base cygwin installation* on WinXP-pro-SP2.
Then I downloaded the latest setup.exe,
selected xorg-x11-base and clicked NEXT...

During install I got an error dialog :

sh.exe - Unable To Locate Component

This application has failed to start because cygwin1.dll was not
found. Re-installing the application may fix this problem.


Everything appeared to work fine both before and after this update,
so I am posting this more as something for developers to work on,
if they think this is a bug.

Regards,
David

* - a fresh install from a few weeks ago



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

Packaging errors with tetex-3.00-3

[Dr. Volker Zell]

Hi

tetex-base:
tetex-doc:
tetex-extra:
tetex-tiny:

 /usr/doc/ instead of /usr/share/doc

tetex-bin:

 bogus  /usr/lib/libkpathsea.la~
 /usr/share/man/mf.1 instead of /usr/share/man/man1/mf.1


Ciao
  Volker


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

RE: system shared memory version mismatch detected woes

[Dave Korn]

Original Message
>From: Rob Light
>Sent: 10 May 2005 14:45

> I've recently updated my cygwin install (1.5.16-1) and
> now I'm getting this error message a lot:
> 
> C:\Cygwin\bin\ssh.exe (3672): *** system shared memory
> version mismatch detected
>  - 0x75BE0074/0x75BE0080.
> This problem is probably due to using incompatible
> versions of the cygwin DLL.
> Search for cygwin1.dll using the Windows
> Start->Find/Search facility
> and delete all but the most recent version.  The most
> recent version *should*
> reside in x:\cygwin\bin, where 'x' is the drive on
> which you have
> installed the cygwin distribution.  Rebooting is also
> suggested if you
> are unable to find another cygwin DLL.
> 
> The only way to "fix" this is to reboot :(
> 
> I've tried the 2005-May-03 nightly DLL the other day
> with no joy.  I've searched the archives and haven't
> found anything recently about this problem.
> 
> I'd like to revert back to the DLL prior to updating
> but I don't know what version that was and I don't
> know how to download specific DLL versions other than
> nightly snapshots.
> 
> Any suggestions?  Many thanks in advance.


  This problem is probably due to using incompatible versions of the cygwin
DLL.  Search for cygwin1.dll using the Windows Start->Find/Search facility
and delete all but the most recent version.  The most recent version
*should* reside in x:\cygwin\bin, where 'x' is the drive on which you have
installed the cygwin distribution.  Rebooting is also suggested if you are
unable to find another cygwin DLL.

  Well, you didn't mention anything about your having done so, so I assume
you didn't.

cheers,
  DaveK
-- 
Can't think of a witty .sigline today


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

system shared memory version mismatch detected woes

[Rob Light]

I've recently updated my cygwin install (1.5.16-1) and
now I'm getting this error message a lot:

C:\Cygwin\bin\ssh.exe (3672): *** system shared memory
version mismatch detected
 - 0x75BE0074/0x75BE0080.
This problem is probably due to using incompatible
versions of the cygwin DLL.
Search for cygwin1.dll using the Windows
Start->Find/Search facility
and delete all but the most recent version.  The most
recent version *should*
reside in x:\cygwin\bin, where 'x' is the drive on
which you have
installed the cygwin distribution.  Rebooting is also
suggested if you
are unable to find another cygwin DLL.

The only way to "fix" this is to reboot :(

I've tried the 2005-May-03 nightly DLL the other day
with no joy.  I've searched the archives and haven't
found anything recently about this problem.  

I'd like to revert back to the DLL prior to updating
but I don't know what version that was and I don't
know how to download specific DLL versions other than
nightly snapshots.

Any suggestions?  Many thanks in advance.




__ 
Do you Yahoo!? 
Yahoo! Mail - Find what you need with new enhanced search. 
http://info.mail.yahoo.com/mail_250

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

Re: Static destructors not running

[William M. (Mike) Miller]

On 5/9/05, Dave Korn <[EMAIL PROTECTED]> wrote:
> Original Message
> >From: William M. (Mike) Miller
> > The output "In dtor." is missing.
> 
>  That's because stdout is already closed by the time your dtor runs.  I
> stepped right into it, it does the printf call but somewhere down in the dll
> it checks the flags field in the stdout FILE object for read/write and finds
> it's not open for either, so it's at eof.  Grep 'cantwrite' if you really
> want to find it.
> 
>  Anyway, your dtor is called.

You're absolutely right -- the destructor is being called.  I should
have checked that myself, rather than assuming that the absence
of its output meant that it was not being executed.  Thanks for
investigating.

I'm still left with the problem of figuring out what changed to cause
this result.  Until I ran the "setup" application last Friday, I was
seeing output from static destructors, and now I don't.  It would
save me a lot of work to be able to restore the old behavior, but I
don't know what was responsible for this change.

-- 
William M. (Mike) Miller | Edison Design Group
[EMAIL PROTECTED]

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

RE: Building GCC-4.0-20050430

[Williams, Gerald S \(Jerry\)]

Anh Vo wrote:
> I successfully built it for three languages Ada, C, C++ with 
> configured as --enable-languages=ada,c,c++ 
> --enable-threads=gnat. A number of Ada Conformance Assessment 
> Test Suite (ACATS) failed. Further testing reveals that the 
> Ada runtime tasking support was not included in the build. 

OT for this list, but you may be interested to know that the
MINGW version supports Ada tasking.

I haven't delved into it, but the GNAT manual indicates that
Ada tasking support is pretty simple if you have a minimal
amount of POSIX support. Of course, you discovered that it
doesn't quite work OOTB. Since I was just toying around when
I ran into this, I found it easier to just install MINGW.
Personally, I don't see the point in supporting Ada if you
don't support tasking, but maybe that's just me. :-)

Of course, PTC.

-Jerry

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

Re: Strange-Dangerous behaviour in Cygwin

[Eric Blake]

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1

According to Angelo Graziosi on 5/9/2005 1:50 PM:
> 
> WHY an "xterm setup" if, as I wrote, the problems are present in standard
> bash shell, i.e. that launched with cygwin.bat.

Chris apologized for misreading your email and misleading this
conversation: http://sources.redhat.com/ml/cygwin/2005-05/msg00393.html

> 
> I have reinstalled Cygwin, installing only the BASE category: NO "xterm",
> NO XORG, NO RXVT. ONLY BASE PACKAGES.
> 
> The problems are PRESENT in any case!!!

What are your stty settings?  What gets sent to the terminal when you type
backspace?  I have the following:

$ [ctrl-v][backspace]^H[ctrl-c]
$ stty erase ^H
$ stty
speed 38400 baud; line = 0;
erase = ^H;
- -imaxbel
- -echoe -echok -echoctl -echoke

To test that setting your stty erase character to the same as the
backspace character, try:
$ stty erase ^H
$ cat > foo # When all stty settings are correct,
y[backspace]n
[ctrl-d]
$ cat -A foo# then backspace consumes y before output appears
n$
$ stty erase ^? # When the erase setting is wrong for the terminal,
$ cat > foo
y[backspace]n
[ctrl-d]
$ cat -A foo
y^Hn$   # the backspace appears on the output

Now my question - why can't cygwin have sane defaults for the tty, so that
this question doesn't continue to pop up?

- --
Life is short - so eat dessert first!

Eric Blake [EMAIL PROTECTED]
-BEGIN PGP SIGNATURE-
Version: GnuPG v1.4.0 (Cygwin)
Comment: Public key at home.comcast.net/~ericblake/eblake.gpg
Comment: Using GnuPG with Thunderbird - http://enigmail.mozdev.org

iD8DBQFCgK9p84KuGfSFAYARAtcdAJ9p1rYwYEpyGQXPuRN/FSt7sCAysQCg0WIb
hR75DFDONfGsqHr6GAYxS4k=
=Wjqq
-END PGP SIGNATURE-

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

RE: Help !!! - Problem running Cygwin in Remote Desktop session with non-admin privileges

[Moghe, Jayant]

I want to download Cygwin 1.5.16.

Please let me know which mirror site hosts this version.

Thanks.

Best regards,
Jayant Moghe
===
Texas Instruments (I) Pvt. Ltd.
Bagmane Tech Park, CV Raman Nagar, Byrasandra
Bangalore - India 560 093
Office Phone: - +91- 80 - 25048295
[EMAIL PROTECTED]


"Fools you are... to say you learn by your experience  I prefer to
profit by other's mistakes and avoid the price of my own."
-Otto von Bismarck, 19th Century Prussian Chancellor.



-Original Message-
From: Moghe, Jayant 
Sent: Tuesday, May 10, 2005 12:12 PM
To: 'cygwin@cygwin.com'
Subject: RE: Help !!! - Problem running Cygwin in Remote Desktop session
with non-admin privileges


I downloaded fresh Cygwin (which is supposed to be 1.5.16), when I
install it, the version it shows is 1.5.14 (0.126/4/2) 2005-04-01.

Can some one guide me downloading the latest Cygwin 1.5.16 version?

My problem has not been resolved, still.

Thanks a bunch for your help.

Best regards,
Jayant Moghe


"Fools you are... to say you learn by your experience  I prefer to
profit by other's mistakes and avoid the price of my own."
-Otto von Bismarck, 19th Century Prussian Chancellor.



-Original Message-
From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf
Of Corinna Vinschen
Sent: Monday, May 09, 2005 6:09 PM
To: cygwin@cygwin.com
Subject: Re: Help !!! - Problem running Cygwin in Remote Desktop session
with non-admin privileges

On May  9 17:15, Moghe, Jayant wrote:
> How to confirm whether Cygwin 1.5.16 has been installed?
> 
> Is it uname -a command?

Did you consider to *try* it?


Corinna

-- 
Corinna Vinschen  Please, send mails regarding Cygwin to
Cygwin Project Co-Leader  mailto:cygwin@cygwin.com
Red Hat, Inc.

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



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

SIGSEGV address with SA_SIGINFO

[Marcus Crestani]

Hi,
I am trying obtain the address caused by a SIGSEGV inside a signal handler, 
but it seems that the siginfo_t struct isn't set correctly. The value I get 
from si->si_addr differs from the address where the segfault actually 
occurred.

void fault_handler (int sn, siginfo_t * si, void *ctx)
{
  fprintf (stderr, "fault_handler: %x\n", si->si_addr);
}

void install_fault_handler (void)
{
  struct sigaction act, segv_oact;
  memset(&act, sizeof(sigaction), 0);
  act.sa_sigaction = fault_handler;
  sigemptyset(&act.sa_mask);
  act.sa_flags = SA_SIGINFO;
  sigaction(SIGSEGV, &act, &segv_oact);
}

int main (void)
{
  char *p = 0;
  install_fault_handler ();
  p[0] = 23;
  return 0;
}

The SEGFAULT in the above code snippet occurs in 0x0, the information 
retrieved from si->si_addr actually shows 0x7c80b651.

I found in the archives that some "limited implementation of sigaction" was 
done in 2004. What is the state of the SA_SIGINFO functionality in current 
cygwin? 
Is there a way to obtain the correct fault address?

Please CC me privately, I am not subscribed to this list.
Thanks for your help,
-- 
Marcus

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

Re: problems in Perl process management

[Steven Hartland]

that's by design if u want to kill an entire tree u can do so with process
explorer a free download from www.sysinternals.com.
   Steve
- Original Message - 
From: "Jurgen Defurne"


I also would like to know if it is possible.
However, it could be that it has nothing to do with Cygwin. I have
a Perl script which forks several children and monitors their output.
If a child fails, then it has no use to run all forked processes further
and I kill them with the perl 'kill' command. However, I also notice that
deeper forked processes (grandchildren) refuse to die. This
script is only run using ActiveState Perl.
I think it is really a serious Windows problem, because using
the task manager it also seems not really possible to kill a complete
process hierarchy.


This e.mail is private and confidential between Multiplay (UK) Ltd. and the person or entity to whom it is addressed. In the event of misdirection, the recipient is prohibited from using, copying, printing or otherwise disseminating it or any information contained in it. 

In the event of misdirection, illegible or incomplete transmission please 
telephone (023) 8024 3137
or return the E.mail to [EMAIL PROTECTED]
--
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/

Re: Bug in the /dev/ttySx handling code?

[Martin Koegler]

On Mon, May 09, 2005 at 10:35:26PM +0200, Martin Koegler wrote:
> At least, I understand, why stty -F /dev/ttyS0 under cygwin return 0 baud:
> tcgetattr returns 0 baud, if DTR is not set, which is different to the 
> behaviour of Linux.
> 
> I would like to track the problem down, but as the use of stty (and cat for 
> doing IO) does not
> work, I have no idea, how to do it.

After some testing, I found the problem:
Cygwin stores the baud rate in c_ospeed of the termios struct, whereas Linux 
stores them in c_cflag.
Therefore all code storing the baud rate in c_cflag is not working on cygwin. 
Posix suggest using cfsetispeed()
and cfsetospeed() to set the baud rate in the termios structure, as the 
location for the baud rate is not specified.

mfg Martin Kögler

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

Re: problems in Perl process management

[Jurgen Defurne]

I also would like to know if it is possible.

However, it could be that it has nothing to do with Cygwin. I have
a Perl script which forks several children and monitors their output.

If a child fails, then it has no use to run all forked processes further
and I kill them with the perl 'kill' command. However, I also notice that
deeper forked processes (grandchildren) refuse to die. This
script is only run using ActiveState Perl.

I think it is really a serious Windows problem, because using
the task manager it also seems not really possible to kill a complete
process hierarchy.

Regards,

Jurgen Defurne









Sonam Chauhan <[EMAIL PROTECTED]>
Sent by: 
[EMAIL PROTECTED]
2005-05-10 10:41 AM
 
To: "'cygwin@cygwin.com'" 
cc: (bcc: Jurgen Defurne/BRG/CE/PHILIPS)
Subject:problems in Perl process management
Classification: 




Hello - 

I'd appreciate help with problems doing process management in Cygwin/Perl. 


I have a Perl application that creates child processes - I need it to kill
processes that exceed a certain timeout. I am trying to use the
Proc::ProcessTable and Proc::Killfam CPAN modules for this.

I ran into two problems: 

The first problem was a "can't stat /dev" error message produced when
calling Proc::Killfam. This problem was fixed by a script I found that
populated entries under /dev. 

To understand the next probem, have a look at the simple test script
attached. The script forks a child process, which runs `sleep` in a third
process. The parent process then tries to kill both children on expiry of 
a
timeout. The script behaves perfectly on Linux -- it works as expected and
kills the fork-ed child Perl process, as well it's `sleep` child process.
However, on Cygwin/Perl it only kills the fork-ed Perl child - it cannot
kill the `sleep`-ing child. 

The problem seems to be that the process table data returned by
Proc::ProcessTable seems to differ from the data returned 'ps'.
Specifically, Proc::ProcessTable returns the WINPID of a process as the 
PID
for the backticked `sleep` process. 

The closest issue I found in the list archives is this one: 
http://sourceware.org/ml/cygwin/2005-02/msg00224.html 
It does not seem to have been resolved. 

I'm running Perl on Cygwin on Windows XP SP2. Running 'cygcheck -c' gives
the following package status for cygwin and Perl:
--
cygwin  1.5.16-1   OK
perl5.8.6-4OK
--

Can anyone help?

Regards,
Sonam Chauhan
-- 
Electronic Commerce, Corporate Express Australia Ltd.
Phone: +61-2-9335-0725, Email: [EMAIL PROTECTED]
 


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


timeout_test2.pl
Description: Binary data
--
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/

[ANNOUNCEMENT] Updated: lilypond-2.4.6-1

[Bertalan Fodor]

A new version of lilypond will be available on the mirrors soon.
This is the latest stable release of LilyPond, the GNU Music Typesetter.
Enjoy.
Bert
--
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/

Re: postgresql and sockets

[Corinna Vinschen]

On May  9 20:45, Krzysztof Duleba wrote:
> I turned off all non-system apps except for cygserver and postgresql and
> still the same.
> 
> How can I provide more debug info? Is it possible to check which processes
> access or modify the socket file?

No more debugging necessary.  I found the cause of the problem.  At one
point the file attributes were not correctly stored for socket files and
when postgres touches the socket file (which it does every 5 minutes),
the correct file attributes got lost.  Especially the system bit got lost,
which is important to recognize the file as a socket.

I've applied a patch to CVS which will show up in the next developers
snapshot on http://cygwin.com/snapshots/


Thanks for reporting and debugging,
Corinna

-- 
Corinna Vinschen  Please, send mails regarding Cygwin to
Cygwin Project Co-Leader  mailto:cygwin@cygwin.com
Red Hat, Inc.

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

RE: "ls" finds file1 but "ls file1" does not

[Dave Korn]

Original Message
>From: Charles D. Russell
>Sent: 10 May 2005 04:58

>> [etc]  Did your ash script go wrong and rename all those files with
actual
>> asterisks on the end ?

> The * in the listing just indicates that the file is executable (an ls
> option that I use by default).  


  Hey, just wondered.  It happened to me once


cheers,
  DaveK
-- 
Can't think of a witty .sigline today


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

problems in Perl process management

[Sonam Chauhan]

Hello - 

I'd appreciate help with problems doing process management in Cygwin/Perl. 

I have a Perl application that creates child processes - I need it to kill
processes that exceed a certain timeout. I am trying to use the
Proc::ProcessTable and Proc::Killfam CPAN modules for this.

I ran into two problems: 

The first problem was a "can't stat /dev" error message produced when
calling Proc::Killfam. This problem was fixed by a script I found that
populated entries under /dev. 

To understand the next probem, have a look at the simple test script
attached. The script forks a child process, which runs `sleep` in a third
process. The parent process then tries to kill both children on expiry of a
timeout. The script behaves perfectly on Linux -- it works as expected and
kills the fork-ed child Perl process, as well it's `sleep` child process.
However, on Cygwin/Perl it only kills the fork-ed Perl child - it cannot
kill the `sleep`-ing child. 

The problem seems to be that the process table data returned by
Proc::ProcessTable seems to differ from the data returned 'ps'.
Specifically, Proc::ProcessTable returns the WINPID of a process as the PID
for the backticked `sleep` process. 

The closest issue I found in the list archives is this one: 
http://sourceware.org/ml/cygwin/2005-02/msg00224.html 
It does not seem to have been resolved. 

I'm running Perl on Cygwin on Windows XP SP2. Running 'cygcheck -c' gives
the following package status for cygwin and Perl:
--
cygwin  1.5.16-1   OK
perl5.8.6-4OK
--

Can anyone help?

Regards,
Sonam Chauhan
-- 
Electronic Commerce, Corporate Express Australia Ltd.
Phone: +61-2-9335-0725, Email: [EMAIL PROTECTED]
 




timeout_test2.pl
Description: Binary data
--
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/