Re: network trace capturing tool in cygwin
Andrey Repin, on Tuesday, June 18, 2019 02:09 PM, wrote... > If that software is required for your work, they have no other way than to let > you use it. > If they actively deny you the working environment, find a better job. That's the easy way out. ;-) Thanks. josé -- Problem reports: http://cygwin.com/problems.html FAQ: http://cygwin.com/faq/ Documentation: http://cygwin.com/docs.html Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple
Re: network trace capturing tool in cygwin
Greetings, Jose Isaias Cabrera! > Andrey Repin, on Tuesday, June 18, 2019 11:30 AM, wrote... >> Just download Wireshark from https://www.wireshark.org/ > That's the problem. That is not allowed. :-( I need to have the CEO sign > for me to get that software here. I have wireshark at home, but at work, > it's not allowed. They are very picky about installing software in the > system. That is the reason why I was looking for the old tcpdump. Thanks. If that software is required for your work, they have no other way than to let you use it. If they actively deny you the working environment, find a better job. -- With best regards, Andrey Repin Tuesday, June 18, 2019 21:08:17 Sorry for my terrible english... -- Problem reports: http://cygwin.com/problems.html FAQ: http://cygwin.com/faq/ Documentation: http://cygwin.com/docs.html Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple
Re: Windowless Perl
On 18/06/2019 16:27, Andrey Repin wrote: On 2019/06/10 13:12, Chris Wagner wrote: I didn't know about run, thanks for the tip. However when I use it to launch something from the Start Menu Run command, it still pops open a terminal window of some kind for a fraction of a second. I'm on Windows 7. Windows has a flag set in each EXE as to whether or not it is a console or GUI program. There are tools that can set the flag in a given EXE file. It's not a flag, it's an exported function. If a program exports winmain(), it's a gui program, if it exports main(), it's a console program. No. It really is a flag. See https://docs.microsoft.com/en-us/windows/desktop/debug/pe-format#windows-subsystem You are describing the behaviour of (recent versions of) the Microsoft linker, which guesses the default value of this flag based on what symbols are defined See https://docs.microsoft.com/en-us/cpp/build/reference/entry-entry-point-symbol, specifically the sentence "If the /DLL or /SUBSYSTEM option is not specified, the linker selects a subsystem and entry point depending on whether main or WinMain is defined." -- Problem reports: http://cygwin.com/problems.html FAQ: http://cygwin.com/faq/ Documentation: http://cygwin.com/docs.html Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple
Re: Moving packages between arch and noarch
Jon Turney writes: > I recently deployed a calm update which makes this process (and it's > reverse, when a previously noarch package becomes archful) no longer > require any manual steps. > > So, going forward, you may build each version of a package with > ARCH=noarch and upload to noarch/, or without, and upload to x86/ and > x86_64/. Thanks, that should earn you a couple gold stars! Andrew? Regards, Achim. -- +<[Q+ Matrix-12 WAVE#46+305 Neuron microQkb Andromeda XTk Blofeld]>+ SD adaptation for Waldorf rackAttack V1.04R1: http://Synth.Stromeko.net/Downloads.html#WaldorfSDada
package cygwin-d-... case sensitivity problems --
The cygwin-doc-... package has several problems in at least the /usr/share/man/man3 directory where multiple file names differ only in case, i.e., the tar file contains, in this order, usr/share/man/man3/jN.3.gz usr/share/man/man3/jn.3.gz The jN.3.gz file contains the roff text and the jn.3.gz file contains a roff .so directive pointing at jN.3. The file that ends up in man3 is jn.3.gz and jN.3.gz disappears. The simplest solution would be to just remove jn.3.gz and similar .so files from the tarball. This would at least allow the roff text files to exist. -- Thanks, --Paul Townsend FMI - where was the tarball created? It certainly was not on a computer with Windows and case insensitivity. -- Problem reports: http://cygwin.com/problems.html FAQ: http://cygwin.com/faq/ Documentation: http://cygwin.com/docs.html Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple
Re: network trace capturing tool in cygwin
Andrey Repin, on Tuesday, June 18, 2019 11:30 AM, wrote... > Just download Wireshark from https://www.wireshark.org/ That's the problem. That is not allowed. :-( I need to have the CEO sign for me to get that software here. I have wireshark at home, but at work, it's not allowed. They are very picky about installing software in the system. That is the reason why I was looking for the old tcpdump. Thanks. josé -- Problem reports: http://cygwin.com/problems.html FAQ: http://cygwin.com/faq/ Documentation: http://cygwin.com/docs.html Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple
Re: [ANNOUNCEMENT] tcsh 6.21.00-1
Greywolf, on Monday, June 17, 2019 10:27 PM, wrote... > [ksh, on the other hand, is welcome to fall off the face of the earth at any > unannounced moment...] Hah. I think I used ksh once in a goverment facility on some obcure SunOS environment. I went to fix a printer driver and I got stuck with ksh and ed. No vi, no emacs, no csh, no sh. Nothing. It was rough... Thanks for listening. How much I owe? josé -- Problem reports: http://cygwin.com/problems.html FAQ: http://cygwin.com/faq/ Documentation: http://cygwin.com/docs.html Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple
Bug in libX11 or something near ?
Hello Cygwin list ! I'm using Cygwin/X and identified a critical bug using some piece of software. I don't really know where to begin, but I'm able to crash some applications via the application's menu, only with Cygwin/X (no crash with Xming, and no crash under any Linux distributions). For information, It goes through VirtualGL. I'll give the example on how to reproduce it with a free software : Paraview (under linux). So you open Paraview, then clic on "View" > show the "Toolbars" submenu, then you move your mouse directly on the "Sources" or "Edit" menu, then it crashes immediately. The only error message in the linux shell (from where it was launched) is "paraview: Fatal IO error: client killed". I got those lines in the XWin.0.log file : SetupSysMenu: GetSystemMenu() failed for HWND 0x130746 winTopLevelWindowProc - WM_DESTROY - WM_WM_KILL I'm on the last available libX11, libxcb1 etc . If you have any idea, thanks :) Philippe -- Problem reports: http://cygwin.com/problems.html FAQ: http://cygwin.com/faq/ Documentation: http://cygwin.com/docs.html Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple
Re: network trace capturing tool in cygwin
Greetings, Jose Isaias Cabrera! > I have not done it in a while, but back in the day there used to be a tool > called tcpdump. I have searched for this on the packages site[1] and I can > not find anything to capture a tpcip network trace in cygwin. Say it is not > so. Are there any tools to capture simple tcpip local network traces in the > actual x86 cygwin snapshots? If so, are there any spots where I can > download and build tcpdump or any tool like that one? Thanks. Just download Wireshark from https://www.wireshark.org/ -- With best regards, Andrey Repin Tuesday, June 18, 2019 18:29:22 Sorry for my terrible english... -- Problem reports: http://cygwin.com/problems.html FAQ: http://cygwin.com/faq/ Documentation: http://cygwin.com/docs.html Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple
Re: Windowless Perl
Greetings, L A Walsh! > On 2019/06/10 13:12, Chris Wagner wrote: >> I didn't know about run, thanks for the tip. However when I use it to >> launch something from the Start Menu Run command, it still pops open a >> terminal window of some kind for a fraction of a second. I'm on Windows >> 7. >> > Windows has a flag set in each EXE as to whether or not it is a console > or GUI program. There are tools that can set the flag in a given EXE file. It's not a flag, it's an exported function. If a program exports winmain(), it's a gui program, if it exports main(), it's a console program. > Perhaps that's similar to the util that Bill Stewart is talking about, > dunno. -- With best regards, Andrey Repin Tuesday, June 18, 2019 18:26:18 Sorry for my terrible english... -- Problem reports: http://cygwin.com/problems.html FAQ: http://cygwin.com/faq/ Documentation: http://cygwin.com/docs.html Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple
Re: lrzip-0.631-1: pthread_createResource temporarily unavailable
I tried the same, but on a local (NTFS) volume and there it completed with no error. Will do some more tests and report... On Sun, 16 Jun 2019 at 22:05, David Balažic wrote: > > Hi! > > Using cygwin64 with latest updates, I got this error after running > lrzip (for hours): > > > $ lrzip -v sda.2019-apr-01.local > The following options are in effect for this COMPRESSION. > Threading is ENABLED. Number of CPUs detected: 4 > Detected 17168990208 bytes ram > Compression level 7 > Nice Value: 19 > Show Progress > Verbose > Temporary Directory set as: /tmp/ > Compression mode is: LZMA. LZO Compressibility testing enabled > Heuristically Computed Compression Window: 109 = 10900MB > Output filename is: sda.2019-apr-01.local.lrz > Warning, unable to set permissions on sda.2019-apr-01.local.lrz > File size: 128035676160 > Will take 12 passes > Beginning rzip pre-processing phase > Beginning rzip pre-processing phase > Beginning rzip pre-processing phase > Beginning rzip pre-processing phase > Beginning rzip pre-processing phase > Beginning rzip pre-processing phase > Beginning rzip pre-processing phase > Beginning rzip pre-processing phase > Beginning rzip pre-processing phase > pthread_createResource temporarily unavailable > Fatal error - exiting > > There is a created file with size 2640192 and name > sda.2019-apr-01.local.lrz in the same folder, after the crash. > > Googling that error line find only one case: > https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=623745 > It is from year 2011 and is supposedly patched. > > The $PWD is /cygdrive/z/tmp which is a CIFS/SMB mount from a my NAS. > > Regards, > David -- Problem reports: http://cygwin.com/problems.html FAQ: http://cygwin.com/faq/ Documentation: http://cygwin.com/docs.html Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple
