Re: How to configure cron's mail?

2006-09-26 Thread René Berber
Joost Kraaijeveld wrote:

> Can I configure where cron sends the mail to? It seems to be
> "[EMAIL PROTECTED]", where user is the account cron is running under, but I
> would like it to go to "[EMAIL PROTECTED]".

Yes, in /etc/ssmtp/ssmtp.conf, but when you install the ssmtp package you are 
supposed to run ssmtp-config.  Anyway you can edit the file, just define root 
and rewriteDomain so that cron uses those.
-- 
René Berber


--
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: Install hangs

2006-09-26 Thread Artie Ziff
Is there an example of log file (posted somewhere) that illustrates
what a successful cygwin installation looks like?

AZ



--
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 configure cron's mail?

2006-09-26 Thread Joost Kraaijeveld
Hi,

Can I configure where cron sends the mail to? It seems to be
"[EMAIL PROTECTED]", where user is the account cron is running under, but I
would like it to go to "[EMAIL PROTECTED]".


-- 
Groeten,

Joost Kraaijeveld
Askesis B.V.
Molukkenstraat 14
6524NB Nijmegen
tel: 024-3888063 / 06-51855277
fax: 024-3608416
web: www.askesis.nl

--
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: Install hangs

2006-09-26 Thread Eric Mader

Eric Mader wrote:
I was able to get setup.exe unstuck by cd'ing to /etc/preremove, running 
automake-devel.sh and then deleting it. I had to do this with about 
three other scripts in this directory before setup.exe would move on to 
the next phase. It's now happily installing all the selected packages.


I'm not sure what was going on with the offending scripts...

Regards,
Eric


It seems I spoke too soon, now it setup.exe hangs on the 
/etc/postinstall/00ash.sh script. The installation seems incomplete. For 
example, the "ls" command doesn't work.


So it seems that whatever was going on with the preinstall scripts is 
also happening w/ th postinstall scripts, but now I don't have a 
functioning environment in which to run them by hand :-(


Regards,
Eric


--
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: Install hangs

2006-09-26 Thread Eric Mader

Eric Mader wrote:

Dave Korn wrote:

On 26 September 2006 18:25, Eric Mader wrote:


Dave Korn wrote:



One other thing: I was updating a previous Cygwin installation. From a
quick spot-check it seems that the installer didn't update anything: for
example gcc still says it's version 3.3.3-1 even though the installer
reports that the most recent version is 3.4.4-1. I also noticed that
setup.log is dated 6/21/2004 and has no entries in it newer than that 
date.


All of this leads me to suspect that the installer didn't update 
anything...



  You could just be right there.  From your cygcheck:

c:  hd  NTFS 53348Mb  99% CP CS UN PA FC IBM_PRELOAD

  Looks like your C drive is full!


cheers,
  DaveK


I had about 750MB free on c:. I just did a bunch of archiving and 
deleting and now there is 6.29GB free. The install still hangs at 
exactly the same place. As far as I can tell, it tries to run the 
preremove script *before* it does any installing - the only other thing 
it seems to do is check the MD5s on the packages...


Regards,
Eric


I was able to get setup.exe unstuck by cd'ing to /etc/preremove, running 
automake-devel.sh and then deleting it. I had to do this with about 
three other scripts in this directory before setup.exe would move on to 
the next phase. It's now happily installing all the selected packages.


I'm not sure what was going on with the offending scripts...

Regards,
Eric


--
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: cywin/x issues

2006-09-26 Thread Christopher Faylor
On Tue, Sep 26, 2006 at 02:35:58PM -0700, captainmidnight wrote:
>4) XMing better?
>
>It looks like cygwin/x has been defunct for a long while now.  In contrast,
>this website
>   http://www.straightrunning.com/XmingNotes/
>claims that the XMing program is actively developed and a lot better.
>
>Anyone have any experience with it versus cygwin/x?

If they do, this is not the mailing list to discuss it.  Either use the xming
or cygwin-xfree mailing lists, please.

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



cywin/x issues

2006-09-26 Thread captainmidnight

I have a client who has some gui applications running on a linux box.  I am
running MS Windows locally, so someone recommended that I try using cygwin.

I installed the following packages this morning: 1) the entire base package
2) the entire x11 package 3) the inetutils and openssh packages (since I
want to use ssh to connect to the remote machine).  Basically, I followed
the instructions here:
http://x.cygwin.com/docs/ug/setup-cygwin-x-installing.html

To ssh into the remote machine, I simply tried the included dos script
/usr/X11R6/bin/startxwin.bat

And once the xwin shell came up, I executed
ssh -X -Y -l  
and entered my password and got into the remote machine.  So far so good.

I then tried playing around withsome x apps: xclock and xlogo worked fine
(how could they go wrong?).

But then I tried executing a medium complex program, gnome-system-monitor,
and I ran into the following issues:


1) speed

The first time that I played with the gui, it was unbelievably slow, to the
point of being unusable.  For instance, clicking on the File menu took 2-3
seconds to display the menu choices (which was simply Quit in this case).

Later on in the afternoon when I played with the exact same app again, it
executed more more quickly.

Anyone have any idea why?  I am guessing that likely my network connection
(a Time Warner cable modem in NYC) was just getting a surge of traffic, or
maybe had signal strength issues or something.  Perhaps also the remote
machine was having a surge of activity at the time (I forgot to check using
top when it was problematic, my mistake).  Or maybe the first time the
program ran, it was downloading remote fonts or something that were cached
locally for subsequent executions.

