RE: hyperthreading fix, try #1

[Volker Bandke]

 
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1

Christopher,

thanks for the explanation  (I read, and even understood it)  Good
job  (Explanation and partial fix).  

  
  
  
  

 With kind Regards|\  _,,,---,,_
ZZZzz /,`.-'`'-.  ;-;;, 
 Volker Bandke   |,4-  ) )-,_. ,\ (  `'-'   
  (BSP GmbH)'---''(_/--'  `-'\_)

  It is easier for a camel to pass through the eye of a needle if
it is lightly greased. -- Kehlog Albran, "The Profit"
  
(Another Wisdom from my fortune cookie jar) 

-BEGIN PGP SIGNATURE-
Version: PGP 8.0.1

iQA/AwUBQghuWh5trGyhAF0wEQJd0QCeK2FJNuk6z0zogcKLd5rJv75tmWMAn3ZT
XV7i3W4/0DjRAss0uJ2BqTf4
=xKB+
-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: bash: tab completion failure from (but not at) /

[fergus]

Recent remarks ("I have an idea about how to fix the race but it would
introduce a destabilizing change that I'd rather not chance before 1.5.13 is
released") suggest that an updated cygwin1.dll might be imminent.
Please could I mention a minor but annoying glitch described along with
Corinna's immediate and effective fix at
http://www.cygwin.com/ml/cygwin/2004-05/msg00449.html but which has
re-emerged in recent snapshots, at least since
http://www.cygwin.com/ml/cygwin/2004-12/msg00838.html, in which Corinna
records her perplexity ("weird") at this re-emergence.
Things worked properly in snapshot 20041222 but fail from 20041223.
Thanks.
Fergus


--
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: perl & Win32 lib support

[Yitzchak Scott-Thoennes]

On Mon, Feb 07, 2005 at 06:42:21PM -0800, linda w wrote:
> I thought there had been a fix in the works for this problem -- I
> wanted to write a program using cygwin perl to access/modify the Registry.
> 
> When I load the Win32 package from cpan and try building it, I get
> a familiar error message "IsWinNT" is undefined, so building and
> installing cpan registry access routines isn't possible. 
> 
> Is there something else that would break if "IsWinNT" is set to
> "true" if the underlying OS is NT based (or IsWin95 for Win9x/Me)?
> 
> I might be able to use ActiveState's Perl, but it doesn't play
> so well with CPAN and doesn't seem to handle Cygwin paths very well
> either.
> 
> Was there a work-around for this?

Upgrade to perl5.8.6, which addresses the IsWinNT-missing problem.
Also, I believe Reini will be releasing a new version of perl-libwin32
real soon 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/

Re: perl winpid?

[Yitzchak Scott-Thoennes]

On Mon, Feb 07, 2005 at 02:17:32PM +0100, Reini Urban wrote:
> Igor Pechtchanski schrieb:
> >On Sun, 6 Feb 2005, Reini Urban wrote:
> >>I feel quite stupid now, but found nothing simple.
> >>How to get the winpid from the current process in cygwin's perl?
> >>
> >>$$ is the cygwin pid which is different from the windows pid
> >>GetCurrentProcessId().
> >
> >winpid = cygwin_internal(CW_CYGWIN_PID_TO_WINPID, pid) ?
> 
> Sure, but in any perl API?
> 
> There's apparently a new libwin32@perl.org list,
> the [EMAIL PROTECTED] list is almost 
> unmaintained for some years now.

The two lists have somewhat different purposes; see the descriptions
at http://lists.perl.org.

> We will check out there where this cygwin specific functionality
> will go to.
> Win32::Process::CygwinToWin32ProcessID() is my suggestion.
> 
> .pm:
> =item Win32::Process::CygwinToWin32ProcessID($pid)
> 
> Returns the windows process ID for the given cygwin pid.
> On non-cygwin platforms it will return the $pid argument without 
> translation.
> 
> =item Win32::Process::Win32ToCygwinProcessID($pid)
> 
> Returns the cygwin process ID for the given windows pid.
> On non-cygwin platforms it will return the $pid argument without 
> translation.
> 
> .xs:
> DWORD
> CygwinToWin32ProcessID(pid)
> DWORD pid
> CODE:
> #ifdef __CYGWIN__
> RETVAL = cygwin_internal(CW_CYGWIN_PID_TO_WINPID, pid);
> #else
> RETVAL = pid;
> #endif
> OUTPUT:
> RETVAL
> 
> DWORD
> Win32ToCygwinProcessID(pid)
> DWORD pid
> CODE:
> #ifdef __CYGWIN__
> RETVAL = (DWORD)cygwin32_winpid_to_pid(pid);
> #else
> RETVAL = pid;
> #endif
> OUTPUT:
> RETVAL

I'd rather see them in the Proc:: namespace, and I think it would make
sense to put them in perl's cygwin.c itself, if Gerrit is willing to
release yet another perl-5.8.6.  If this sounds OK, I'll come up with
a patch.

--
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: RFE: enhance setup.exe to used cached mirrors file

[Erik de Castro Lopo]

On Mon, 7 Feb 2005 22:28:32 -0500 (EST)
Igor Pechtchanski <[EMAIL PROTECTED]> wrote:

> The best way to second such requests is with a patch.  Remember,
> . :-)

Where would I find the code to setup.exe?

I had a look in the main CVS tree but couldn't find it.

Erik
-- 
+---+
  Erik de Castro Lopo  [EMAIL PROTECTED] (Yes it's valid)
+---+
"Baldie is such a wonderful villain
The Linux/OSS community could not possibly ask for a better villain than
our man Baldie. He is absolutely perfect for the part. Just look at his
creds: 1) Physically repulsive; 2) Morally bankrupt; 3) Megalomaniacal;
4) Possessed of a truly nasty, abusive disposition; 5) Prone to Hitlerian
ranting; 6) Stalinesque paranoia... The list just goes on and on. The man
has the gift of true despicability, no doubt about it. If it weren't for
Baldie we'd be stuck with Bilgatus' merely vacuuous and creepy persona
for an anthropomorphization of the Evil Empire -- tepid at best."
  -- Matthew Alton in LinuxToday.com on Steve Balmer

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

