opus 1.5.2-1

2024-04-12 Thread Takashi Yano via Cygwin-announce
The following packages have been uploaded to the Cygwin distribution:

* libopus0-1.5.2-1
* libopus-devel-1.5.2-1
* libopus-doc-1.5.2-1

The Opus codec is designed for interactive speech and audio
transmission over the Internet. It is designed by the IETF Codec Working
Group and incorporates technology from Skype's SILK codec and Xiph.Org's
CELT codec.
-- 
  *** CYGWIN-ANNOUNCE UNSUBSCRIBE INFO ***

The easiest way to unsubscribe is to visit 
, and click 'Unsubscribe'.

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



Updated: lighttpd-1.4.76

2024-04-12 Thread Glenn Strauss
Version 1.4.76-1 of "lighttpd" has been uploaded.

lighttpd is a secure, fast, modular web server with low resource usage

lighttpd 1.4.76:

* detect VU#421644 HTTP/2 CONTINUATION Flood
  * issue trace and send GO_AWAY
  * (lighttpd not vulnerable to attack)

* avoid CVE-2024-3094 xz supply chain attack
  * use 'git archive' to replace 'make dist' to create release tarballs
* remove excess complexity (m4 and autotools) from release process
* now more easily verifiable that sources come from signed git release tag

Note:
  This cygwin lighttpd-1.4.76-1 release requires >= cygwin-3.5.0 to take
  advantage of new support for posix_spawn_file_actions_addfchdir_np().
  As this support is optional, please contact me if this is a hardship
  for those unable to upgrade to cygwin-3.5.0 and I can create a package
  of lighttpd without this feature, whose use merely provides a marginal
  performance improvement for starting CGI programs.

Source: https://git.lighttpd.net/lighttpd/lighttpd1.4.git/
News: https://www.lighttpd.net/
License: BSD 3-clause
  https://git.lighttpd.net/lighttpd/lighttpd1.4/src/branch/master/COPYING
-- 
  *** CYGWIN-ANNOUNCE UNSUBSCRIBE INFO ***

The easiest way to unsubscribe is to visit 
, and click 'Unsubscribe'.

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



Re: Cygwin a bit slow

2024-04-12 Thread J M via Cygwin
Hi,

For me not use AV or disable parts is not an option...

Then, if AV is inspecting the CreateProcess, these processes can be known
the path of these process?

Ex, I launch grep. One AV process can discern the path of these process, or
it is impossible to find out if the executable is inside of c:\cygwin64
directory and discard and/or not catch the event, and then inform to the AV
enterprises howto to do these tasks?

I did the following tests with Avast AV:

With all shields stopped or all shields up, same result, one more time that
other:

Launch multiple while true with echo and grep by example and sleep to
results.

In all cases, cpu very high and memory progressively up and up until
windows crash memory exhausted.

The AVs not known howto discern this or it is impossible discern this?

Regards

El jue., 11 abr. 2024 1:17, Sam Edge via Cygwin 
escribió:

> On 10/04/2024 11:34, Christian Franke via Cygwin wrote:
> > J M via Cygwin wrote:
> >> ...
> >>
> >> Specifically for this problem, I have investigated the problem and can
> be
> >> related to pipes and antivirus.
> >>
> >> Specifically
> >> while true
> >> do
> >> echo ABC | grep AAA
> >> done
> >>
> >> It makes the cpu of that antivirus go up.
> >
> > This is as expected because malware scanners hook into Win32 API's
> > CreateProcess*() calls which are also used by the fork()/exec()
> > emulation of Cygwin. Each run of 'grep' above uses at least two
> > CreateProcess*() calls.
>
> This is very true and depends greatly on the AV being used. I find Trend
> is particularly bad, even if you exclude all the Cygwin directories and
> directories of files being accessed. Somehow, the way the hooks are
> implemented stalls process creation and file open in ways that Windows
> Defender does not. This is particularly noticeable when using
> Cygwin-based build tools - build times generally increase at least
> 10-fold after installing Trend.
>
> On one job, I wasted a lot of time and client's money collecting logs
> for Trend to analyse to no avail. I think the product is basically very
> badly written. The fact that it creates dozens of processes with
> hundreds of threads just to do AV scanning does not fill me with
> confidence!
>
> Wherever possible, I remove third-party AV from Windows machines and
> install group policy to enforce Windows Defender and malware detection
> in the browser and/or a proxy & the email server instead. Saves a lot of
> CPU cycles. :-)
>
>
> --
> Sam Edge
>
>
> --
> Problem reports:  https://cygwin.com/problems.html
> FAQ:  https://cygwin.com/faq/
> Documentation:https://cygwin.com/docs.html
> Unsubscribe info: https://cygwin.com/ml/#unsubscribe-simple
>