I am aware that some personal firewalls are known to cause slow performance;
see, for example, some of the posts here:
http://blog.gmane.org/gmane.os.cygwin.xfree/day=20040824
I tried looking at my windows networking state with netstat but did not see
the loopback issues reported above, so I do not think that my firewall (AVG)
is the culprit.


2) warning messages

Executing gnome-system-monitor caused a ton of errors like
** (gnome-system-monitor:30353): WARNING **: Unable load icon Failed to
open file '/usr/share/pixmaps/ssh-askpass-gnome.png': No such file or
directory
to appear.

I also saw 3 errors like
 (gnome-system-monitor:30353): Gtk-WARNING **: Attempting to sort on invalid
type GdkPixbuf
once gnome-system-monitor is up and running.

A web search reveals that a few other people have these errors too, e.g.:
http://lists.linuxcoding.com/rhl/2005/msg39096.html

Is the reason for the above because the remote machine is using an old
version of linux?

Typing uname -a on the remote machine gave
... 2.6.11-1.1369_FC4smp #1 SMP Thu Jun 2 23:08:39 EDT 2005 i686 i686 
i386
GNU/Linux

Would FC5 cure these errors?


3) fonts

The gnome-system-monitor app simply looks horrible.  The best description
that I can give is that it looks like when you take a screen shot and then
save it as a jpeg file instead of as a png file: the text looks weird and
sorta smeared.

Did I simply fail to configure things properly?  And is there a ready cure
for the bad looking fonts?


4) XMing better?

It looks like cygwin/x has been defunct for a long while now.  In contrast,
this website
http://www.straightrunning.com/XmingNotes/
claims that the XMing program is actively developed and a lot better.

Anyone have any experience with it versus cygwin/x?
-- 
View this message in context: 
http://www.nabble.com/cywin-x-issues-tf2341359.html#a6516394
Sent from the Cygwin Users mailing list archive at Nabble.com.


--
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: Bash problem - v3.1.17(8) - syntax error

2006-09-26 Thread mwoehlke

Arun Biyani wrote:
I just upgraded to the current bash. Now I am getting an error. I 
reinstalled, rebooted

the machine. Still get the same error. The variable $HOME is set correctly.

 > bash: /c/home/abiyani/.bash_login: line 7: syntax error: unexpected 
end of file

 >
 > [EMAIL PROTECTED] ~
 > $ bash --version
 > GNU bash, version 3.1.17(8)-release (i686-pc-cygwin)
 > Copyright (C) 2005 Free Software Foundation, Inc.
 >
 > [EMAIL PROTECTED] ~
 > $ cat ~/.bashrc
 > #
 > if [ -f $HOME/wrk/sys/com/bash_more ]
 > then
 > . $HOME/wrk/sys/com/bash_more
 > fi
 > #
 >
 >
 > [EMAIL PROTECTED] ~


Just for the record, the release announcement did mention:
"A script on a binary mount that uses \r\n line endings will probably 
encounter syntax errors or odd variable assignments, because the \r is 
treated literally.  If this happens to you, use d2u to fix the line 
endings, or change your script to live in a text mount point.  A script 
that resides on a text mount can have either line ending (even 
inconsistently mixed), but be aware that text mount points are slower, 
due to \r\n filtering."


--
Matthew
Download. Untar. Configure. Make. Install. Lather. Rinse. Repeat.


--
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: [Fwd: Re: Bash problem - v3.1.17(8) - syntax error]

2006-09-26 Thread Arun Biyani

Igor Peshansky wrote:


Is there any particular reason you post the output of od on .bashrc when
the error was reported in .bash_login?

BTW, for the future, you might want to run "od -c" instead -- its output
is a bit more readable.
Igor
  

Igor & Dave,

Thx. It is a CR/LF problem. I had run d2u on .bashrc but not on 
.bash_login. After I ran

dos2unix on both, the problem has gone away.

Arun



--
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: [Fwd: Re: Bash problem - v3.1.17(8) - syntax error]

2006-09-26 Thread Igor Peshansky
On Tue, 26 Sep 2006, Arun Biyani wrote:

>  Original Message 
> Subject:  Re: Bash problem - v3.1.17(8) - syntax error
> Date: Tue, 26 Sep 2006 12:17:34 -0700
> From: Arun Biyani <[EMAIL PROTECTED]>
> To:   Dave Korn <[EMAIL PROTECTED]>
> References:   <[EMAIL PROTECTED]>

.  Thanks.

> Dave Korn wrote:
> > On 26 September 2006 20:11, Arun Biyani wrote:
> >
> >
> > > I just upgraded to the current bash. Now I am getting an error. I
> > > reinstalled, rebooted the machine. Still get the same error. The
> > > variable $HOME is set correctly.
> >
> >   Wrong line-ends most likely.  Run d2u on it.
> >
> > cheers,
> >   DaveK
>
> Still the same problem.
>
> > bash: /c/home/abiyani/.bash_login: line 7: syntax error: unexpected
> > end of file
> >
> > [EMAIL PROTECTED] ~
> > $ od < .bashrc
> > 000 005043 063151 055440 026440 020146 044044 046517 027505
> > 020 071167 027553 074563 027563 067543 027555 060542 064163
> > 040 066537 071157 020145 005135 064164 067145 020012 020040
> > 060 027040 022040 047510 042515 073457 065562 071457 071571
> > 100 061457 066557 061057 071541 057550 067555 062562 063012
> > 120 005151 005043 12
> > 125
> >
> > [EMAIL PROTECTED] ~
> > $