RXVT copy/paste behavior

[Rizwan Kassim]

While I've googled constantly for it (and seen it alluded to on this
list, but never explicitly explained), I havent been able to find out
how to do the following:

Disable the behavior in rxvt that copies any selected region into the clipboard.
Enable the right mouse button to act as paste (rather than just the
middle mouse button)
Find some other way of selecting an rxvt range and copying it (maybe
the middle button)

Any one know how to do this?

Cheers,
Rizwan

--
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: hyperthreading fix, try #1

[Gary R. Van Sickle]

Um... I say Gold Star for this explanation alone, which somehow is
completely free from any hint of sarcasm, "WJM"ness, and passive aggression.

Bad day Chris? ;-)

Oh, and double-gold stars to any and all who coughed up the dough.

-- 
Gary R. Van Sickle
 

> -Original Message-
> From: [EMAIL PROTECTED] 
> [mailto:[EMAIL PROTECTED] On Behalf Of Christopher Faylor
> Sent: Monday, February 07, 2005 2:44 PM
> To: cygwin@cygwin.com
> Subject: Re: hyperthreading fix, try #1
> 
> On Mon, Feb 07, 2005 at 08:17:52AM +0100, Volker Bandke wrote:
> >Which system configuration did you use to recreate the problem?
> 
> I got enough donations to purchase the following:
> 
> Motherboard:  ASUS P4P800SE 
> Memory:   1G
> CPU:  CPU P4/3.0EGHz 800M 478P/1MB HT RT
> HD:   Samsung 120GB
> Case: ASPIRE XINFINITY BL 350W RTL
> 
> I purchased this from Newegg.  I love that company.
> 
> I put the system together in one night, turned it on, and it worked.
> All of the lights came on correctly, the system booted with a 
> CD, and transferring data from my old system proceeded 
> without a hitch, thanks to my knoppix CD -- love that knoppix, too.
> 
> The one thing that took me forever to fix was getting XP running.
> Somehow my XP CD got cracked with a big chunk taken out of 
> it, so I had to get a new CD, and I ended up transferring 
> data from my old system multiple times as I attempted to 
> install the new CD without overwriting all of my existing data.
> 
> The way I usually do this is to copy raw partitions over, 
> since my windows box is multi-boot and represents years of 
> work.  Sometimes the OS figures out how to reconfigure 
> itself, sometimes it needs a nudge.
> In this case, it needed to be whacked with a large branch.
> 
> I couldn't get W2K working but I've held off further 
> investigations in that for another time.
> 
> >also, can you describe (in _short_ terms) the cause of the error?
> 
> Cygwin has a problem because normal pipe I/O on windows is 
> not interruptible (generically speaking - you could kludge it on NT).
> So, to work around this problem, it starts up pipe i/o in a 
> thread and kills the thread when a signal comes in.  It's a 
> sledge hammer approach to interrupting pipe I/O.
> 
> The pipe thread uses a synchronization event to tell the 
> initiating reader when the pipe is all set, has grabbed its 
> arguments and is ready to go.  This event was also used to 
> tell the reader that there was a successful read.
> 
> Previous to my fix, cygwin did not reliably wait for both 
> events to happen so, after the first read on a pipe, it would 
> become out of sync.  This would present a problem on any kind 
> of SMP-like system but it wouldn't be as noticeable on a 
> non-SMP system.
> 
> Once I ran the test case twenty times or so, I went back and 
> looked at the code I'd previously stared at for hours and saw 
> a few synchronization issues.  For once the back trace from 
> gdb showed that something was clearly amiss.
> 
> So, the fix was to try much harder to ensure that we've 
> correctly waited for notification events, even in the 
> scenario when cygwin thinks it has to terminate a thread due 
> to the arrival of a signal.  It is possible that the read has 
> completed in that case and cygwin should not throw the data 
> away since the read really *wasn't* terminated by a signal.
> 
> Unfortunately, there is still a race here.  I have an idea 
> about how to fix the race but it would introduce a 
> destabilizing change that I'd rather not chance before 1.5.13 
> is released.  Given that I can't reproduce the problem with 
> the test script anymore, I think I'll release cygwin with 
> this change plus any other potential fixes required to handle 
> the "make -j" problem.
> 
> 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/
> 


--
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: RFE: enhance setup.exe to used cached mirrors file

[Igor Pechtchanski]

Yuk, top-posting.  Reformatted.

On Mon, 7 Feb 2005, linda w wrote:

> Alexey N. Solofnenko wrote:
>
> > Would not it be great if Cygwin's setup did not just fail if
> > mirrors.lst is unavailable and continued with just last server in the
> > list? I tried to install Cygwin KDE, but setup was failing on a
> > completely unrelated to what I was doing problem.
>
> I 2nd this request -- wanted to install some other packages but was
> blocked by the mirrors.txt download -- maybe it could use a cached copy
> of mirrors.txt to look at other mirror files -- i.e. cache mirrors.txt
> on the existing mirrors so if cygwin server is down, setup would use
> existing mirrors to avoid a single point of failure -- but still check
> mirrors.txt on cygwin.com if it was up.

The best way to second such requests is with a patch.  Remember,
. :-)
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/

perl & Win32 lib support

[linda w]

I thought there had been a fix in the works for this problem -- I
wanted to write a program using cygwin perl to access/modify the Registry.
When I load the Win32 package from cpan and try building it, I get
a familiar error message "IsWinNT" is undefined, so building and
installing cpan registry access routines isn't possible. 

Is there something else that would break if "IsWinNT" is set to
"true" if the underlying OS is NT based (or IsWin95 for Win9x/Me)?
I might be able to use ActiveState's Perl, but it doesn't play
so well with CPAN and doesn't seem to handle Cygwin paths very well
either.
Was there a work-around for this?
Thanks,
-linda
--
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/