-- 
Problem reports:  https://cygwin.com/problems.html
FAQ:  https://cygwin.com/faq/
Documentation:https://cygwin.com/docs.html
Unsubscribe info: https://cygwin.com/ml/#unsubscribe-simple


Re: Change for the initial installation of Cygwin to set the default terminal terminal 256 color

2024-04-12 Thread Brian Inglis via Cygwin
The Cygwin native terminal emulator `mintty` is supported by Cygwin default 
`ncurses`/`terminfo` installs:


$ TERM=mintty tput colors
256

On 2024-04-12 07:27, Thomas Wolff via Cygwin wrote:

Am 12.04.2024 um 11:18 schrieb Lee via Cygwin:

On Fri, Apr 12, 2024 at 4:05 AM J M  wrote:

Some examples that I view that can do Cygwin better by default:

tput colors
8

echo $TERM
xterm

I made my mintty changes by point & click experimentation - if you
want to make system-wide changes the place to do that is in
/etc/minttyrc
   https://github.com/mintty/mintty/wiki/Tips
   Configuring mintty
   For its configuration, it reads configuration files in this order:
   /etc/minttyrc
   ... etc.

$ grep -i term .minttyrc
Term=xterm-256color

$ tput colors
256

$ echo $TERM
xterm-256color



Note that mintty always supports all modes, including 256 colours and
true-color (TERM=xterm-direct), regardless of the TERM setting or the
$TERM environment value. That value is only used by some applications
(like tput and apparently vim) as an indication which features to use.
Thomas



And if use vim, comparing with one Ubuntu terminal:

I need to set "set mouse-=a" because the copy paste is difficult.
The colors are very bright.
The cursor does not look good when doing a search and moves over the yellow
background text.

What settings would I need to make it look like Ubuntu's vim?

I'd suggest doing a 'man vim' to find out where all the possible
configuration files are & then copy them to your cygwin machine.



El jue., 11 abr. 2024 14:36, J M  escribió:

You can change in the initial install setup of Cygwin to set the default
terminal to 256 color as Ubuntu does?


--
Take care. Thanks, Brian Inglis  Calgary, Alberta, Canada

La perfection est atteinte   Perfection is achieved
non pas lorsqu'il n'y a plus rien à ajouter  not when there is no more to add
mais lorsqu'il n'y a plus rien à retirer but when there is no more to cut
-- Antoine de Saint-Exupéry


--
Problem reports:  https://cygwin.com/problems.html
FAQ:  https://cygwin.com/faq/
Documentation:https://cygwin.com/docs.html
Unsubscribe info: https://cygwin.com/ml/#unsubscribe-simple


Re: Change for the initial installation of Cygwin to set the default terminal terminal 256 color

2024-04-12 Thread Thomas Wolff via Cygwin



Am 12.04.2024 um 11:18 schrieb Lee via Cygwin:

On Fri, Apr 12, 2024 at 4:05 AM J M  wrote:

Some examples that I view that can do Cygwin better by default:

tput colors
8

echo $TERM
xterm