Is there any particular reason you post the output of od on .bashrc when
the error was reported in .bash_login?

BTW, for the future, you might want to run "od -c" instead -- its output
is a bit more readable.
Igor
-- 
http://cs.nyu.edu/~pechtcha/
  |\  _,,,---,,_[EMAIL PROTECTED] | [EMAIL PROTECTED]
ZZZzz /,`.-'`'-.  ;-;;,_Igor Peshansky, Ph.D. (name changed!)
 |,4-  ) )-,_. ,\ (  `'-'   old name: Igor Pechtchanski
'---''(_/--'  `-'\_) fL a.k.a JaguaR-R-R-r-r-r-.-.-.  Meow!

"Las! je suis sot... -Mais non, tu ne l'es pas, puisque tu t'en rends compte."
"But no -- you are no fool; you call yourself a fool, there's proof enough in
that!" -- Rostand, "Cyrano de Bergerac"

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



Double Sided printing

2006-09-26 Thread Job Evers

In unix I can usually print double sided doing:

lpr -o sides=two-sided-long-edge

When I try this using the cygwin lpr...obviously this doesn't work.
Any suggestions on how to print double sided?

Thanks,

Job

--
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: Install hangs

2006-09-26 Thread Eric Mader

Dave Korn wrote:

On 26 September 2006 18:25, Eric Mader wrote:


Dave Korn wrote:



One other thing: I was updating a previous Cygwin installation. From a
quick spot-check it seems that the installer didn't update anything: for
example gcc still says it's version 3.3.3-1 even though the installer
reports that the most recent version is 3.4.4-1. I also noticed that
setup.log is dated 6/21/2004 and has no entries in it newer than that date.

All of this leads me to suspect that the installer didn't update anything...



  You could just be right there.  From your cygcheck:

c:  hd  NTFS 53348Mb  99% CP CS UN PA FC IBM_PRELOAD

  Looks like your C drive is full!


cheers,
  DaveK


I had about 750MB free on c:. I just did a bunch of archiving and 
deleting and now there is 6.29GB free. The install still hangs at 
exactly the same place. As far as I can tell, it tries to run the 
preremove script *before* it does any installing - the only other thing 
it seems to do is check the MD5s on the packages...


Regards,
Eric


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



[Fwd: Re: Bash problem - v3.1.17(8) - syntax error]

2006-09-26 Thread Arun Biyani



 Original Message 
Subject:Re: Bash problem - v3.1.17(8) - syntax error
Date:   Tue, 26 Sep 2006 12:17:34 -0700
From:   Arun Biyani <[EMAIL PROTECTED]>
To: Dave Korn <[EMAIL PROTECTED]>
References: <[EMAIL PROTECTED]>



Dave Korn wrote:

On 26 September 2006 20:11, Arun Biyani wrote:

  

I just upgraded to the current bash. Now I am getting an error. I
reinstalled, rebooted
the machine. Still get the same error. The variable $HOME is set correctly.



  Wrong line-ends most likely.  Run d2u on it.

cheers,
  DaveK

 
Still the same problem.


bash: /c/home/abiyani/.bash_login: line 7: syntax error: unexpected 
end of file


[EMAIL PROTECTED] ~
$ od < .bashrc
000 005043 063151 055440 026440 020146 044044 046517 027505
020 071167 027553 074563 027563 067543 027555 060542 064163
040 066537 071157 020145 005135 064164 067145 020012 020040
060 027040 022040 047510 042515 073457 065562 071457 071571
100 061457 066557 061057 071541 057550 067555 062562 063012
120 005151 005043 12
125

[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: Bash problem - v3.1.17(8) - syntax error

2006-09-26 Thread Dave Korn
On 26 September 2006 20:11, Arun Biyani wrote:

> I just upgraded to the current bash. Now I am getting an error. I
> reinstalled, rebooted
> the machine. Still get the same error. The variable $HOME is set correctly.

  Wrong line-ends most likely.  Run d2u on it.

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/



Bash problem - v3.1.17(8) - syntax error

2006-09-26 Thread Arun Biyani
I just upgraded to the current bash. Now I am getting an error. I 
reinstalled, rebooted

the machine. Still get the same error. The variable $HOME is set correctly.

> bash: /c/home/abiyani/.bash_login: line 7: syntax error: unexpected 
end of file

>
> [EMAIL PROTECTED] ~
> $ bash --version
> GNU bash, version 3.1.17(8)-release (i686-pc-cygwin)
> Copyright (C) 2005 Free Software Foundation, Inc.
>
> [EMAIL PROTECTED] ~
> $ cat ~/.bashrc
> #
> if [ -f $HOME/wrk/sys/com/bash_more ]
> then
> . $HOME/wrk/sys/com/bash_more
> fi
> #
>
>
> [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: DLL error messages suppressed under zsh/RXVT

2006-09-26 Thread Williams, Gerald S \(Jerry\)
Shankar Unni wrote:
> Before sending your cygcheck.out, try checking the archives.
> This problem was talked about a couple of months ago.

Thanks for the reference. The problem I reported (check the OP)
may be related but isn't exactly the same. AFAICT, suppression
of those DLL error messages should be universal. I got error
messages (due to DLL rebase issues) in one case, but not in the
other. Worse, the program simply hung rather than returning an
error code (which the makefile would have caught, at least).

My WAG is that the fact that RXVT isn't a Windows console was
the cause of the differing error message suppression that I
saw, but as Peter Castro pointed out, perhaps "all bets are
off" when there are rebase issues.

I am still confused about Peter's ability to get a dialog box.
Is this a version difference? Is there a new CYGWIN option? I'm
getting error code 53 (ENOANO ?!?) if a DLL is missing.

BTW, I didn't see any response to Dave Korn's August 30 comment
on the "missing DLL" issue. Did I miss it? Are we looking for a
P to TC?

Dave Korn wrote:
> Of course, but there's still an issue here why this case
> doesn't get a proper ENOENT status in $? and an error
> message on stderr.

gsw

--
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 Setup die?

2006-09-26 Thread Dave Korn
On 22 September 2006 01:59, Artie Ziff wrote:

> Hello,
> 
> Is common for installation process to die? 

  Not common, but it does happen sometimes.  More often what happens is that
one of the scripts takes an ever-so-long time to run and it /seems/ to have
crashed.

> On Win XP Pro ver. 2002
> SP2, I run setup.exe. Eventually it hangs... this time Cygwin Setup
> dialog showing Progress 19% of xorg-x11-bin-dlls-6.8.99.901-1.tar.bz2,
> where it appears to hang.

  19% of which stage?  Downloading?  Installing?

> Is there simple way to recover and pickup where left off? My
> experience from two previous attempts: must reselect everything I
> want. Does Set Up gui maintain current state of installation currently
> on disk? Is there a way to inform the GUI so I need not go through
> pain of reselecting items I want?

  Depends.  If you've managed to download the packages to your local package
directory, you can just re-run it, choose "install from local directory",
click "keep" in the package chooser, then click all the way through without
altering any settings and it should just finish off any missing bits from the
last time.

  However, that's the most I can tell you in general terms; we need more
information to try and figure out what's actually happening in your machine.


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: Install hangs

2006-09-26 Thread Dave Korn
On 26 September 2006 18:25, Eric Mader wrote:

> Dave Korn wrote:

> One other thing: I was updating a previous Cygwin installation. From a
> quick spot-check it seems that the installer didn't update anything: for
> example gcc still says it's version 3.3.3-1 even though the installer
> reports that the most recent version is 3.4.4-1. I also noticed that
> setup.log is dated 6/21/2004 and has no entries in it newer than that date.
> 
> All of this leads me to suspect that the installer didn't update anything...


  You could just be right there.  From your cygcheck:

c:  hd  NTFS 53348Mb  99% CP CS UN PA FC IBM_PRELOAD

  Looks like your C drive is full!


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: Install hangs

2006-09-26 Thread Eric Mader

Dave Korn wrote:

On 26 September 2006 10:20, Chris Taylor wrote:


  Ooh, yes, I guess I should have pointed that out.  


  Artie, Eric, as long as it's got as far as the postinstall stage, that means 
most of the installation is there; postinstall scripts are mostly written in 
bash shell script, and at the time they are run enough of cygwin should have 
been installed for them to work.  Ceratinly all the binary files should have 
been installed, and since cygcheck is a native win32 program and will run no 
matter how borked the cygwin installation is, you should have no problems 
invoking it from a DOS shell in the cygwin bin dir.


One other thing: I was updating a previous Cygwin installation. From a 
quick spot-check it seems that the installer didn't update anything: for 
example gcc still says it's version 3.3.3-1 even though the installer 
reports that the most recent version is 3.4.4-1. I also noticed that 
setup.log is dated 6/21/2004 and has no entries in it newer than that date.


All of this leads me to suspect that the installer didn't update anything...

Regards,
Eric


--
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: Install hangs

2006-09-26 Thread Eric Mader

Dave Korn wrote:

On 26 September 2006 10:20, Chris Taylor wrote:


Dave Korn wrote:

On 26 September 2006 05:22, Artie Ziff wrote:


I recently experienced a similar scenario, posted a general description
of the user experience (with some questions) in an attempt to elicit
general comments. I rcv'd the same response as those before me... as is
evidenced in the archives. That is, no response. I suppose the
philosophy is: if there is no response then no problem exists. ;-)

  Nope.  The philosophy is: if there is no information, then no diagnosis
can be made. 


Problem reports:   http://cygwin.com/problems.html

^

  Cygchecks, gentlemen, please.  As attachments, please.  Let's see what
you've got so far, and then later we might need to look at setup logs and
suchlike. 


cheers,
  DaveK


I wonder if perhaps they think they can't run cygcheck because they
haven't finished installing cygwin yet?

It does seem that many people are unaware that cygcheck is a native
win32 binary...



  Ooh, yes, I guess I should have pointed that out.  


  Artie, Eric, as long as it's got as far as the postinstall stage, that means 
most of the installation is there; postinstall scripts are mostly written in 
bash shell script, and at the time they are run enough of cygwin should have 
been installed for them to work.  Ceratinly all the binary files should have 
been installed, and since cygcheck is a native win32 program and will run no 
matter how borked the cygwin installation is, you should have no problems 
invoking it from a DOS shell in the cygwin bin dir.

cheers,
  DaveK


Yes, cygwin seems to work:

[EMAIL PROTECTED] /cygdrive/c
$ uname -a
CYGWIN_NT-5.1 StarBug2 1.5.13(0.122/4/2) 2005-03-01 11:01 i686 unknown 
unknown C

ygwin

[EMAIL PROTECTED] /cygdrive/c
$

I've enclosed the output from cygcheck -c and cygcheck -s

Regards,
Eric
Cygwin Package Information
Package Version Status
_update-info-dir00231-1 OK
apr 0.9.6-1 OK
apr-util0.9.6-1 OK
ash 20040127-1  OK
astyle  1.15.3-3OK
atk 1.8.0-1 OK
atk-devel   1.8.0-1 OK
atk-doc 1.8.0-1 OK
atk-runtime 1.8.0-1 OK
autoconf2.59-1  OK
autoconf-devel  2.59-1  OK
autoconf-stable 2.13-5  OK
automake1.7.9-1 OK
automake-devel  1.9.2-1 OK
automake-stable 1.4p6-2 OK
base-files  3.2-1   OK
base-passwd 2.2-1   OK
bash2.05b-16OK
bc  1.06-2  OK
binutils20041229-1  OK
bison   20030307-1  OK
byacc   1.9-1   OK
bzip2   1.0.2-6 OK
ccrypt  1.7-1   OK
cgoban  1.9.14-1OK
cmake   2.0.5-1 OK
coreutils   5.2.1-5 OK
crypt   1.1-1   OK
ctags   5.5-4   OK
cvs 1.11.17-1   OK
cvsutils0.2.1-1 OK
cygipc  2.03-2  OK
cygrunsrv   1.01-1  OK
cygutils1.2.6-1 OK
cygwin  1.5.13-1OK
cygwin-doc  1.4-2   OK
cygwin-x-doc1.0.4-1 OK
ddd 3.3.9-1 OK
diffutils   2.8.7-1 OK
doxygen 1.2.18-1OK
ed  0.2-1   OK
editrights  1.01-1  OK
emacs   21.2-13 OK
emacs-X11   21.2-13 OK
expat   1.95.8-1OK
file4.12-1  OK
findutils   20041227-1  OK
flex2.5.4a-3OK
fontconfig  2.2.2-1 OK
fortune 1.99.1-1OK
freetype2   2.1.5-1 OK
fvwm2.4.7-3 OK
gawk3.1.4-3 OK
gcc 3.3.3-3 OK
gcc-ada 3.3.3-3 OK
gcc-core3.3.3-3 OK
gcc-g++ 3.3.3-3 OK
gcc-gdc 3.3.3-3 OK
gcc-mingw   20040810-1  OK
gcc-mingw-core  20040810-1  OK
gcc-mingw-g++   20040810-1  OK
gdb 20041228-2  OK
gdbm1.8.3-7 OK
gettext 0.1

Problems with archiver "ar"

2006-09-26 Thread Frank Illenseer

Hi all,

with the current CYGWIN installation I suddenly get errors with the archiver 
"ar":


 ar: creating MYlib.a
  15 [main] ar 3024 _cygtls::handle_exceptions: Error while dumping 
state

  (probably corrupted stack)

or

 ar: MYlib.a: Memory exhausted


I am using CYGWIN on Windows XP Pro with latest service packs and hotfixes 
applied.
The partitions under CYGWIN are mounted in textmode due to the latest bash 
update.

The version of ar is: GNU ar 2.17.50 20060817

Can anyone help me?


Thanks in advance
Frank



--
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 with archiver "ar"

2006-09-26 Thread Christopher Faylor
On Tue, Sep 26, 2006 at 05:00:57PM +0200, Frank Illenseer wrote:
>with the current CYGWIN installation I suddenly get errors with the 
>archiver "ar":
>
> ar: creating MYlib.a
>  15 [main] ar 3024 _cygtls::handle_exceptions: Error while dumping 
>state
>  (probably corrupted stack)
>
>or
>
> ar: MYlib.a: Memory exhausted
>
>I am using CYGWIN on Windows XP Pro with latest service packs and
>hotfixes applied.  The partitions under CYGWIN are mounted in textmode
>due to the latest bash update.

>The version of ar is: GNU ar 2.17.50 20060817
>
>Can anyone help me?

What kind of help are you expecting if you don't provide any details about
what you're doing?

You should start here: http://cygwin.com/problems.html .

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: grep weirdness - matching space character

2006-09-26 Thread Christopher Faylor
On Tue, Sep 26, 2006 at 11:16:42AM +0100, The Blog User wrote:
>I am really struggling to understand what I am doing wrong here.
>
>I have a log file with a line that looks like this:
>
>++ 04:51:32 All 94 items succeeded
>
>The binary data for that line is this:
>
>2B 2B 20 30 34 3A 35 31 3A 33 32 20 41 6C 6C 20 39 34 20 69 74 65 6D 73 20
>73 75 63 63 65 65 64 65 64 0A
>
>using grep and tail (versions below) I am failing to match that line
>
>$ tail -1 /path/to/file/the.log | grep -a "All \d*.items succeeded"
>
>however if I insert 3 (why three?) dots (or a .*) between 'All' and '\d' I
>get a match, what is happening ?

grep doesn't recognize \d as matching a number so it is not going to do
what you think it does.  All...  will skip over the 94 above and match
zero occurrences of \d so that's why that works.

Use [0-9]* instead of \d.

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: grep weirdness - matching space character

2006-09-26 Thread Richard Quadling

On 26/09/06, Dave Korn <[EMAIL PROTECTED]> wrote:

On 26 September 2006 11:17, The Blog User wrote:

> I am really struggling to understand what I am doing wrong here.
>
> I have a log file with a line that looks like this:
>
> ++ 04:51:32 All 94 items succeeded
>
> The binary data for that line is this:
>
> 2B 2B 20 30 34 3A 35 31 3A 33 32 20 41 6C 6C 20 39 34 20 69 74 65 6D 73 20
> 73 75 63 63 65 65 64 65 64 0A
>
> using grep and tail (versions below) I am failing to match that line
>
> $ tail -1 /path/to/file/the.log | grep -a "All \d*.items succeeded"

  There's no such thing as \d.

> however if I insert 3 (why three?) dots (or a .*) between 'All' and '\d' I
> get a match, what is happening ?

  The dots are eating the '94' as well as the space.

> This seems wrong to me, since - from my knowledge of regex's - that is
> saying there must be three characters between the 'All' and the first
> digit, yet I can see there is only a single space character.

  Escaping a d just matches a literal 'd'.  So the expression '\d*' matches
zero or more of the letter d.  If you use the three dots to eat the two digits
as well as the space, the optional any-number-of-d's is matched by the zero
d's following, and then the trailing 'items succeeded' matches.

  Whereas with only the one dot, the dot matches the space, then there's
zero-optional-'d's, then the '9' fails to match against '.items succeeded'.


$ cat c:\log.log
++ 04:51:32 All 90 items succeeded
++ 04:51:32 All 91 items succeeded
++ 04:51:32 All 92 items succeeded
++ 04:51:32 All 93 items succeeded
++ 04:51:32 All 94 items succeeded

$ tail -1 c:\log.log
++ 04:51:32 All 94 items succeeded

$ tail -1 c:\log.log | grep -a "All [0-9]* items succeeded"
++ 04:51:32 All 94 items succeeded


Is that what you wanted?

--
-
Richard Quadling
Zend Certified Engineer : http://zend.com/zce.php?c=ZEND002498&r=213474731
"Standing on the shoulders of some very clever giants!"

--
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: grep weirdness - matching space character

2006-09-26 Thread Jack


No such escape as '\d' - I thought that was digit, is that a perl-ism ?

Anyway, I now understand what is going on, thanks for your help.





--
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: grep weirdness - matching space character

2006-09-26 Thread Kenneth Nellis
Because "\d" is a Perl-specific feature, you should specify "grep -P".
-Original Message-
From: The Blog User [mailto:blog at yankeeboysoftware dot com] 
Sent: Tuesday, September 26, 2006 6:17 AM
To: cygwin@cygwin.com
Subject: grep weirdness - matching space character

I am really struggling to understand what I am doing wrong here.

I have a log file with a line that looks like this:

++ 04:51:32 All 94 items succeeded

The binary data for that line is this:

2B 2B 20 30 34 3A 35 31 3A 33 32 20 41 6C 6C 20 39 34 20 69 74 65 6D 73 20
73 75 63 63 65 65 64 65 64 0A

using grep and tail (versions below) I am failing to match that line

$ tail -1 /path/to/file/the.log | grep -a "All \d*.items succeeded"

however if I insert 3 (why three?) dots (or a .*) between 'All' and '\d' I
get a match, what is happening ?

$ tail -1 /path/to/file/the.log | grep -a "All...\d*.items succeeded"


I tried '.*' before I looked at the binary values, and got a match, then I
reverted to '...'  by trial and error.
This seems wrong to me, since - from my knowledge of regex's - that is
saying there must be three characters between the 'All' and the first
digit, yet I can see there is only a single space character.

VERSION Information
$ uname -a
CYGWIN_NT-5.1 gbws-00027514 1.5.21(0.156/4/2) 2006-07-30 14:21 i686 Cygwin

$ bash --version
GNU bash, version 3.1.17(6)-release (i686-pc-cygwin)

$ grep --version
grep (GNU grep) 2.5.1

$ tail --version
tail (GNU coreutils) 5.97


--
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: New windows from cygwin in ssh

2006-09-26 Thread Igor Peshansky
Ugh, top-posting...  Reformatted.

On Tue, 26 Sep 2006, Pavel Ivanoff wrote:

> > -Original Message-
> > From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Pavel Ivanoff
> > Sent: Friday, September 22, 2006 4:57 PM
> > To: [EMAIL PROTECTED]

.  Thanks.

> > Subject: New windows from cygwin in ssh
> >
> > Hi, all!
> >
> > Tell me please were there any changes to cygwin that made such
> > behaviour: when launch from cygwin bash shell any windows program like
> > notepad, for example, it normally opens its window and I can work with
> > it. But when I enter to cygwin via ssh from Linux-machine or even from
> > local cygwin bash, launching notepad hangs and doesn't seem to open
> > any windows or to do any other work. I can terminate this hanging by
> > Ctrl+C, of cause, but problem is that I can't invoke any
> > windows-program from cygwin via ssh. In cygwin release of March 01,
> > 2005 this launching works as I expect it, but in release of January
> > 20, 2006 it doesn't. Were there some changes that did block this
> > functionality for some reason?
>
> Can anybody help me with this problem? There is some guess that this
> happens due to some Local Security Policy on Windows XP (I know that in
> last versions of cygwin sshd requires several settings in Local Security
> Policy to work correctly). But I can't understand what policy prohibits
> to make desktop windows over ssh...

You weren't clear on exactly what you want to happen.  If you wish to see
the window pop up on the remote machine's desktop, you need to add the
"Allow service to interact with desktop" checkmark in the sshd service
description (or, alternatively, install it with the '-i' cygrunsrv flag).

If you want the window to be forwarded over to the local machine (i.e.,
the one you're ssh'ing from), that is not currently possible with Windows.
One thing you can try is use a tool like VNC (which you can forward over
ssh, too).
HTH,
Igor
-- 
http://cs.nyu.edu/~pechtcha/
  |\  _,,,---,,_[EMAIL PROTECTED] | [EMAIL PROTECTED]
ZZZzz /,`.-'`'-.  ;-;;,_Igor Peshansky, Ph.D. (name changed!)
 |,4-  ) )-,_. ,\ (  `'-'   old name: Igor Pechtchanski
'---''(_/--'  `-'\_) fL a.k.a JaguaR-R-R-r-r-r-.-.-.  Meow!

"Las! je suis sot... -Mais non, tu ne l'es pas, puisque tu t'en rends compte."
"But no -- you are no fool; you call yourself a fool, there's proof enough in
that!" -- Rostand, "Cyrano de Bergerac"

--
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: New windows from cygwin in ssh

2006-09-26 Thread Pavel Ivanoff
Can anybody help me with this problem? There is some guess that this
happens due to some Local Security Policy on Windows XP (I know that in
last versions of cygwin sshd requires several settings in Local Security
Policy to work correctly). But I can't understand what policy prohibits
to make desktop windows over ssh...

Thanks in advance.
Pavel Ivanov


> -Original Message-
> From: [EMAIL PROTECTED] 
> [mailto:[EMAIL PROTECTED] On Behalf Of Pavel Ivanoff
> Sent: Friday, September 22, 2006 4:57 PM
> To: cygwin@cygwin.com
> Subject: New windows from cygwin in ssh
> 
> Hi, all!
> 
> Tell me please were there any changes to cygwin that made such
> behaviour: when launch from cygwin bash shell any windows program like
> notepad, for example, it normally opens its window and I can work with
> it. But when I enter to cygwin via ssh from Linux-machine or even from
> local cygwin bash, launching notepad hangs and doesn't seem 
> to open any
> windows or to do any other work. I can terminate this hanging 
> by Ctrl+C,
> of cause, but problem is that I can't invoke any windows-program from
> cygwin via ssh.
> In cygwin release of March 01, 2005 this launching works as I 
> expect it,
> but in release of January 20, 2006 it doesn't. Were there some changes
> that did block this functionality for some reason?
> 
> Best regards.
> Pavel Ivanov
> 
> --
> 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: New windows from cygwin in ssh

2006-09-26 Thread Pavel Ivanoff
I've always authenticated via keypair. But after your letter I've tried
to authenticate via password and received the same result. I looked to
Windows Task Manager and in both cases it showd that notepad is running
as me. sshd is also running as me... Have you some other idea?

Pavel Ivanov


> -Original Message-
> From: Chris Taylor [mailto:[EMAIL PROTECTED] 
> Sent: Tuesday, September 26, 2006 2:25 PM
> To: Pavel Ivanoff
> Cc: cygwin@cygwin.com
> Subject: Re: New windows from cygwin in ssh
> 
> Pavel Ivanoff wrote:
> > Can anybody help me with this problem? There is some guess that this
> > happens due to some Local Security Policy on Windows XP (I 
> know that in
> > last versions of cygwin sshd requires several settings in 
> Local Security
> > Policy to work correctly). But I can't understand what 
> policy prohibits
> > to make desktop windows over ssh...
> > 
> > Thanks in advance.
> > Pavel Ivanov
> > 
> > 
> 
> How are you authenticating with ssh? Password 
> (keyboard-interactive) or 
> keypair?
> 
> If you are authenticating via keypair, it isn't really 
> running as you, 
> iirc. The SYSTEM user doesn't normally create desktop 
> windows, so it's 
> possible that this process isn't allowed to as a result..
> 
> Chris
> 

--
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: grep weirdness - matching space character

2006-09-26 Thread Dave Korn
On 26 September 2006 11:17, The Blog User wrote:

> I am really struggling to understand what I am doing wrong here.
> 
> I have a log file with a line that looks like this:
> 
> ++ 04:51:32 All 94 items succeeded
> 
> The binary data for that line is this:
> 
> 2B 2B 20 30 34 3A 35 31 3A 33 32 20 41 6C 6C 20 39 34 20 69 74 65 6D 73 20
> 73 75 63 63 65 65 64 65 64 0A
> 
> using grep and tail (versions below) I am failing to match that line
> 
> $ tail -1 /path/to/file/the.log | grep -a "All \d*.items succeeded"

  There's no such thing as \d.
 
> however if I insert 3 (why three?) dots (or a .*) between 'All' and '\d' I
> get a match, what is happening ?

  The dots are eating the '94' as well as the space.

> This seems wrong to me, since - from my knowledge of regex's - that is
> saying there must be three characters between the 'All' and the first
> digit, yet I can see there is only a single space character.

  Escaping a d just matches a literal 'd'.  So the expression '\d*' matches
zero or more of the letter d.  If you use the three dots to eat the two digits
as well as the space, the optional any-number-of-d's is matched by the zero
d's following, and then the trailing 'items succeeded' matches.

  Whereas with only the one dot, the dot matches the space, then there's
zero-optional-'d's, then the '9' fails to match against '.items succeeded'.



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: New windows from cygwin in ssh

2006-09-26 Thread Chris Taylor

Pavel Ivanoff wrote:

Can anybody help me with this problem? There is some guess that this
happens due to some Local Security Policy on Windows XP (I know that in
last versions of cygwin sshd requires several settings in Local Security
Policy to work correctly). But I can't understand what policy prohibits
to make desktop windows over ssh...

Thanks in advance.
Pavel Ivanov




How are you authenticating with ssh? Password (keyboard-interactive) or 
keypair?


If you are authenticating via keypair, it isn't really running as you, 
iirc. The SYSTEM user doesn't normally create desktop windows, so it's 
possible that this process isn't allowed to as a result..


Chris

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



grep weirdness - matching space character

2006-09-26 Thread The Blog User
I am really struggling to understand what I am doing wrong here.

I have a log file with a line that looks like this:

++ 04:51:32 All 94 items succeeded

The binary data for that line is this:

2B 2B 20 30 34 3A 35 31 3A 33 32 20 41 6C 6C 20 39 34 20 69 74 65 6D 73 20
73 75 63 63 65 65 64 65 64 0A

using grep and tail (versions below) I am failing to match that line

$ tail -1 /path/to/file/the.log | grep -a "All \d*.items succeeded"

however if I insert 3 (why three?) dots (or a .*) between 'All' and '\d' I
get a match, what is happening ?

$ tail -1 /path/to/file/the.log | grep -a "All...\d*.items succeeded"


I tried '.*' before I looked at the binary values, and got a match, then I
reverted to '...'  by trial and error.
This seems wrong to me, since - from my knowledge of regex's - that is
saying there must be three characters between the 'All' and the first
digit, yet I can see there is only a single space character.

VERSION Information
$ uname -a
CYGWIN_NT-5.1 gbws-00027514 1.5.21(0.156/4/2) 2006-07-30 14:21 i686 Cygwin

$ bash --version
GNU bash, version 3.1.17(6)-release (i686-pc-cygwin)

$ grep --version
grep (GNU grep) 2.5.1

$ tail --version
tail (GNU coreutils) 5.97

--
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: Install hangs

2006-09-26 Thread Dave Korn
On 26 September 2006 10:20, Chris Taylor wrote:

> Dave Korn wrote:
>> On 26 September 2006 05:22, Artie Ziff wrote:
>> 
>>> I recently experienced a similar scenario, posted a general description
>>> of the user experience (with some questions) in an attempt to elicit
>>> general comments. I rcv'd the same response as those before me... as is
>>> evidenced in the archives. That is, no response. I suppose the
>>> philosophy is: if there is no response then no problem exists. ;-)
>> 
>>   Nope.  The philosophy is: if there is no information, then no diagnosis
>> can be made. 
>> 
 Problem reports:   http://cygwin.com/problems.html
>> ^
>> 
>>   Cygchecks, gentlemen, please.  As attachments, please.  Let's see what
>> you've got so far, and then later we might need to look at setup logs and
>> suchlike. 
>> 
>> cheers,
>>   DaveK
> 
> 
> I wonder if perhaps they think they can't run cygcheck because they
> haven't finished installing cygwin yet?
> 
> It does seem that many people are unaware that cygcheck is a native
> win32 binary...


  Ooh, yes, I guess I should have pointed that out.  

  Artie, Eric, as long as it's got as far as the postinstall stage, that means 
most of the installation is there; postinstall scripts are mostly written in 
bash shell script, and at the time they are run enough of cygwin should have 
been installed for them to work.  Ceratinly all the binary files should have 
been installed, and since cygcheck is a native win32 program and will run no 
matter how borked the cygwin installation is, you should have no problems 
invoking it from a DOS shell in the cygwin bin dir.

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: Install hangs

2006-09-26 Thread Chris Taylor

Dave Korn wrote:

On 26 September 2006 05:22, Artie Ziff wrote:


I recently experienced a similar scenario, posted a general description
of the user experience (with some questions) in an attempt to elicit
general comments. I rcv'd the same response as those before me... as is
evidenced in the archives. That is, no response. I suppose the
philosophy is: if there is no response then no problem exists. ;-)


  Nope.  The philosophy is: if there is no information, then no diagnosis can
be made.


Problem reports:   http://cygwin.com/problems.html

^

  Cygchecks, gentlemen, please.  As attachments, please.  Let's see what
you've got so far, and then later we might need to look at setup logs and
suchlike.

cheers,
  DaveK



I wonder if perhaps they think they can't run cygcheck because they 
haven't finished installing cygwin yet?


It does seem that many people are unaware that cygcheck is a native 
win32 binary...



Chris

--
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: Install hangs

2006-09-26 Thread Dave Korn
On 26 September 2006 05:22, Artie Ziff wrote:

> I recently experienced a similar scenario, posted a general description
> of the user experience (with some questions) in an attempt to elicit
> general comments. I rcv'd the same response as those before me... as is
> evidenced in the archives. That is, no response. I suppose the
> philosophy is: if there is no response then no problem exists. ;-)

  Nope.  The philosophy is: if there is no information, then no diagnosis can
be made.

>> Problem reports:   http://cygwin.com/problems.html
^

  Cygchecks, gentlemen, please.  As attachments, please.  Let's see what
you've got so far, and then later we might need to look at setup logs and
suchlike.

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/