RFE: enhance setup.exe to used cached mirrors file (was Re: sourceware.org downtime)

[linda w]

I 2nd this request -- wanted to install some other packages but was
blocked by the mirrors.txt download -- maybe it could use a cached
copy of mirrors.txt to look at other mirror files -- i.e. cache mirrors.txt
on the existing mirrors so if cygwin server is down, setup would use
existing mirrors to avoid a single point of failure -- but still
check mirrors.txt on cygwin.com if it was up. 

??
-linda

Alexey N. Solofnenko wrote:
Would not it be great if Cygwin's setup did not just fail if 
mirrors.lst is unavailable and continued with just last server in the 
list? I tried to install Cygwin KDE, but setup was failing on a 
completely unrelated to what I was doing problem.

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

Installing in root (was Re: Linux Journal Cygwin article)

[linda w]

Perhaps he has read that many developers and users on this list
use "C:\" as the root diretory and have no problems.  I had the
impression that the advice to install into a subdirectory was more
of a Covering One's Behind (COB?) when presenting cygwin as a commercial
solution to vendors.  I find it more useful to have it in the root
directory, as I use my cygwin tools and shell to manage my XP machine
instead of the Windows tools.  I have yet to run into a problem
with conflicting software ...
Is it still worth the extra hassle of separating cygwin into it's
own sub-root?  I integrated my cygwin and windows home as well --
they are both "/home/"; i.e. "Documents and Settings" on
my machine has been renamed/changed to /home.
I strongly wish that I wouldn't get the "reminder" of not
installing in "root" as I've had for the past three+ years --
if I've already installed there, I've already seen that warning
message countless times before (sigh)...
Maybe the advice not to install in root could be reconsidered?
Has anyone had any problems installing in root?
Defaulting to a subdirectory is probably the "right" thing to do,
but on the good/bad scale, certainly choosing "\" to install in
isn't like crossing the streams or something, eh? :-)
-linda
Christopher Faylor wrote:
And the author actually gives some bad advice of not using the default
c:\cygwin root directory, claiming that we said it was best to do things
that way.  Why would we have a program with a default that
we didn't want people to use?
--
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/

svn on apache on Cygwin?

[Steve Kelem]

Does anyone have a pointer on how to build apache on Cygwin so that it 
supports svn?

Thanks for your help,
Steve Kelem


--
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: hyperthreading fix, try #1

[Markus Schönhaber]

Dave Korn wrote:
  I thought you meant CGF should be promoted to Sherriff!
Oh no! He's much to mean for being promoted to Sherriff.
Think of the children!
But those gold stars are more then well deserved. Thanks cgf!
Regards
  mks
--
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 web site?

[James Merritt]

Hi,

Got connected just now to cygwin.com.  Installed
Cygwin on another computer Saturday, downloaded the
setup.exe file, and had no problems connecting.  Even
last Thursday and Friday I was able to connect with no
problems.  And I am using dialup, if that makes a
difference.

Have a great day!!

James E. Merritt

--- Dario Alcocer <[EMAIL PROTECTED]> wrote:

> Gene Smith wrote:
> > Where has the cygwin web site gone? Seem to be
> refusing connections.
> > http://www.cygwin.com/
> 
> Just to confirm your observation, I've not been able
> to get connect to 
> www.cygwin.com since Thursday.  A friend of mine
> tried installing last 
> Friday and got the same result.
> 
> -- D.
> 
> 
> --
> 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/
> 
> 





__ 
Do you Yahoo!? 
Yahoo! Mail - You care about security. So do we. 
http://promotions.yahoo.com/new_mail

--
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: hyperthreading fix, try #1

[Christopher Faylor]

On Mon, Feb 07, 2005 at 08:17:52AM +0100, Volker Bandke wrote:
>Which system configuration did you use to recreate the problem?

I got enough donations to purchase the following:

Motherboard:ASUS P4P800SE 
Memory: 1G
CPU:CPU P4/3.0EGHz 800M 478P/1MB HT RT
HD: Samsung 120GB
Case:   ASPIRE XINFINITY BL 350W RTL

I purchased this from Newegg.  I love that company.

I put the system together in one night, turned it on, and it worked.
All of the lights came on correctly, the system booted with a CD, and
transferring data from my old system proceeded without a hitch, thanks
to my knoppix CD -- love that knoppix, too.

The one thing that took me forever to fix was getting XP running.
Somehow my XP CD got cracked with a big chunk taken out of it, so I had
to get a new CD, and I ended up transferring data from my old system
multiple times as I attempted to install the new CD without overwriting
all of my existing data.

The way I usually do this is to copy raw partitions over, since my
windows box is multi-boot and represents years of work.  Sometimes the
OS figures out how to reconfigure itself, sometimes it needs a nudge.
In this case, it needed to be whacked with a large branch.

I couldn't get W2K working but I've held off further investigations in
that for another time.

>also, can you describe (in _short_ terms) the cause of the error?

Cygwin has a problem because normal pipe I/O on windows is not
interruptible (generically speaking - you could kludge it on NT).
So, to work around this problem, it starts up pipe i/o in a thread
and kills the thread when a signal comes in.  It's a sledge hammer
approach to interrupting pipe I/O.

The pipe thread uses a synchronization event to tell the initiating
reader when the pipe is all set, has grabbed its arguments and is ready
to go.  This event was also used to tell the reader that there was a
successful read.

Previous to my fix, cygwin did not reliably wait for both events to
happen so, after the first read on a pipe, it would become out of
sync.  This would present a problem on any kind of SMP-like system
but it wouldn't be as noticeable on a non-SMP system.

Once I ran the test case twenty times or so, I went back and looked at
the code I'd previously stared at for hours and saw a few
synchronization issues.  For once the back trace from gdb showed that
something was clearly amiss.