I made my mintty changes by point & click experimentation - if you
want to make system-wide changes the place to do that is in
/etc/minttyrc
   https://github.com/mintty/mintty/wiki/Tips
   Configuring mintty
   For its configuration, it reads configuration files in this order:
   /etc/minttyrc
   ... etc.

$ grep -i term .minttyrc
Term=xterm-256color

$ tput colors
256

$ echo $TERM
xterm-256color

Note that mintty always supports all modes, including 256 colours and
true-color (TERM=xterm-direct), regardless of the TERM setting or the
$TERM environment value. That value is only used by some applications
(like tput and apparently vim) as an indication which features to use.
Thomas




And if use vim, comparing with one Ubuntu terminal:

I need to set "set mouse-=a" because the copy paste is difficult.
The colors are very bright.
The cursor does not look good when doing a search and moves over the yellow
background text.

What settings would I need to make it look like Ubuntu's vim?

I'd suggest doing a 'man vim' to find out where all the possible
configuration files are & then copy them to your cygwin machine.

Regards,
Lee


El jue., 11 abr. 2024 14:36, J M  escribió:


Hi,

You can change in the initial install setup of Cygwin to set the default
terminal to 256 color as Ubuntu does?



--
Problem reports:  https://cygwin.com/problems.html
FAQ:  https://cygwin.com/faq/
Documentation:https://cygwin.com/docs.html
Unsubscribe info: https://cygwin.com/ml/#unsubscribe-simple


Re: Change for the initial installation of Cygwin to set the default terminal terminal 256 color

2024-04-12 Thread Lee via Cygwin
On Fri, Apr 12, 2024 at 4:05 AM J M  wrote:
>
> Some examples that I view that can do Cygwin better by default:
>
> tput colors
> 8
>
> echo $TERM
> xterm

I made my mintty changes by point & click experimentation - if you
want to make system-wide changes the place to do that is in
/etc/minttyrc
  https://github.com/mintty/mintty/wiki/Tips
  Configuring mintty
  For its configuration, it reads configuration files in this order:
  /etc/minttyrc
  ... etc.

$ grep -i term .minttyrc
Term=xterm-256color

$ tput colors
256

$ echo $TERM
xterm-256color


> And if use vim, comparing with one Ubuntu terminal:
>
> I need to set "set mouse-=a" because the copy paste is difficult.
> The colors are very bright.
> The cursor does not look good when doing a search and moves over the yellow
> background text.
>
> What settings would I need to make it look like Ubuntu's vim?

I'd suggest doing a 'man vim' to find out where all the possible
configuration files are & then copy them to your cygwin machine.

Regards,
Lee

> El jue., 11 abr. 2024 14:36, J M  escribió:
>
> > Hi,
> >
> > You can change in the initial install setup of Cygwin to set the default
> > terminal to 256 color as Ubuntu does?

-- 
Problem reports:  https://cygwin.com/problems.html
FAQ:  https://cygwin.com/faq/
Documentation:https://cygwin.com/docs.html
Unsubscribe info: https://cygwin.com/ml/#unsubscribe-simple


Re: Change for the initial installation of Cygwin to set the default terminal terminal 256 color

2024-04-12 Thread J M via Cygwin
Some examples that I view that can do Cygwin better by default:

tput colors
8

echo $TERM
xterm

And if use vim, comparing with one Ubuntu terminal:

I need to set "set mouse-=a" because the copy paste is difficult.
The colors are very bright.
The cursor does not look good when doing a search and moves over the yellow
background text.

What settings would I need to make it look like Ubuntu's vim?

I don't know if I can put screenshots to explain it better.

Regards


El jue., 11 abr. 2024 14:36, J M  escribió:

> Hi,
>
> You can change in the initial install setup of Cygwin to set the default
> terminal to 256 color as Ubuntu does?
>
> Regards
>
>
>

-- 
Problem reports:  https://cygwin.com/problems.html
FAQ:  https://cygwin.com/faq/
Documentation:https://cygwin.com/docs.html
Unsubscribe info: https://cygwin.com/ml/#unsubscribe-simple