So, the fix was to try much harder to ensure that we've correctly waited
for notification events, even in the scenario when cygwin thinks it has
to terminate a thread due to the arrival of a signal.  It is possible
that the read has completed in that case and cygwin should not throw the
data away since the read really *wasn't* terminated by a signal.

Unfortunately, there is still a race here.  I have an idea about how to
fix the race but it would introduce a destabilizing change that I'd
rather not chance before 1.5.13 is released.  Given that I can't
reproduce the problem with the test script anymore, I think I'll release
cygwin with this change plus any other potential fixes required to
handle the "make -j" problem.

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: hyperthreading fix, try #1

[Igor Pechtchanski]

On Mon, 7 Feb 2005, Christopher Faylor wrote:

> On Mon, Feb 07, 2005 at 09:32:09AM -0500, Igor Pechtchanski wrote:
> >On Mon, 7 Feb 2005, Corinna Vinschen wrote:
> >>On Feb 7 08:17, Brian Gallew wrote:
> >>>Christopher Faylor wrote:
> Fixing that seems to have fixed my hyperthreading problems.  I have run
> three invocations of the scripts for four days without a hiccup.
> Previously, I had problems within minutes.
> >>>
> >>>Go, you! Someone should give you a gold star for this.
> >>
> >>Igor?  Ready to polish a gold star for cgf?
> >
> >Always.  Regular ones I have a-plenty, just don't ask me for the
> >flashing ones.  ;-)
>
> Let's wait until a fix has been fully confirmed.  That hasn't happened yet.

 and
 look like
confirmations to me.  Besides, if you get one gold star per fixed bug they
will all be well-deserved. :-)
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: cc1plus : out of memory

[Igor Pechtchanski]

Ugh, top-posting...  Reformatted.

On Mon, 7 Feb 2005, Alexis Cothenet wrote:

> On Mon, 7 Feb 2005, Igor Pechtchanski wrote:
>
> > On Mon, 7 Feb 2005, Alexis Cothenet wrote:
> >
> > > Hi all,
> > >
> > > the subject is the error message i gave compiling a simple programm
> > > on cygwin. I tried to compile it under Linux OS and it worked fine.
> > > Does someone knows what is the problem and how could i soulve it ?
> >
> > You could start by reviewing and following the Cygwin problem reporting
> > guidelines at ...  Also,
> > .
> > Igor
>
> Hi,
>
> I have already seen this page but this mailing list seems to me
> the better one for this question, am i wrong ?
> I have ever checked on google what could be the reason of this message
> during a compilation.
> It was indicated that it could be relied on the gcc version but
> the cygwin gcc version i have is 3.3.3 and it didn't work. The Linux gcc
> version on which i compiled with success is 2.96...
>
> Does someone has ever had this problem using cygwin ?
> (I didn't found it on the archives...)

What exactly on that page made you think you should address another list?
The page does ask you to provide the information about your system by
attaching the output of "cygcheck -svr".  I've also asked you to "Please
Provide A Simple Testcase" (that's what PPAST means, since you obviously
haven't followed the acronym link).  Without this information (your system
setup, environment, the exact program that produced this error and how you
compile it) nobody on this list will be able to help you.
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: hyperthreading fix, try #1

[Dave Korn]

> -Original Message-
> From: cygwin-owner On Behalf Of CV
> Sent: 07 February 2005 18:54

> CV  hotmail.com> writes:
> > Another vote for the silver star !
> 
> Oops, I meant the gold star of course !
> 
> Cheers CV
> 


  I thought you meant CGF should be promoted to Sherriff!


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: hyperthreading fix, try #1

[CV]

CV  hotmail.com> writes:
> Another vote for the silver star !

Oops, I meant the gold star of course !

Cheers CV




--
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: hyperthreading fix, try #1

[CV]

Christopher Faylor  cygwin.com> writes:

> I'm not naive enough to think that I've solved all of the hyperthreading
> problems but I would like people to try today's snapshot (or any
> snapshot newer than today's) and report on whether it solves the problem
> or not.  If it doesn't, please provide as simple a test case as possible
> so that I can duplicate the problem.

Working well here: HP Pavilion with P4HT3.2G.

I only ran into the hyperthreading bug the other day when trying
to chown a large directory tree. It would bomb out after a minute
or two (a few hundred to maybe a thousand files).

With the new build (whether stripped with --strip-debug or unstripped)
the command completes as expected.

Another vote for the silver star !
Cheers CV


--
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 web site?

[Dario Alcocer]

Gene Smith wrote:
Where has the cygwin web site gone? Seem to be refusing connections.
http://www.cygwin.com/
Just to confirm your observation, I've not been able to get connect to 
www.cygwin.com since Thursday.  A friend of mine tried installing last 
Friday and got the same result.

-- D.
--
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: tee piping to head gives error message

[Buchbinder, Barry (NIH/NIAID)]

At Monday, February 07, 2005 1:13 PM, Dave Korn wrote:
>> -Original Message-
>> From: cygwin-owner On Behalf Of Buchbinder, Barry (NIH/NIAID)
>> Sent: 07 February 2005 17:28
> 
>> As described in the Subject.  Though it seems that everything works
>> OK; tee just gives and error message under some circumstances.
>> 
>> /tmp> cat stafflist.htm | tee ttt | head > /dev/null
>> tee: standard output: Broken pipe
> 
>> So the file that tee write looks good and the write error is
>> only to the pipe.
> 
>   That'll be because head closed the pipe, and tee was still trying
> to write into it.

Further experimentation supported that.  Inserting cat between tee and head
did not eliminate the error message, while inserting sort did.
 
>> So head seems to be passing on the number of lines that ones
>> asks it to pass on.
> 
>   Given that the purpose of head is to print the first few lines of a
> file, it kind of makes sense to me that it would close the file after
> it's read them rather than keeping the input file open and manually
> reading-and-discarding the entire rest of it for no good reason.

Agreed.

>   So I reckon this is as-expected and by-design behaviour.

I might put it as "as-designed" rather than "by-design".  And for me, it
certainly was unexpected.  tee and head are both part of coreutils.  I would
expect that all coreutils would behave the same for head closing the pipe,
but they don't.  And I would also expect that all utilities in a package
that includes a utility that breaks pipes as a normal course of its
operation would be silent when the two utilities are used together.  I would
expect that tee pipes to head more often than something nasty happens and a
pipe just breaks.

This seems like something the coreutils maintainer might want to address
with the upstream maintainers, or to patch himself.  (I won't complain if he
doesn't patch it.  Taking on coreutils was quite a commitment -- well
deserving of the two gold stars -- and I know that fixing this may be a low
priority.)  Unfortunately, though PTC, I'm not capable of providing a patch.
In any case, tee seems to save its input as desired, so while the error
message is annoying and misleading, I suppose that one can live with it.

>> So it seems to be specific to piping from tee to head.
> 
>   It's just that tee notices when a write to stdout fails, whereas
> most applications are more loosely coded and don't check.
> 
>> But the number of lines/bytes at which the error disappears
>> does not seem to be constant.
> 
>   Umm, no,  it's equal to the number of lines in the source file.

No.  It should be equal to the numbers of lines in the source file but is
not.  The error message went away around 126 or 130 lines, while the source
file had 556.

(I would speculate that the disappearance of the error messages when enough
lines are provided might have something to do with buffering, but I'm not a
programmer and speculation by we mere "users" is sometimes discouraged.  As
for why it is not consistent ...)
 
>> So it seems that when given enough lines/bytes, there is no
>> error message.
> 
>   If you ask head for less lines than are in the source file, it
> closes its input (which is tee's output) before tee has written the
> entire file, and tee complains.  OTOH if you ask head for >= the
> number of lines in the source file, tee completes, and head notices
> that it has no more input and exits gracefully. 
> 
>> Everything should be up to date.
> 
>   Except perhaps your caffeine levels this morning ?
> 
> 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: cc1plus : out of memory

[Dave Korn]

> -Original Message-
> From: cygwin-owner On Behalf Of Alexis Cothenet
> Sent: 07 February 2005 16:22

> I have already seen this page but this mailing list seems to me
> the better one for this question, am i wrong ?

  This sentence doesn't even make sense, how could there possibly be a choice of
one or the other?  One is a web page, the other is a mailing list.  The web page
tells you what kind of information you would need to send to the mailing list
for people to be able to help you.  You aren't supposed to try and talk to the
web page, they aren't alive and can't talk back to you.  

  Now go and read that web page again, and read it more carefully this time.

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/

AT&T ksh93

[Glenn Fowler]

On 17 Dec 2004 16:35:31 - Christopher Faylor wrote:

> I'd like to note for the archives also that I'd like to get the real version
> of ksh into the cygwin distribution.

> This comes up from time to time.  The first time it happened someone was 
> insisting
> that they needed to change the cygwin DLL for this to happen and I had 
> reservations
> about the licensing status of some of the changes since the person had also 
> seen
> U/WIN sources.  Then, somehow, ksh was built without the need to change 
> cygwin and
> a cygwin ksh package was going to show up any second now.

> Well, years later, we still don't have a ksh.

> Anyone want to take the plunge?

Rather than waste time arguing about cygwin correctness, we added
section 2 system call intercepts to our base library to get cygwin to
act like unix.  The library intercepts keep windows from contaminating
our mainline source and scripts.  For details see

http://www.research.att.com/sw/download/win32/

Since the last cygwin round AT&T ksh93, ast libraries, and UWIN source
and binaries have been released uder the OSI approved CPL 1.0
(Common Public License 1.0.)  I packaged the 2005-02-02 standalone
ksh for cygwin and posted setup.hint, tarballs and md5 sums at

http://www.research.att.com/sw/download/beta/

The packages under this URL are password protected.  See

http://www.research.att.com/sw/download/faq.license.html

for the rationale and name and password to use (the same name and
password for every user.)

I believe previous ksh93 vs. cygwin issues mentioned on this list have
been addressed in this release.

I won't be the cygwin ksh93 maintainer, but I can supply cygwin
packages at the above URL to the maintainer, including any changes
required in the package files.  All of our packages, including the
cygwin ones, are generated by table driven scripts, so any cygwin
specific package changes will be rolled back into those tables and
scripts.

-- Glenn Fowler -- AT&T Research, Florham Park NJ --


--
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: tee piping to head gives error message

[Dave Korn]

> -Original Message-
> From: cygwin-owner On Behalf Of Dave Korn
> Sent: 07 February 2005 18:13


> 
> > But the number of lines/bytes at which the error disappears 
> > does not seem to be constant.


  Ah, I just managed to reproduce this.  That is indeed rather strange.  Hmm.  

  Oh, hang on, it gets more interesting, I just got it to *really* fail.  Here's
a test on a file with 4207 lines in it.

[EMAIL PROTECTED] /artimi/firmware> cat diffs.txt  | tee tmp2.txt  | head -4100 
> /dev/nu
ll
tee: write error
[EMAIL PROTECTED] /artimi/firmware> cat diffs.txt  | tee tmp2.txt  | head -4100 
> /dev/nu
ll
[EMAIL PROTECTED] /artimi/firmware> cat diffs.txt  | tee tmp2.txt  | head -4100 
> /dev/nu
ll
[EMAIL PROTECTED] /artimi/firmware> cat diffs.txt  | tee tmp2.txt  | head -4100 
> /dev/nu
ll
tee: write error
[EMAIL PROTECTED] /artimi/firmware>
[EMAIL PROTECTED] /artimi/firmware>
[EMAIL PROTECTED] /artimi/firmware> cat diffs.txt  | tee tmp2.txt  | head -4100 
> /dev/nu
ll
tee: write error
[EMAIL PROTECTED] /artimi/firmware> cat diffs.txt  | tee tmp2.txt  | head -4100 
> /dev/nu
ll
tee: write error
[EMAIL PROTECTED] /artimi/firmware> cat diffs.txt  | tee tmp2.txt  | head -4100 
> /dev/nu
ll
Terminate batch job (Y/N)?


  Wow.  The last time where I tried it, it paused for a long time as if it had
hung, and then managed to kill my entire bash shell and cygwin.bat session.  I
guess there really is a bug there.

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: tee piping to head gives error message

[Dave Korn]

> -Original Message-
> From: cygwin-owner On Behalf Of Buchbinder, Barry (NIH/NIAID)
> Sent: 07 February 2005 17:28

> As described in the Subject.  Though it seems that everything works OK; tee
> just gives and error message under some circumstances.
> 
> 
> /tmp> cat stafflist.htm | tee ttt | head > /dev/null
> tee: standard output: Broken pipe

> So the file that tee write looks good and the write error is 
> only to the pipe.

  That'll be because head closed the pipe, and tee was still trying to write
into it.

> So head seems to be passing on the number of lines that ones 
> asks it to pass on.

  Given that the purpose of head is to print the first few lines of a file, it
kind of makes sense to me that it would close the file after it's read them
rather than keeping the input file open and manually reading-and-discarding the
entire rest of it for no good reason.

  So I reckon this is as-expected and by-design behaviour.

> So it seems to be specific to piping from tee to head.

  It's just that tee notices when a write to stdout fails, whereas most
applications are more loosely coded and don't check.

> But the number of lines/bytes at which the error disappears 
> does not seem to be constant.

  Umm, no,  it's equal to the number of lines in the source file.

> So it seems that when given enough lines/bytes, there is no 
> error message.

  If you ask head for less lines than are in the source file, it closes its
input (which is tee's output) before tee has written the entire file, and tee
complains.  OTOH if you ask head for >= the number of lines in the source file,
tee completes, and head notices that it has no more input and exits gracefully.

> Everything should be up to date.  

  Except perhaps your caffeine levels this morning ?

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: cc1plus : out of memory

[Alexis Cothenet]

Hi,

I have already seen this page but this mailing list seems to me
the better one for this question, am i wrong ?
I have ever checked on google what could be the reason of this message 
during a compilation.
It was indicated that it could be relied on the gcc version but
the cygwin gcc version i have is 3.3.3 and it didn't work. The Linux gcc 
version on which i compiled with success is 2.96...

Does someone has ever had this problem using cygwin ?
(I didn't found it on the archives...)

Thanks a lot in advance.

Regards,
Alexis


On Mon, 7 Feb 2005, Igor Pechtchanski wrote:

> On Mon, 7 Feb 2005, Alexis Cothenet wrote:
> 
> > Hi all,
> >
> > the subject is the error message i gave compiling a simple programm
> > on cygwin. I tried to compile it under Linux OS and it worked fine.
> > Does someone knows what is the problem and how could i soulve it ?
> 
> You could start by reviewing and following the Cygwin problem reporting
> guidelines at ...  Also,
> .
>   Igor
> 

-- 
*
  Alexis COTHENET
  Docteur en Physique Mathematique, Particules, Modelisation
  Specialites: Developpements informatiques,
   Modelisation/simulation, Traitement/analyse de donnees,
   algorithmes statistiques, mathematiques
  CV disponible sur: http://marwww.in2p3.fr/~cothenet
*


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

tee piping to head gives error message

[Buchbinder, Barry (NIH/NIAID)]

As described in the Subject.  Though it seems that everything works OK; tee
just gives and error message under some circumstances.


/tmp> cat stafflist.htm | tee ttt | head > /dev/null
tee: standard output: Broken pipe
tee: write error
/tmp> wc ttt
  556  1738 21441 ttt
/tmp> wc stafflist.htm
  556  1738 21441 stafflist.htm
/tmp> cmp stafflist.htm ttt
/tmp>


So the file that tee write looks good and the write error is only to the
pipe.


tee: standard output: Broken pipe
 10  38 484
tee: write error
/tmp> cat stafflist.htm | tee ttt | head -50 | wc
tee:  50 1671832
standard output: Broken pipe
tee: write error
/tmp> cat stafflist.htm | tee ttt | head -125 | wc
tee: standard output: Broken pipe125 3434103

tee: write error
/tmp> cat stafflist.htm | tee ttt | head -50 | wc
tee: standard output: Broken pipe 50 1671832

tee: write error
/tmp> cat stafflist.htm | tee ttt | head | wc
tee: standard output: Broken pipe
 10  38 484
tee: write error
/tmp> cat stafflist.htm | tee ttt | head -126 | wc
tee: standard output: Broken pipe126 3454121

tee: write error
/tmp> cat stafflist.htm | tee ttt | head -127 | wc
tee: standard output: Broken pipe127 3494153

tee: write error
/tmp> cat stafflist.htm | tee ttt | head -130 | wc
130 3594309
1 /tmp> cat stafflist.htm | tee ttt | head -800 | wc
5561738   21441
/tmp>


So head seems to be passing on the number of lines that ones asks it to pass
on.


/tmp> cat stafflist.htm | tee ttt | tail > /dev/null
/tmp> cat stafflist.htm | tee ttt | tac > /dev/null
/tmp> cat stafflist.htm | tee ttt | cat > /dev/null
/tmp> cat stafflist.htm | tee ttt | sed -e 's/^/-/' > /dev/null
/tmp> cat stafflist.htm | tee ttt | wc > /dev/null
/tmp> cat stafflist.htm | tee ttt | head > /dev/null
tee: standard output: Broken pipe
tee: write error
/tmp> cat stafflist.htm | head > /dev/null
/tmp> cmp stafflist.htm ttt
/tmp>


So it seems to be specific to piping from tee to head.


/tmp> wc stafflist.htm
  556  1738 21441 stafflist.htm
/tmp> cat stafflist.htm | tee ttt | head -50 > /dev/null
tee: standard output: Broken pipe
tee: write error
/tmp> cat stafflist.htm | tee ttt | head -120 > /dev/null
tee: standard output: Broken pipe
tee: write error/tmp>
/tmp> cat stafflist.htm | tee ttt | head -125 > /dev/null
tee: standard output: Broken pipe
tee: write error
/tmp> cat stafflist.htm | tee ttt | head -126 > /dev/null
/tmp> cat stafflist.htm | tee ttt | head -130 > /dev/null
/tmp>


So it seems that when given enough lines/bytes, there is no error message.
But the number of lines/bytes at which the error disappears does not seem to
be constant.


Everything should be up to date.  cygcheck.out is attached.


- Barry



cygcheck.out
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/

Corrupted distribution files

[Keith Moore]

docbook-xsl/docbook-xsl-1.67.2-1-src.tar.bz2 and 
gettext/libintl1/libintl1-0.10.40-1-src.tar.bz2 appear to be corrupt on 
some of the distribution servers.

I've checked three separate mirrors: 
http://mirrors.kernel.org/sources.redhat.com/cygwin/release/, 
http://ftp.gwdg.de/pub/linux/sources.redhat.com/cygwin/release/, and 
http://sunsite.icm.edu.pl/pub/cygnus/cygwin/release/.

docbook-xsl is corrupted on all three mirrors.
libintl1 appears to be corrupted on mirrors.kernel.org only (ftp.gwdg.de 
and sunsite.icm.edu.pl look OK).

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

sshd and "No buffer space available"

[di dit]

Hi,

First, a big "thank you" to all of you for your incredible job.

Here is a bug report regarding sshd on cygwin. I use it on a Win 98
PC that I keep running "always". I have sshd started at the beginning
and it works fine ... except after a few days. Then I can't use the network.
When trying to connect to another host, putty and ssh from cygwin on
this same machine return:
  Network error: No buffer space available
ping from cygwin on the same machine works, but trying to ping this
machine from another host does not work.
It is sshd's fault, because if I kill the sshd process and restart it, then
everything works as expected again.

didit

--
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: hyperthreading fix, try #1

[Rolf Campbell]

Volker Bandke wrote:
 
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1

Rolf,
a)  Your test case fails on my machine as well, right at the
beginning
b)  I seem to remember that there was/is a separate problem with "make
- -j", even on non-hyperthreasd machines.  Unfortunately I cannot
search the mailing list right now due to some error (that possibly
has to do with cygwin.com's earlier breakdown.  I do remember a
sentence somewhere like "We don't recommend that you use 'make -j' as
it seems to be broken"
c)  Running your testcase with '-j1' instead of '-j2' does not fail on
my machine
Thanks for you info Volker.  Here's what I've figured out:
This test does fail (in the same way) on non-hyperthreaded machines 
(Win2000Pro on a PIII).  But, this is a regression from 1.5.12 (that 
test runs fine on the non-HT machine with 1.5.12.  There was (maybe 
still is) a problem with running "make -j" without the max task counter, 
but "make -j2" has always worked very well on non-ht machines.

I will try out some other snapshots and see if I can narrow down the 
time when this showed up later today.

-Rolf
--
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: hyperthreading fix, try #1

[Christopher Faylor]

On Mon, Feb 07, 2005 at 09:32:09AM -0500, Igor Pechtchanski wrote:
>On Mon, 7 Feb 2005, Corinna Vinschen wrote:
>>On Feb 7 08:17, Brian Gallew wrote:
>>>Christopher Faylor wrote:
Fixing that seems to have fixed my hyperthreading problems.  I have run
three invocations of the scripts for four days without a hiccup.
Previously, I had problems within minutes.
>>>
>>>Go, you! Someone should give you a gold star for this.
>>
>>Igor?  Ready to polish a gold star for cgf?
>
>Always.  Regular ones I have a-plenty, just don't ask me for the
>flashing ones.  ;-)

Let's wait until a fix has been fully confirmed.  That hasn't happened yet.

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: cc1plus : out of memoey

[Igor Pechtchanski]

On Mon, 7 Feb 2005, Alexis Cothenet wrote:

> Hi all,
>
> the subject is the error message i gave compiling a simple programm
> on cygwin. I tried to compile it under Linux OS and it worked fine.
> Does someone knows what is the problem and how could i soulve it ?

You could start by reviewing and following the Cygwin problem reporting
guidelines at ...  Also,
.
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: How to start up cygwin so all users use the same home dir and environment?

[Jesper Vad Kristensen]

As is often the case my fractured mind finds itself speaking to ...
itself. 

Anyway, I tried something and changed my cygwin.bat to this:

@echo off
C:
chdir C:\cygwin\bin
->  set HOME=/cygdrive/c/cygwin/home/elhack
->  set USER=elhack
->  set USERNAME=elhack
bash --login -i

I also made an entry for "elhack" user in /etc/passwd

This seems, so far, to have provided me with the necessary way to force
cygwin to start with a specific/shared user account even if I'm logged
into the computer as another person. I just thought I'd share the
discovery with you :)

Regards,

Jesper Vad Kristensen


>-Original Message-
>From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] 
>On Behalf Of Jesper Vad Kristensen
>Sent: Thursday, February 03, 2005 3:18 PM
>To: cygwin@cygwin.com
>Subject: How to start up cygwin so all users use the same home 
>dir and environment?
>
>
>Hi there,
>
>I'm trying to do something odd (I'll explain the "why" later), but
>here's what I would like to do:
>
>All users here are in the same Windows Domain, and I would like an
>unknown number of users to be able to log into this one Windows server,
>and when they start cygwin there I would like them all to use, say,
>/cygdrive/c/cygwin/home/shareduser as home dir (~/). I.e. no matter who
>logs into the windows box they all share the one and same cygwin
>environment.
>
>Just a bit of explanation on why I'd go and do something stupid like
>this. Well, it all boils down to a paranoid security department and
>being in a large organization where technical concerns 
>sometimes have to
>be subordinated to bureaucracy. The server is installed with 
>Windows and
>Cygwin and some other tools. One department (=they) is responsible for
>taking requests from developers/project leaders (=us) and putting
>software in production. These tech boys will ideally only have to know
>one thing: which server to login to, and what keys to poke once inside.
>I.e. security is at the level of domain login to the Windows server.
>Once inside they're welcome to do whatever they want on the server,
>specifically in our case: compile source code, get executables and put
>them into production. There will never be two persons logged in at the
>same time. The server will be used for nothing else.
>
>If this is doable it's easy: just add the tech boys to a group on the
>Domain and they (whoever they are, however many they are) have 
>access to
>the tool they need to use to put things into production. What they have
>to do is start cygwin, run a script with the right parameters, read the
>error log and that's it. (Of course, I should perhaps have 
>made the tool
>exclusively in Windows, but I needed perl, gnu file utils, etc. because
>it's so easy to work with.)
>
>Regards,
>
>Jesper Vad Kristensen
>Denmark
>
>--
>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: hyperthreading fix, try #1

[Igor Pechtchanski]

On Mon, 7 Feb 2005, Corinna Vinschen wrote:

> On Feb  7 08:17, Brian Gallew wrote:
> > Christopher Faylor wrote:
> > >Fixing that seems to have fixed my hyperthreading problems.  I have run
> > >three invocations of the scripts for four days without a hiccup.
> > >Previously, I had problems within minutes.
> >
> > Go, you!  Someone should give you a gold star for this.
>
> Igor?  Ready to polish a gold star for cgf?

Always.  Regular ones I have a-plenty, just don't ask me for the flashing
ones. ;-)
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: hyperthreading fix, try #1

[Corinna Vinschen]

On Feb  7 08:17, Brian Gallew wrote:
> Christopher Faylor wrote:
> >Fixing that seems to have fixed my hyperthreading problems.  I have run
> >three invocations of the scripts for four days without a hiccup.
> >Previously, I had problems within minutes.
> 
> Go, you!  Someone should give you a gold star for this.

Igor?  Ready to polish a gold star for cgf?


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/

cc1plus : out of memoey

[Alexis Cothenet]

Hi all,

the subject is the error message i gave compiling a simple programm
on cygwin. I tried to compile it under Linux OS and it worked fine.
Does someone knows what is the problem and how could i soulve it ?

Thanks very much.

Cheers,
Alexis



--
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: perl winpid?

[Reini Urban]

Igor Pechtchanski schrieb:
On Sun, 6 Feb 2005, Reini Urban wrote:
I feel quite stupid now, but found nothing simple.
How to get the winpid from the current process in cygwin's perl?
$$ is the cygwin pid which is different from the windows pid
GetCurrentProcessId().
winpid = cygwin_internal(CW_CYGWIN_PID_TO_WINPID, pid) ?
Sure, but in any perl API?
There's apparently a new libwin32@perl.org list,
the [EMAIL PROTECTED] list is almost 
unmaintained for some years now.

We will check out there where this cygwin specific functionality
will go to.
Win32::Process::CygwinToWin32ProcessID() is my suggestion.
.pm:
=item Win32::Process::CygwinToWin32ProcessID($pid)
Returns the windows process ID for the given cygwin pid.
On non-cygwin platforms it will return the $pid argument without 
translation.

=item Win32::Process::Win32ToCygwinProcessID($pid)
Returns the cygwin process ID for the given windows pid.
On non-cygwin platforms it will return the $pid argument without 
translation.

.xs:
DWORD
CygwinToWin32ProcessID(pid)
DWORD pid
CODE:
#ifdef __CYGWIN__
RETVAL = cygwin_internal(CW_CYGWIN_PID_TO_WINPID, pid);
#else
RETVAL = pid;
#endif
OUTPUT:
RETVAL
DWORD
Win32ToCygwinProcessID(pid)
DWORD pid
CODE:
#ifdef __CYGWIN__
RETVAL = (DWORD)cygwin32_winpid_to_pid(pid);
#else
RETVAL = pid;
#endif
OUTPUT:
RETVAL
--
Reini Urban
http://xarch.tu-graz.ac.at/home/rurban/
--
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: hyperthreading fix, try #1

[Brian Gallew]

Christopher Faylor wrote:
Fixing that seems to have fixed my hyperthreading problems.  I have run
three invocations of the scripts for four days without a hiccup.
Previously, I had problems within minutes.
Go, you!  Someone should give you a gold star for this.
--
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 start a Win gui app on remote server

[Christian Weinberger]

Alexander

The solution works, but be aware that there is a drawback running sshd in
interactive mode:

Whenever a user logs off from the server PC with the windows logoff function,
windows ends all currently running ssh sessions.

Search the list for a more detailed explanation.

Regards,
Christian





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

ScanMail Notification.

[NCLUSTER/RU/ISTC . ISTC]

At 02/07/05 14:02:44, Attachment Filter detected on server
CN=NCLUSTER/OU=RU/O=ISTC:

ScanMail detected my_numbers.exe matched the Attachment Filter "Filter
Attachment by File Type > Extension name(s)" setting and took this action:
Block.


in a message from cygwin@cygwin.com to [EMAIL PROTECTED], and took this action:
Block.

Detected by ScanMail for Domino 3.0.0.1280
using pattern file version (NULL)
and scan engine version (NULL).


--
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: Cygserver 100% CPU

[Patrick Samson]

--- Corinna Vinschen wrote:
> I've checked in a patch which uses a somewhat more
> complicated 
> synchronization method in msleep.  The testsuite
> testcases still
> work as expected but I would like to get some
> feedback on your issue.
> Please test cygserver from the next Cygwin snapshot
> or build your
> own.  Does the new code help or at least change
> anything?

Sorry for the delay, but I do not have access to
the systems anymore, so I can't test your new code
right now. I had a look at the code and it seems
better than before, I agree.
I still hope to be able to test the solution in the
future, but it may take some time.
I will keep you informed.




__ 
Do you Yahoo!? 
Meet the all-new My Yahoo! - Try it today! 
http://my.yahoo.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/