Re: BUG: exec format error: emacs
I have now solved the problem by explicitly removing /usr/bin/emacs before re-installing it using Cygwin Setup. Now it indeed became a symlink (to /etc/alternatives/emacs). Ronald On Fri, Jan 17, 2020, at 17:16, Ken Brown wrote: > On 1/17/2020 10:33 AM, Ronald Fischer wrote: > > When trying to run `emacs`, I get > > > > (on zsh) : zsh: exec format error: emacs > > (on bash): bash: /usr/bin/emacs: cannot execute binary file: Exec format > > error > > Are you sure Cygwin's emacs is the first one in your path? Cygwin's > /usr/bin/emacs should be a symlink: > > $ ls -l /usr/bin/emacs > lrwxrwxrwx 1 kbrown-admin None 23 2019-03-21 18:11 /usr/bin/emacs -> > /etc/alternatives/emacs* > > Ken > > -- > 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 > > -- 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: BUG: exec format error: emacs
On Fri, Jan 17, 2020, at 17:16, Ken Brown wrote: > On 1/17/2020 10:33 AM, Ronald Fischer wrote: > > When trying to run `emacs`, I get > > > > (on zsh) : zsh: exec format error: emacs > > (on bash): bash: /usr/bin/emacs: cannot execute binary file: Exec format > > error > > Are you sure Cygwin's emacs is the first one in your path? Well, at least you can see from the error message that /usr/bin/emacs is going to be executed. > Cygwin's > /usr/bin/emacs should be a symlink: Actually, this is not the case: $ ls -l /usr/bin/emacs -rwxrwx---+ 1 FISRONA Domain Users 60 Apr 26 2019 /usr/bin/emacs $ stat /usr/bin/emacs File: /usr/bin/emacs Size: 60 Blocks: 1 IO Block: 65536 regular file Device: 38d54b25h/953502501dInode: 1407374883785092 Links: 1 Access: (0770/-rwxrwx---) Uid: (3672028/ FISRONA) Gid: (1049089/Domain Users) Access: 2019-06-03 12:34:56.255711900 +0200 Modify: 2019-04-26 20:48:58.0 +0200 Change: 2019-06-03 12:34:56.255711900 +0200 Birth: 2019-06-03 12:34:56.255711900 +0200 Two things I find of interest here: Although I have installed the new version using Cygwin's set-up program just a couple of days ago, the modify time goes back to 2019. And the size is too small! Ronald -- 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: Cygwin/X does not seem to work on Windows 10
> I pinned the Cygwin/X "XWin Server" Start Menu item to the taskbar. > When I click that, I get "Cygwin/X Server 0:0" and "X applications menu on :0" > icons in the systray. When I start it via the "XWin Server" entry in the Start Menu - which I have discovered just now, since you mentioned it, I do not get anything in the systray. However, when I use the FVWM entry in the Start Menu, I get a maximized window inside which fvwm is running, and inside this, I can - from the context menu - start among others xterm etc. Ronald -- 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: Cygwin/X does not seem to work on Windows 10
On Tue, Jun 4, 2019, at 15:18, Massimo Balestra wrote: > > > - Installed all the packages, as described in > > https://x.cygwin.com/docs/ug/setup.html > > - Started XLaunch > > - Selected "Multiple Window" and "Start no client", to start the X Server > > I don't know XLaunch but for the Xwindows I prepared a shorcut that run: > > D:\cygwin64\bin\XWin.exe -multiwindow -listen tcp This is interesting, because the way to use XLaunch is the one which is described on the Cygwin/X website. Anyway, I did I started it from the Windows command prompt, as you suggested (without the -listen option because I don't plan to use ssh), and when I then start my DISPLAY=:0.0 xterm & I get the error message xterm: cannot load font "-Misc-Fixed-bold-R-*-*-13-120-75-75-C-120-ISO10646-1" which means that at least the DISPLAY is not a problem anymore. Don't know why it can't find a suitable font, since I have installed plenty of fonts from the Cygwin X11 category. What still does not work is the "X-icon" in the notification area. As a further test, I started DISPLAY=:0.0 xeyes & because this for sure doesn't need any font. This worked too. Ronald -- 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
Cygwin/X does not seem to work on Windows 10
What I did: - Installed all the packages, as described in https://x.cygwin.com/docs/ug/setup.html - Started XLaunch - Selected "Multiple Window" and "Start no client", to start the X Server - Clicked on "Fertig stellen" (= finish). - Using mintty, I started a cygwin shell (zsh). - Inside this shell, I tried a xterm & which, not surprisingly, resulted into: xterm: Xt error: Can't open display: xterm: DISPLAY is not set and then a DISPLAY=:0.0 xterm & which also produced an error message: xterm: Xt error: Can't open display: :0.0 Interestingly, there is an X-Icon in the notification area, and when I hover over it, the tooltip says "Cygwin/X Servre: 0.0", but when I right-click on this icon, no context menu appears. When I do a double-LEFT-click on this icon, the icon disappears completely. I then opened the Task Manager, but could not find any process where the name hinted that an X server would be running. Ronald -- 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: Bug: No json support anymore in Ruby 2.3.6
Hi Ken. I see your point For me, the foremost issue is to confirm, whether this is indeed a bug in the Cygwin package for Ruby, or not, and my posting on the mailing list was mainly intended to draw attention from the Ruby package maintainers (although other comments are, of course, also highly preciated, and in particular without your comment, I would not have known about the concept of default gems). I have to maintain a consistent state of our application accross several sites (Cygwin, Linux), and so far, only the new 2.3.6 Cygwin version, which I installed tentaively, has this problem. The previous version was correct in this respect, and all those versions I'm aware of, which run on Linux, also come with json built in. For the time being, we just avoid updating the Ruby version on Cygwin (because it seems to be nearly impossible to go back to the previous version once you have updated a package). BTW, the definition of "default gems" provided on the stdgems site also includes the sentence that "one can not REMOVE them" (because they are bundled with Ruby), so I think it is even risky to deliver an explicit version of this gem as part of our application, which might then be in conflict with those installation which do contain the json gem in a different version. Furthermore, explicitly installing the json gem requires also to download the C compiler and the Cygwin library bindings for Ruby, because json contains C code. I rather would prefer not opening this can of worms Ronald On Tue, Nov 20, 2018, at 17:26, Ken Brown wrote: > On 11/20/2018 10:39 AM, Ronald Fischer wrote: > > Hi Ken, > > > > actually, the page regarding the gem list for the Ruby version in question > > (the one we have at Cygwin) is > > > > https://stdgems.org/2.3.6/ > > > > but this page too lists json as "default gem". > > > > The page https://stdgems.org/ then defines this term as: > > > > "Default gems: These gems are part of Ruby and you can always require them > > directly" > > > > So from this I would conclude that json (and the other default gems) should > > be part of the Ruby installation, since "they are part of Ruby". If you > > disagree with my interpretation, please explain where I undersood the text > > in a wrong way. > > > > BTW, I think that my viewpoint is also supported by > > > > https://ruby-doc.org/stdlib-2.3.6/ > > > > which says that the packages listed on this page are found in the /lib > > directory of Ruby. > > > > But even if I go along with your interpretation of the text, in that the > > default gems are delivered as a separated package, they should be available > > at least on the Cygwin server, and be installable from there, but I did a > > search for "ruby-default" and could not get a match. > > I was just trying to tell you how to solve the problem. I wasn't offering an > opinion about ruby packaging or which gems should be installed by default. > > Ken > ТÒÐÐ¥&ö&ÆVÒ÷'G3¢‡GG¢òö7–wv–âæ6öÒ÷&ö&ÆV×2æ‡FÖÀФd¢‡GG¢òö7–wv–âæ6öÒöfðÐ > ¤Fö7VÖVçFF–ö㢇GG¢òö7–wv–âæ6öÒöFö72æ‡FÖÀÐ¥Vç7V'67&––æfó¢‡GG¢òö7–wv– > âæ6öÒöÖÂò7Vç7V'67&–×6–×ÆPÐ Ð -- 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: Bug: No json support anymore in Ruby 2.3.6
Hi Ken, actually, the page regarding the gem list for the Ruby version in question (the one we have at Cygwin) is https://stdgems.org/2.3.6/ but this page too lists json as "default gem". The page https://stdgems.org/ then defines this term as: "Default gems: These gems are part of Ruby and you can always require them directly" So from this I would conclude that json (and the other default gems) should be part of the Ruby installation, since "they are part of Ruby". If you disagree with my interpretation, please explain where I undersood the text in a wrong way. BTW, I think that my viewpoint is also supported by https://ruby-doc.org/stdlib-2.3.6/ which says that the packages listed on this page are found in the /lib directory of Ruby. But even if I go along with your interpretation of the text, in that the default gems are delivered as a separated package, they should be available at least on the Cygwin server, and be installable from there, but I did a search for "ruby-default" and could not get a match. Ronald On Tue, Nov 20, 2018, at 15:00, Brian Inglis wrote: > On 2018-11-20 06:13, Ken Brown wrote: > > On 11/20/2018 3:41 AM, Ronald Fischer wrote: > >> Since I updated Ruby to 2.3.6, the standard library json is missing: > >> ruby -e 'require "json"' > >> /usr/share/rubygems/rubygems/core_ext/kernel_require.rb:55:in `require': > >> cannot load such file -- json (LoadError) > >> from > >> /usr/share/rubygems/rubygems/core_ext/kernel_require.rb:55:in `require' > >> from -e:1:in `' > > Install the ruby-json package. > > By recent ruby standards, ruby should depend on and install ruby-stdgems, > which > should install ruby-libraries, ruby-default-gems, and ruby-bundled-gems, where > the latter two should depend on and install the lists of default and bundled > standard library gems, which should include ruby-json and other standard > library > gems. > > Packages for ruby-stdgems, ruby-default-gems, and ruby-bundled-gems could be > dummy (virtual) packages (like _obsolete packages) to define the generic and > version dependent gem lists, to make version dependent changes easier. > > See https://stdgems.org/{libraries,default_gems,bundled_gems}.json > > -- > Take care. Thanks, Brian Inglis, Calgary, Alberta, Canada > > This email may be disturbing to some readers as it contains > too much technical detail. Reader discretion is advised. > > -- > 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 > -- 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: Bug: No json support anymore in Ruby 2.3.6
For modules which, according to the Ruby-Docs, are supposed to be in the stdlib, no Gem installation must be necessary. With other words: A Ruby application which only uses features from the stdlib, should run on any other Ruby installation (of compatible version) without the requirement of installing a Gem. On Tue, Nov 20, 2018, at 14:13, Ken Brown wrote: > On 11/20/2018 3:41 AM, Ronald Fischer wrote: > > Since I updated Ruby to 2.3.6, the standard library json is missing: > > > > ruby -e 'require "json"' > > /usr/share/rubygems/rubygems/core_ext/kernel_require.rb:55:in `require': > > cannot load such file -- json (LoadError) > > from /usr/share/rubygems/rubygems/core_ext/kernel_require.rb:55:in > > `require' > > from -e:1:in `' > > Install the ruby-json package. > > Ken > BKCBи[H\мЮЫиоYнк[ллKми[\Ы[BTNЫиоYнк[ллKй\KУBин[Y[] > [лЫиоYнк[ллKйимЫ[B[нXимXH[ЮЫиоYнк[ллKл[ > Шн[нXимXK\к[\CBB -- 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: No json support anymore in Ruby 2.3.6
Since I updated Ruby to 2.3.6, the standard library json is missing: ruby -e 'require "json"' /usr/share/rubygems/rubygems/core_ext/kernel_require.rb:55:in `require': cannot load such file -- json (LoadError) from /usr/share/rubygems/rubygems/core_ext/kernel_require.rb:55:in `require' from -e:1:in `' The other standard libs which I tried, are present, for example: ruby -e 'require "yaml"; require "set"' (no error here). Ronald cygcheck.out Description: Binary data -- 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
Ejecting a USB drive using Cygwin (sync)?
I'm looking for a command, which would allow me from a shell script to prepare the removal of a USB device (stick, external hard drive etc.). With other words, after issuing the command, I should be able to physically remove the USB device. Can the `sync` command be used, for instance sync -f /cygdrive/e assuming that the USB device is on drive E:? The man page of *sync* is a bit vague in this respect. Or is there another Cygwin command which can be used for this purpose? Ronald -- 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: git can not access remote repository anymore after cygwin+git update
On Thu, Oct 19, 2017, at 14:28, Marco Atzeri wrote: > On 19/10/2017 13:38, Ronald Fischer wrote: > > I'm using 64 Bit Cygwin on Windows 7. After upgrading Git to version > > 2.14.2 (I think I had 2.13 or 2.12 before), git can not access our > > repository anymore. Commands such as "git pull" or "git push" result > > into the error > > > > > > fatal: Could not read from remote repository. > > Please make sure you have the correct access rights > > and the repository exists. > it seems your cygwin package was not update correctly: > > cygwin 2.9.0-3 OK > > but > > 3238k 2017/04/01 C:\cygwin64\bin\cygwin1.dll - os=4.0 img=0.0 sys=5.2 >"cygwin1.dll" v0.0 ts=2017-04-01 20:47 > Cygwin DLL version info: > DLL version: 2.8.0 > > May be is not the root cause but you should reinstall the package > with no running process. This was it! Thanks a lot!!! Ronald -- 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
git can not access remote repository anymore after cygwin+git update
I'm using 64 Bit Cygwin on Windows 7. After upgrading Git to version 2.14.2 (I think I had 2.13 or 2.12 before), git can not access our repository anymore. Commands such as "git pull" or "git push" result into the error fatal: Could not read from remote repository. Please make sure you have the correct access rights and the repository exists. Since I can't go back to the previous version (I didn't find any Git mirror which has 2.12 or 2.13), I have now intalled Git for Windows (https://git-scm.com/) along Cygwin git, also in Version 2.14.2. With this, I don't have any problems (I have installed it in a separate directory, which is not in my PATH, and I'm using git-scm for operations which access our remote repository, and Cygwin git for everything else). This works fine so far, but I still wonder what has changed in git so that this is broken. Of course it could also be that the permission error is not related to the new git version, but to some changes in the Cygwin core libraries, because they had also been updated. Note that there is no "real" access problem from the Windows side, because if it were so, Git for Windows would also report an error. Any idea what's wrong here? Ronald cygcheck.out Description: Binary data -- 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: confirm unsubscribe from cygwin@cygwin.com
On Fri, Aug 18, 2017, at 10:21, cygwin-h...@cygwin.com wrote: > Hi! This is the ezmlm program. I'm managing the > cygwin@cygwin.com mailing list. > > To confirm that you would like > >yn...@mm.st > > removed from the cygwin mailing list, please send an empty reply > to this address: > >cygwin-uc.1503044504.lmgeeelabmfmbholblcj-ynnor=mm...@cygwin.com > > Usually, this happens when you just hit the "reply" button. > If this does not work, simply copy the address and paste it into > the "To:" field of a new message. > > I haven't checked whether your address is currently on the mailing list. > To see what address you used to subscribe, look at the messages you are > receiving from the mailing list. Each message has your address hidden > inside its return path; for example, m...@xdd.ff.com receives messages > with return path:> --- Administrative commands for the cygwin list --- > > I can handle administrative requests automatically. Please > DO NOT SEND THEM TO THE LIST ADDRESS! If you do, I will not > see them and other subscribers will be annoyed. Instead, send > your message to the correct command address: > > > To subscribe to the list, send a message to: > > > To remove your address from the list, send a message to: > > > Send mail to the following for info and FAQ for this list: > > > > Similar addresses exist for the digest list: > > > > You can start a subscription for an alternate address, > for example "john@host.domain", just add a hyphen and your > address (with '=' instead of '@') after the command word: >
Re: bash pipe fails in script with subshell/loop cmbination
> > TWO - this fails, apparently (warning: my guess) at the pipe > $ for j in 1 2;do echo $j $(echo hello | cat);done > 1 > 2 This works for me: $ for j in 1 2;do echo $j $(echo hello | cat);done 1 hello 2 hello I have: GNU bash, version 4.4.12(3)-release (x86_64-unknown-cygwin) Ronald -- 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
Ruby ri does not display core docs - is it a bug or do I miss a package?
I have installed Ruby and the Ruby-doc package (and also some other doc packages related to Ruby gems). However, ri does not work for core packages. Example: $ ri String = String < Object (from gem bigdecimal-1.3.2) -- = Instance methods: to_d (from gem rake-11.3.0) -- = Instance methods: ext, pathmap, pathmap_explode, pathmap_partial, pathmap_replace We can see that String related methods from the gems are displayed, but not what is in the core package. Similarily: $ ri 'String#length' Nothing known about String#length Is this a bug? cygcheck.out Description: Binary data -- 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
Ruby ri does not display core docs - is it a bug or do I miss a package?
I have installed Ruby and the Ruby-doc package (and also some other doc packages related to Ruby gems). However, ri does not work for core packages. Example: $ ri String = String < Object (from gem bigdecimal-1.3.2) -- = Instance methods: to_d (from gem rake-11.3.0) -- = Instance methods: ext, pathmap, pathmap_explode, pathmap_partial, pathmap_replace We can see that String related methods from the gems are displayed, but not what is in the core package. Similarily: $ ri 'String#length' Nothing known about String#length Is this a bug? cygcheck.out Description: Binary data -- 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 zsh and bash with builtin ls when colorization is used and the filename starts with a drive letter
I have in my .zshrc: alias "ls=ls --color=auto" export LS_COLORS="di=1;4;33:*rc=7:*.rb=32:*.irbrc=32:*.sh=36:*.zsh=36:*.bak=2:*~=2:*.log=34;*.txt=34:ex=1" Now compare these two commands and their output: $ ls -l C:/cygwin64/home/fisrona/gitwrk/vp5/manualtest/logs/manualtest_222.log -rw-r--r-- 1 fisrona Domain Users 5771150 Aug 1 16:33 xt=34mC:/cygwin64/home/fisrona/gitwrk/vp5/manualtest/logs/manualtest_222.log $ command ls -l C:/cygwin64/home/fisrona/gitwrk/vp5/manualtest/logs/manualtest_222.log -rw-r--r-- 1 fisrona Domain Users 5771150 Aug 1 16:33 C:/cygwin64/home/fisrona/gitwrk/vp5/manualtest/logs/manualtest_222.log The output in both cases is printed in the same way, but as you can see, the zsh builtin ls displays a strange "xt=34m" in front of the file path, while /usr/bin/ls does not. Further investigation shows that this happens only if the file path starts with a drive letter (here: C:) and the -l option is requested. When setting --color=always and piping the output into a hex viewer, I can see that the what is getting prefixed to the file path is: 020 r o n a D o m a i n U s e r 6f72616e44206d6f6961206e73557265 040 s 5 7 7 1 1 5 0 A u g 1 20733735313735312030754120673120 060 1 6 : 3 3 033 [ 0 m 033 [ 3 4 ; 31203a361b20305b1b6d335b3b34 100 * . t x t = 3 4 m C : / c y g w 2e2a78743d743433436d2f3a79637767 120 i n 6 4 / h o m e / f i s r o n 6e693436682f6d6f2f65696672736e6f We can see here, that part of the text inside the LS_COLORS variable (i.e. ;.txt=34m) has been placed in the output. It is interesting that this happens only if we have a drive letter. If I write ls -l /cygdrive/c/cygwin64/home/fisrona/gitwrk/vp5/manualtest/logs/manualtest_222.log instead, the error does not occur. This is with zsh 5.3, which is what I'm usually using. For curiosity, I tested the same with bash, and the bash ls builtin command seems to behave the same as zsh. cygcheck.out Description: Binary data -- 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: confirm subscribe to cygwin@cygwin.com
On Tue, Aug 1, 2017, at 09:59, cygwin-h...@cygwin.com wrote: > Hi! This is the ezmlm program. I'm managing the > cygwin@cygwin.com mailing list. > > To confirm that you would like > >yn...@mm.st > > added to the cygwin mailing list, please send > an empty reply to this address: > >cygwin-sc.1501574340.cbnkklbpjoijcnnolmal-ynnor=mm...@cygwin.com > > Usually, this happens when you just hit the "reply" button. > If this does not work, simply copy the address and paste it into > the "To:" field of a new message. > > This confirmation serves two purposes. First, it verifies that I am able > to get mail through to you. Second, it protects you in case someone > forges a subscription request in your name. > > > --- Administrative commands for the cygwin list --- > > I can handle administrative requests automatically. Please > DO NOT SEND THEM TO THE LIST ADDRESS! If you do, I will not > see them and other subscribers will be annoyed. Instead, send > your message to the correct command address: > > > To subscribe to the list, send a message to: >> > To remove your address from the list, send a message to: > > > Send mail to the following for info and FAQ for this list: > > > > Similar addresses exist for the digest list: > > > > You can start a subscription for an alternate address, > for example "john@host.domain", just add a hyphen and your > address (with '=' instead of '@') after the command word: >
Re: Killing-Process woes
> > The background processes are actually (zsh-) scripts, which do some > > setup (basically setting various environment variables), and then invoke > > a (Cygwin-)Ruby program which does the "real work". The program is > > executed by something like > > > > ruby myprog.rb > > > > (Note that this Ruby program is NOT invoked in background). > > > > When my SIGINT trap is entered, I can see from ps indeed the > > relationship between the processes involved, for instance > > > > 1085292966224 10536 cons33672028 08:05:10 > > /usr/bin/ruby > > 929662246224 11236 cons33672028 08:05:10 > > /usr/bin/zsh > > > > The PID of my background process - the zsh wrapper - in this concrete > > case is 9296, and we can see that this is the parent of the Ruby > > process, 10852. The problem is that if I just kill 9296, the Ruby > > process keeps running, orphaned: > > > > 10852 16224 10536 cons33672028 08:05:10 > > /usr/bin/ruby > > > > I've found on Stackoverflow the suggestion to treat this as a process > > group and use negative PIDs. I tried this too, but it didn't work. Here > > is a similar example: > > > > Not implemented as you found out below. But I don't know that the > negative process number is in use anywhere. Are you sure it wasn't a > signal number as a option to kill? No, the article refered to a process group (and this indeed would be done by negative PIDs), but as I said, this didn't work anyway. > Perhaps use the -f --force switch might help. No, doesn't help either. For the time being, I have reverted to analyzing the output of ps. It is pretty tedious: # Get the PID of the shell script local wrapper_proc=$! # Give the wrapper some time to start the Ruby process below. Without this, the # Ruby process would not be visible yet. sleep 3 # Find out the PID of the child process of the wrapper local sub_pid=$(ps |grep -oE "^ *[0-9]+ *$wrapper_proc "|awk ' {print $1}') # Sanity check if [[ $sub_pid =~ ^[0-9]+$ ]] then # Add this to the array of these child processes additional_pids+=$sub_pid else echo "Info: Could not extract VP pid from '$sub_pid'" fi Inside my SIGINT trap, I do not only kill the processes found via $jobstates, but also the processes collected in $additional_pids. An awful solution, and one which is not easy to maintain and may break! Ronald -- 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: Bug: grep behaves incorrectly under the locale C.UTF-8, if a file contains Umlaut characters
> > If I grep the file using, say, > > > $ grep . X >Y > > > (i.e. select every non-empty line and write the result to Y), this works > > fine, if LANG is set to one of: UTF-8, C, C.de_DE, C.en_EN, en_EN, > > de_DE. > > > However, if LANG is set to C.UTF-8, two things happen: > > > - grep classifies the file as binary file and produces the error message > > "Binary file X matches" > > This is an intended behavior, upstream decision since mid-2015, I recall. Might be, but this still does not explain the issues 1., 2. and 3., which I layed out in detail below. Note that never said that the fact, that grep classifies certain characters as binary, would by itself a bug. Or is the intended behaviour, that with C.UTF-8 (and *only* with this setting), the resulting standard output of grep is interspersed with "Binary file matches" lines? If this is the case, I really would like to se a justification for this decision. > > > - Both the grepped lines (i.e. in our example the non-empty lines) AND > > the error message end up in the standard output (i.e. in file Y). > > > IMO, there are several problems with this: > > > 1. It's hard to see, why an umlaut character makes the file X binary > > under encoding C.UTF-8, but not under encoding UTF-8 or C.en_EN > > > 2. If grep classifies a file as binary, I think the desired behaviour > > would be to NOT produce any output, unless the -a flag has been > > supplied. > > > 3. If grep writes a message "Binary file ... matches", this message > > should go to stderr, not stdout. The stdout is supposed to contain only > > a subset of the input lines. > > Ronald -- 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: grep behaves incorrectly under the locale C.UTF-8, if a file contains Umlaut characters
I have a file X which contains ASCII text, but also in some lines German umlaut characters. The file is classified as: $ file X X: ISO-8859 text, with CRLF line terminators If I grep the file using, say, $ grep . X >Y (i.e. select every non-empty line and write the result to Y), this works fine, if LANG is set to one of: UTF-8, C, C.de_DE, C.en_EN, en_EN, de_DE. However, if LANG is set to C.UTF-8, two things happen: - grep classifies the file as binary file and produces the error message "Binary file X matches" - Both the grepped lines (i.e. in our example the non-empty lines) AND the error message end up in the standard output (i.e. in file Y). IMO, there are several problems with this: 1. It's hard to see, why an umlaut character makes the file X binary under encoding C.UTF-8, but not under encoding UTF-8 or C.en_EN 2. If grep classifies a file as binary, I think the desired behaviour would be to NOT produce any output, unless the -a flag has been supplied. 3. If grep writes a message "Binary file ... matches", this message should go to stderr, not stdout. The stdout is supposed to contain only a subset of the input lines. Ronald cygcheck.out Description: Binary data -- 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
Editors set x-bit (sometimes)
Does anybody have an explanation for the following strange phenomenon? When I create Ruby files (*.rb) with an, the files end up with the x-bit set with some editors, while this does not happen with some other editors. This is annoying, because when I use git to put the file in a repository, and the repository is later read on Linux, the incorrect x-bit is applied there too. The text editors where this happens, do so consistently, as long as the file is below my Ruby HOME directory. It does not happen, if I store the file outside my $HOME, say in c:\tmp. Since a few editors do not show this behaviour, one might blame the way the editor creates the file. However, these text editors were not written with a Cygwin environment in mind, and Windows doesn't have the concept of an "executable bit", and it happens only if I create files below my Cygwin Home, so I think this happens when Cygwin tries to "infer" the x-bit from some other file properties. I am aware that Cygwin has a policy to infer, whether the x-bit should be set or not set. Nevertheless, this does not apply in my case: - The files don't have a #! line - I don't have a file association on Windows which would mark a .rb file as being run by Ruby - My file system is ntfs BTW, my CYGWIN environment variable is set to just 'nodosfilewarning'. I'm using Windows 7 and the 64-bit-version of Cygwin. - Ronald -- 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
zsh bug: Incorrect (misleading) error message in zsh when using rm and drive letter is specified
I observed this: -0-1- ~/exp > rm e:/media/* zsh: sure you want to delete all the files in /home/FISRONA/exp/e:/media [yn]? n We see that zsh is catching the case that I want to rm all files in the specified directory, and warns me about it (note that it is a zsh error message, not a error message from rm), which is fine and expected behaviour (which can be controlled by the zsh option RM_STAR_SILENT). However, the path printed by zsh is wrong: It interprets e:/... as relative path, while it is an absolute path. It seems that zsh is not translating windows pathes using a drive letter to /cygdrive/... pathes in this case. Version information: zsh 5.1.1 (x86_64-unknown-cygwin) Ronald -- 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: SIGINT generated by Control-C, is not delivered in mintty
On Fri, Jul 17, 2015, at 21:03, Thomas Wolff wrote: Am 14.07.2015 um 09:44 schrieb Ronald Fischer: Using Cygwin 64 on Windows 7: In a bash or zsh running inside mintty, pressing Control-C has no effect. In a bash or zsh running in a Windows Console, it works fine. Ronald, can you please clarify on the question: how did you start mintty (desktop shortcut or command line from cygwin console) because that might make a difference. Indeed, it does! When starting it from a desktop shortcut, it works, but when started as a background process, it doesn't. Ronald -- 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: SIGINT generated by Control-C, is not delivered in mintty
Indeed, it does! When starting it from a desktop shortcut, it works, but when started as a background process, it doesn't. Ah, so that is the Cygwin console # i.e. execution of the file Cygwin.bat, located in the Windows Cygwin root. Actually no, though the difference doesn't matter - but for the safe side, here are the gory details: In a cmd.exe Command window (or, to be more precise, in a command window hosted by the Console2 console), I use the command cmd /c c:\cygwin64\bin\zsh -l to start an interactive zsh Shell, and from *this*, I start a Ruby program, and from *this*, a mintty is started in the background. But I can see the effect simpler in this way: Just open a DOS Command Window, and in the command line type c:\cygwin64\bin\zsh -c /usr/bin/mintty and the error can be reproduced. BTW, same effect with bash instead of zsh. -- 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: SIGINT generated by Control-C, is not delivered in mintty
But I can see the effect simpler in this way: Just open a DOS Command Window, and in the command line type c:\cygwin64\bin\zsh -c /usr/bin/mintty and the error can be reproduced. BTW, same effect with bash instead of zsh. Understood. For the moment, invoke mintty through cmd, i.e. put cmd between Ruby and mintty. That should help. The trick is to make mintty NOT interact with a cons. Great! This works Ronald -- 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: SIGINT generated by Control-C, is not delivered in mintty
On Tue, Jul 14, 2015, at 11:27, Achim Gratz wrote: Ronald Fischer ynnor at mm.st writes: Using Cygwin 64 on Windows 7: In a bash or zsh running inside mintty, pressing Control-C has no effect. In a bash or zsh running in a Windows Console, it works fine. This can be verified in two ways: (1) Using 'trap': In the shell, we do a trap 'echo trapped' INT Now whenever we hit Control-C, we expect trapped to be printed on stdout. This is not the case when the shell runs inside mintty. (2) Using 'cat': In the shell, we do a cat which has the effect that cat reads from stdin. A control-C should abort it. Again, this doesn't work when we run inside mintty. WJFFM. Make sure that the stuff in GW (GNUwin?) and Linux64 does not interfer. Also, you have multiple cygwin1.dll on your path (p/nano), fix that and see if it makes any difference. Good point, but did not help: I have removed the GNUwin Utilities and the path to my second cygwin1.dll from my PATH (which is a good idea anyway), verified it, and repeated the test - same result. Next - to be really sure that we don't have any interference - I did a PATH=/usr/bin mintty and inside mintty did a echo $PATH to verify, that I really have only /usr/bin in my PATH, and here too, the same effect - Control-C not delivered. BTW, the last time I worked with mintty (on a different project) - it was about 3 years ago - it worked fine, so I guess the bug sneaked in recently. Ronald -- 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: Possible bug with chere 1.4 when configuring for fish
I've had more time to look around. If you add the following to the file ~/.config/fish/config.fish (create it if you haven't already got one), then things should work as intended: if status --is-login set PATH /usr/local/bin /usr/bin $PATH end Alternatively drop it in the fish global startup file, /usr/share/fish/config.fish. I tried the variant of putting it into the global startup file, it doesn't resolve the problem for me. I'll play around a bit with it as soon as I have time (I'm a first-time user of fish and am busy with other things right now, so this might take some time). Ronald -- Ronald Fischer rona...@eml.cc + If a packet hits a pocket on a socket on a port, + and the bus is interrupted and the interrupt's not caught, + then the socket packet pocket has an error to report. + (cited after Peter van der Linden) -- 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: Possible bug with chere 1.4 when configuring for fish
On Tue, Apr 8, 2014, at 0:35, Dave Kilroy wrote: On 07/04/2014 13:02, Ronald Fischer wrote: I have installed fish 2.1.0. Works fine, when invoking a new fish shell manually. However, when doing a chere -ifcm -t mintty -s fish and invoke the new fish shell from the Windows Explorer context menu, I get plenty of error messages, like this: snip Thanks for the report. I've just checked my x86_64 and x86 installation. Things are working on my installation as I have c:\cygwin\bin on my standard windows path. When I remove it and invoke fish, I get the errors that you highlight. Similarly when echo'ing $PATH under the broken fish, /usr/bin is not one of the entries. Indeed: Once I'm adding the cygwin bin path to my windows system environment, it works, so this is at least a temporary workaround (on the long run, I don't want to have the cygwin path permanently set on this machine). I need to have a play around to see how I can fix this, but I thought cygwin prepended /usr/bin to the path... I don't think cygwin by itself changes the path. It certainly doesn't change the Windows system path (as defined in the Advanced System Settings for Windows). However, when I start a bash shell, /usr/bin is part of the PATH. This happens inside /etc/profile. But this file is not always processed; This depends on how bash is started. You can see the detailed rules in the bash man-page, in the section INVOCATION. My guess is that when doing a chere -2 fish, you start via bash in a way that /etc/profile is not read. As for chere -1 fish, I suspect that this will never work, unless the user has put the Cygwin bin path into his system PATH. Maybe in this case, chere should output a warning message. Ronald -- Ronald Fischer rona...@eml.cc + If a packet hits a pocket on a socket on a port, + and the bus is interrupted and the interrupt's not caught, + then the socket packet pocket has an error to report. + (cited after Peter van der Linden) -- 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
Can not install cron (authorization problem)
I'm on Windows 7 (64Bit), with local admin rights. My first attempt to install the cron services, failed like this: Do you want the cron daemon to run as yourself? (yes/no) yes Error in openPolicy (LsaOpenPolicy returned 0xc022=STATUS_ACCESS_DENIED)! I thought that maybe I have to do this as administrator. I therefore opened a mintty by running it as administrator, and executed cron-config again. This time, indeed, the error message does not occur anymore. However, after entering my user id and Windows password, I got the error message: Do you want the cron daemon to run as yourself? (yes/no) yes Please enter the password for user 'rofischx': Reenter: cygrunsrv: Error installing a service: CreateService: Win32 error 1057: The account name is invalid or does not exist, or the password is invalid for the account name specified. Now I'm absolutely sure that I entered my password correctly (I tried several times, always the same effect), and the user name is also correct. What else could be the problem? BTW, the command 'id' shows: uid=437575(rofischx) gid=10513(Domain Users) groups=10513(Domain Users),0(root),544(Administrators),545(Users) Ronald -- Ronald Fischer rona...@eml.cc + If a packet hits a pocket on a socket on a port, + and the bus is interrupted and the interrupt's not caught, + then the socket packet pocket has an error to report. + (cited after Peter van der Linden) -- 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: Why does nedit complain about these missing fonts?
On Sun, May 20, 2012, at 14:19, Yaakov (Cygwin/X) wrote: On 2012-05-20 05:07, Ronald Fischer wrote: The question remains, why nedit looks at *those* fonts. I'm perfectly happy to specify in the preferences of nedit only those fonts which are actually installed with Xming. However, nedit seems to look at certain fonts, which I certainly have not mentioned in my preferences Fonts are also required for rendering the interface (menus and dialog boxes). True, but this does not apply here (I think), because I when I instruct nedit to use specific fonts (those which are installed on my system) for the interface, nedit indeed uses these fonts, but still displays the error message. Meanwhile I found something in the Cygwin/X FAQs about this problem (I had overlooked it the first time): This seems to be a well known problem with some X applications, and it was recommended to install certain adobe fonts via Cygwin setup. So I run setup again to install the required fonts, and also (via xset) did a refresh of the font path. The problem still persisted. Looking at the installed fonts, I found my fonts being present only in /usr/share/fonts/100dpi and /usr/share/fonts/75dpi as a bunch of gz-files. I'm not sure whether this is correct (i.e. whether the X server is supposed to unpack them on demand), or whether the Cygwin setup script is supposed to do this. I think it is the latter, because when I did a xset fp+ /usr/share/fonts I got the error message xset: bad font path element (#90), possible causes are: Directory does not exist or has wrong permissions Directory missing fonts.dir Incorrect font server address or syntax Could it be that part of the installation is missing on the Cygwin side? In a correct installation, where are these fonts supposed to be stored? Ronald -- Ronald Fischer rona...@eml.cc + If a packet hits a pocket on a socket on a port, + and the bus is interrupted and the interrupt's not caught, + then the socket packet pocket has an error to report. + (cited after Peter van der Linden) -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Problem reports: http://cygwin.com/problems.html Documentation: http://x.cygwin.com/docs/ FAQ: http://x.cygwin.com/docs/faq/
Re: Why does nedit complain about these missing fonts?
On Sun, May 20, 2012, at 14:19, Yaakov (Cygwin/X) wrote: On 2012-05-20 05:07, Ronald Fischer wrote: Fonts are also required for rendering the interface (menus and dialog boxes). Update: Yaakov, I just found out that you were right in your assumption that there *is* at least one part in the nedit user interface which DOES use preset fonts (which can't be changed): It's how the file names are rendered in the open file dialogue. So this indeed explains the warning I get. What still reminds to do is to install the missing fonts properly - see my previous posting to see what I attempted for this task. Ronald -- Ronald Fischer rona...@eml.cc + If a packet hits a pocket on a socket on a port, + and the bus is interrupted and the interrupt's not caught, + then the socket packet pocket has an error to report. + (cited after Peter van der Linden) -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Problem reports: http://cygwin.com/problems.html Documentation: http://x.cygwin.com/docs/ FAQ: http://x.cygwin.com/docs/faq/
Re: Why does nedit complain about these missing fonts?
On Sat, May 19, 2012, at 23:18, Yaakov (Cygwin/X) wrote: On 2012-05-19 05:20, Ronald Fischer wrote: In fact, it is. nedit, like other old Motif (and Xaw) applications, depends on server-side fonts. (Modern GUI toolkits, such as GTK+ and Qt, use client-side fonts via fontconfig or a wrapper thereto.) Therefore, you must install fonts where Xming will find them, and hence this is not an issue per se with nedit or Cygwin/X. I understand, and I'll have a look there! Actually, I thought that fonts are independent of the acutal implementation of the X-Server. I now see that I was wrong. The question remains, why nedit looks at *those* fonts. I'm perfectly happy to specify in the preferences of nedit only those fonts which are actually installed with Xming. However, nedit seems to look at certain fonts, which I certainly have not mentioned in my preferences Ronald -- Ronald Fischer rona...@eml.cc + If a packet hits a pocket on a socket on a port, + and the bus is interrupted and the interrupt's not caught, + then the socket packet pocket has an error to report. + (cited after Peter van der Linden) -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Problem reports: http://cygwin.com/problems.html Documentation: http://x.cygwin.com/docs/ FAQ: http://x.cygwin.com/docs/faq/
Re: Why does nedit complain about these missing fonts?
On Fri, May 18, 2012, at 13:37, Yaakov (Cygwin/X) wrote: On 2012-05-18 07:42, Ronald Fischer wrote: I'm using Xming as X server. This is not a support forum for Xming. But for the cygwin X applications. I think nedit must have a reason to look for these fonts which I have never specified somewhere As far I can see, Xming is not involved here (and I just mentioned it in *case* it is important). Basically, I could imagine two approaches to solve this: Either tell nedit not looking for these fonts, or installing these fonts in a place that nedit can find them. In both cases I don't know how to do it; that's why I posted it her. Posting it to a Xming forum doesn't make that much sense (I think), because the response there would likely be This is not a support forum for Cygwin Ronald -- Ronald Fischer rona...@eml.cc + If a packet hits a pocket on a socket on a port, + and the bus is interrupted and the interrupt's not caught, + then the socket packet pocket has an error to report. + (cited after Peter van der Linden) -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Problem reports: http://cygwin.com/problems.html Documentation: http://x.cygwin.com/docs/ FAQ: http://x.cygwin.com/docs/faq/
Why does nedit complain about these missing fonts?
I'm using Xming as X server. xlsfonts lists the following fonts as available: -misc-fixed-medium-r-semicondensed--0-0-75-75-c-0-iso8859-1 -misc-fixed-medium-r-semicondensed--13-100-100-100-c-60-iso8859-1 -misc-fixed-medium-r-semicondensed--13-120-75-75-c-60-iso8859-1 6x13 cursor fixed In the nedit preferences, I set the primary font to -misc-fixed-medium-r-semicondensed--13-120-75-75-c-60-iso8859-1 and then clicked on Fill highlight fonts from primary. However, when I invoke Cygwin's 'nedit', I get the error messages: Cannot convert string -*-helvetica-medium-r-normal-*-*-120-*-*-*-iso8859-1 to type FontStruct Cannot convert string -*-helvetica-bold-r-normal-*-*-120-*-*-*-iso8859-1 to type FontStruct Cannot convert string -*-helvetica-medium-o-normal-*-*-120-*-*-*-iso8859-1 to type FontStruct Cannot convert string -*-courier-medium-r-normal-*-*-120-*-*-*-iso8859-1 to type FontStruct Cannot convert string -*-courier-bold-r-normal-*-*-120-*-*-*-iso8859-1 to type FontStruct Cannot convert string -*-courier-medium-o-normal-*-*-120-*-*-*-iso8859-1 to type FontStruct I wonder why nedit is searching for helvetica and courier fonts. What's the best to do in this case? Just for completeness (though it likely doesn't matter here): I also searched the Xming documentation. There is a command (mkfontscale) which makes Windows fonts available to X. I have executed it, and it created a file c:\windows\fonts\fonts.dir, which seems to be a mapping between Windows font files (.TTF, .FON) and X font names. I don't know if or to what extend this could help me with the nedit problem; in any case, this list also doesn't contain helvetica or courier. Ronald -- Ronald Fischer rona...@eml.cc + If a packet hits a pocket on a socket on a port, + and the bus is interrupted and the interrupt's not caught, + then the socket packet pocket has an error to report. + (cited after Peter van der Linden) -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Problem reports: http://cygwin.com/problems.html Documentation: http://x.cygwin.com/docs/ FAQ: http://x.cygwin.com/docs/faq/
xargs: Why does order of command line switches matter?
Why do I get a different output in the following two invocations of xargs? I had expected that the relative order of the command line switches (-I, -L) would not matter: $ ls | xargs -I DIR -L 1 echo DIR DIR wontprint.txt DIR x.cmd DIR x.pl DIR x.sh $ ls | xargs -L 1 -I DIR echo DIR wontprint.txt x.cmd x.pl x.sh xargs (GNU findutils) 4.5.9 Packaged by Cygwin (4.5.9-2) Ronald -- Ronald Fischer rona...@eml.cc + If a packet hits a pocket on a socket on a port, + and the bus is interrupted and the interrupt's not caught, + then the socket packet pocket has an error to report. + (cited after Peter van der Linden) -- 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: ssh -X : connect /tmp/.X11-unix/X0: No such file or directory
On Fri, Apr 20, 2012, at 19:53, Jon TURNEY wrote: On 20/04/2012 11:43, Ronald Fischer wrote: My setup so far (which is working well), was to use Xming as X-Server and putty for logging into our Solaris hosts via ssh. Since I have Cygwin installed, I thought I could use its ssh equally well, so I exported the ssh key from putty to the format understood by ssh, and used the following bash command to login to the Solaris host: DISPLAY=:0.0 TERM=xterm ssh -p 22 -K -X -i MyPrivateKeyFile MyUserName@SolarisHost When I now try to start an X application, I get an error message like this connect /tmp/.X11-unix/X0: No such file or directory XIO: fatal IO error 131 (Connection reset by peer) on X server SolarisHost:239.0 after 0 requests (0 known processed) with 0 events remaining. I think I know what's going on here. The solution should be to use DISPLAY=localhost:0.0 instead, which means to connect to the X server for display 0 via TCP/IP, which the Xming X server should be listening on. Nice idea, but the result is, that I just get a different error message. Now it becomes: connect localhost port 6000: Connection refused X connection to SolarisHost:217.0 broken (explicit kill or server shutdown). From the FAQ, I see that port 6000 is the default. Could it be that I need to specify somehow a non-standard port? Ronald -- Ronald Fischer rona...@eml.cc + If a packet hits a pocket on a socket on a port, + and the bus is interrupted and the interrupt's not caught, + then the socket packet pocket has an error to report. + (cited after Peter van der Linden) -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Problem reports: http://cygwin.com/problems.html Documentation: http://x.cygwin.com/docs/ FAQ: http://x.cygwin.com/docs/faq/
ssh -X : connect /tmp/.X11-unix/X0: No such file or directory
My setup so far (which is working well), was to use Xming as X-Server and putty for logging into our Solaris hosts via ssh. Since I have Cygwin installed, I thought I could use its ssh equally well, so I exported the ssh key from putty to the format understood by ssh, and used the following bash command to login to the Solaris host: DISPLAY=:0.0 TERM=xterm ssh -p 22 -K -X -i MyPrivateKeyFile MyUserName@SolarisHost When I now try to start an X application, I get an error message like this connect /tmp/.X11-unix/X0: No such file or directory XIO: fatal IO error 131 (Connection reset by peer) on X server SolarisHost:239.0 after 0 requests (0 known processed) with 0 events remaining. Further investigation reveals the following: (1) I start my putty login, and find that on the remote host DISPLAY is set to (say): SolarisHost:261.0 Starting X applications works fine. (2) I start my open ssh login from Cygwin, and find that the DISPLAY variable is set to a different value, for example SolarisHost:239.0 . Starting X applications does not work. (3) In the latter shell, I export DISPLAY=SolarisHost:261.0 . Starting X applications now works. The fact that each login produces a different value for DISPLAY, is normal behaviour. Even when starting several putty sessions, each gets a different value for DISPLAY, and X apps work in all of them. It seems that by doing the ssh connection via putty, something is done which is missing from my ssh started from Cygwin. BTW, I also tried to use -Y instead of -X in my ssh invocation, but with no effect. Ronald -- Ronald Fischer rona...@eml.cc + If a packet hits a pocket on a socket on a port, + and the bus is interrupted and the interrupt's not caught, + then the socket packet pocket has an error to report. + (cited after Peter van der Linden) -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Problem reports: http://cygwin.com/problems.html Documentation: http://x.cygwin.com/docs/ FAQ: http://x.cygwin.com/docs/faq/
Re: ls does not show any output
Maybe a non-cygwin ls gets in your way. Do the following: (1) Type bash to ensure that you are running in a bash shell (2) Verify that the ls problem still exists, and if it does (3) Type type -a ls to see which ls is being used. Ronald -- Ronald Fischer rona...@eml.cc + If a packet hits a pocket on a socket on a port, + and the bus is interrupted and the interrupt's not caught, + then the socket packet pocket has an error to report. + (cited after Peter van der Linden) -- 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: chere, mksh and pdksh
On Wednesday, November 23, 2011 8:31 PM, Dave Kilroy kilr...@googlemail.com wrote: On 23/11/2011 08:12, Ronald Fischer wrote: Is there a technical reason, why chere needs to know a predefined set of keys for the shell to install? If I recall, this was to make it simple to locate any entry chere may have created. I thought so. This would go well to allow a path in addition to a key. For instance, would it not be sufficient to pass the path to the shell? In this case, new shells can be installed without the need to update chere. I think it would have to be a munged path. I suspect '/' would not be valid in a key name. Yes, but I don't think this would be a real problem in practice. New shells would depend on the shell conforming to some minimal requirements. If I recall, the existing shells do login shells slightly different. They do the login differently, but this is not something chere needs to worry. Any shell could be invoked by just calling the path (this works from command line). Of course one might argue that the user would want more control on how the shell should be invoked. For instance, I want to choose whether the shell should act as a login shell or as a non-login shell, or whether the -x should be set on invocation. Note that these are features not supported by the current chere, but when we think about expanding the concept, it makes sense thinking about this too. In fact, this could be achieved easily too, in two ways: Either chere allows for a path to the shell AND arguments, which means that the arguments need to be munged in as well; or chere insists in only getting a path to a shell. In the latter case, the user could supply a cover script (say, in bash), which just does an exec to the shell he wants to, supplying the necessary parameters. Also, if I can use the path to the shell as a key, I could (by using appropriate symlinks) have several chere entries for the same shell (for instance, mintty with ksh AND rxvt with ksh). My feeling is that most people have a prefered terminal, but may need to use different shells. The terminals behave in different ways, for example how they react on ANSI escape sequences, so it's handy to be able to run a shell in different terminals. To do what you want, my feeling is that it's easier use what chere does as an example. You can even script it with something like: chere -ip -t mintty -s ksh | sed -e s/cygwin_ksh/mintty_ksh/g a.sh chere -ip -t rxvt -s ksh | sed -e s/cygwin_ksh/rxvt_ksh/g b.sh ./a.sh ./b.sh This is indeed a feasible solution! Good point! Ronald -- Ronald Fischer rona...@eml.cc + If a packet hits a pocket on a socket on a port, + and the bus is interrupted and the interrupt's not caught, + then the socket packet pocket has an error to report. + (cited after Peter van der Linden) -- 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: chere, mksh and pdksh
It's been a while since I last refreshed the package, so I'll have a look and see if I can get something done ASAP. Is there a technical reason, why chere needs to know a predefined set of keys for the shell to install? For instance, would it not be sufficient to pass the path to the shell? In this case, new shells can be installed without the need to update chere. Also, if I can use the path to the shell as a key, I could (by using appropriate symlinks) have several chere entries for the same shell (for instance, mintty with ksh AND rxvt with ksh). Ronald -- Ronald Fischer rona...@eml.cc + If a packet hits a pocket on a socket on a port, + and the bus is interrupted and the interrupt's not caught, + then the socket packet pocket has an error to report. + (cited after Peter van der Linden) -- 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
chere, mksh and pdksh
I would like to use chere to create a context menu for a terminal running ksh. I have installed mksh, since pdksh is marked as obsolete. However, the chere man-page says that it expects pdksh, if I want a Korn Shell. What is the best way to proceed? - Install pdksh too, although it is obsolete? - Create a symlink /usr/bin/pkdsh, to point to mksh? Ronald -- Ronald Fischer rona...@eml.cc + If a packet hits a pocket on a socket on a port, + and the bus is interrupted and the interrupt's not caught, + then the socket packet pocket has an error to report. + (cited after Peter van der Linden) -- 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
Please explain afio warning message
Executing the command find . -print0 | afio -o -z -Z -0 -Y '*.log' -T 1k -G 2 /cygdrive/c/temp/arch.afio results in the following warning message: afio: .: Cannot create cpio-compatible file header for this input afio: /cygdrive/c/temp/save.afio [offset 0]: Continuing, archive will not be fully compatible with cpio or afio versions 2.4.7 and lower afio: /cygdrive/c/temp/save.afio: Warning: Created archive is not fully compatible with cpio or afio versions 2.4.7 and lower. afio: /cygdrive/c/temp/save.afio: See the ARCHIVE PORTABILITY section of the manpage. I read the section about portability, but still don't know the reason for this warning, only that it somehow must be related to the usage of . for denoting the working directory. Can I safely ignore the warnings? Is there a way to suppress them, other than redirecting stderr to the bit bucket? cpio compatibility is not crucial for me. -- Ronald Fischer rona...@eml.cc + If a packet hits a pocket on a socket on a port, + and the bus is interrupted and the interrupt's not caught, + then the socket packet pocket has an error to report. + (cited after Peter van der Linden) -- 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: Mapping underline to colour - how is the colour determined?
infocmp cygwincygwin.txt Which package do I need to have infocmp installed? According to Setup, I have terminfo 5.7 installed. However, infocmp is not in my PATH, not is there a man page for it. http://cygwin.com/cgi-bin2/package-grep.cgi?grep=infocmp Regards Marco Hmm... Using this link, I get a search result of the following packages: = Found 5 matches for infocmp ncurses/ncurses-5.7-16 Utilities for terminal handling ncurses/ncurses-5.7-18 Utilities for terminal handling ncursesw/ncursesw-5.7-18Utilities for terminal handling tetex-bin/tetex-bin-2.0.2-15-srcThe TeX text formatting system (binaries). tetex-bin/tetex-bin-3.0.0-3-src The TeX text formatting system (binaries). = Nothing which looks like infocmp Ronald -- Ronald Fischer rona...@eml.cc + If a packet hits a pocket on a socket on a port, + and the bus is interrupted and the interrupt's not caught, + then the socket packet pocket has an error to report. + (cited after Peter van der Linden) -- 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: Mapping underline to colour - how is the colour determined?
Thanks a lot for the detailed instructions! Now go create a new working directory somewhere, perhaps under your home directory. In there, type: infocmp cygwin cygwin.txt Which package do I need to have infocmp installed? According to Setup, I have terminfo 5.7 installed. However, infocmp is not in my PATH, not is there a man page for it. Regards, Ronald -- Ronald Fischer rona...@eml.cc + If a packet hits a pocket on a socket on a port, + and the bus is interrupted and the interrupt's not caught, + then the socket packet pocket has an error to report. + (cited after Peter van der Linden) -- 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
Mapping underline to colour - how is the colour determined?
When I (to give an example) execute a man command within a mintty window, and do the same within a normal Windows console window, I see that those words represented as underlined words in the mintty window, are represented by a different colour in the Windows console windows. I guess this different has nothing to do with the man command, but by the way the terminal definition says how render emphasized words. Since the Windows console (likely) can't underline, colouring is used. It's kind of a terminal property. Do I understand this correctly? I would like to understand, where this mapping to a certain colour is done. Reason is that the colour used for my Windows console window, is a bit hard to read and I would like to change it. Any suggestions? Ronald -- Ronald Fischer rona...@eml.cc + If a packet hits a pocket on a socket on a port, + and the bus is interrupted and the interrupt's not caught, + then the socket packet pocket has an error to report. + (cited after Peter van der Linden) -- Ronald Fischer rona...@eml.cc + If a packet hits a pocket on a socket on a port, + and the bus is interrupted and the interrupt's not caught, + then the socket packet pocket has an error to report. + (cited after Peter van der Linden) -- 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
Best way to repair cygwin?
Cygwin worked well so far. However, starting with today, I get the following error - for example when invoking bash: MUCNL3E6880:~ 2 23 $ bash --norc 163 [main] bash 5788 exception::handle: Exception: STATUS_ACCESS_VIOLATION 1958 [main] bash 5788 open_stackdumpfile: Dumping stack trace to bash.exe.stackdup When doing a zsh -f this works at first, but as soon as I do a man man in the shell, I get 9420794 [main] sh 8004 exception::handle: Exception: STATUS_ACCESS_VIOLATION Exception: STATUS_ACCESS_VIOLATION at eip=6102048B eax=009DD298 ebx=61246414 ecx=758E7B6E edx=003F51F8 esi= edi=0022FA10 ebp=61020C00 esp=0022C7E0 program=C:\cygwin\bin\sh.exe, pid 8004, thread main cs=001B ds=0023 es=0023 fs=003B gs= ss=0023 Stack trace: Frame Function Args End of stack trace 9455844 [main] sh 5776 exception::handle: Exception: STATUS_ACCESS_VIOLATION 9458931 [main] sh 5776 open_stackdumpfile: Dumping stack trace to sh.exe.stackdump 9487143 [main] sh 348 exception::handle: Exception: STATUS_ACCESS_VIOLATION 9490092 [main] sh 348 open_stackdumpfile: Dumping stack trace to sh.exe.stackdump 9494562 [main] sh 1860 fork: child -1 - died waiting for longjmp before initializatio n, retry 0, exit code 0x8B00, errno 11 sh: fork: retry: Resource temporarily unavailable ... (and so on, in a endless loop). I wonder why zsh is invoking sh.exe implicitly, when I just call man, but in any case the error message suggests that bash.exe / sh.exe is broken. I had run setup again yesterday evening, in order to install wcd (found in the util section). The setup run to the end without error message, and I switched off the PC. Today I found bash broken. Since wcd utility is an extension to the chdir command, it is conceivable that it fiddled around with bash somehow, but I consider it unlikely that this would cause the effect I am observing: Such an obvious bug would not have been unnoticed. I wonder whether there is an easy way to repair Cygwin (maybe a procedure to automatically re-install everything). I searched on the Net but didn't find anything in this direction. Any other idea what I could do? Ronald -- Ronald Fischer rona...@eml.cc + If a packet hits a pocket on a socket on a port, + and the bus is interrupted and the interrupt's not caught, + then the socket packet pocket has an error to report. + (cited after Peter van der Linden) -- 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
SOLVED (was: Re: fixing fork failures (was: Re: Best way to repair cygwin?))
This is typically the result of one of two things: 1. http://cygwin.com/acronyms/#BLODA 2. DLL collisions - Install the 'rebase' package, read its README in /usr/share/doc/Cygwin, and follow the instructions there to run 'rebaseall'. Thanks a lot! In my case it turned out to be a BLODA I will however install rebase too, in case I need it one day. Ronald -- Ronald Fischer rona...@eml.cc + If a packet hits a pocket on a socket on a port, + and the bus is interrupted and the interrupt's not caught, + then the socket packet pocket has an error to report. + (cited after Peter van der Linden) -- 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: Does not work well: rlwrap + rxvt + cmd
On Wed, 24 Aug 2011 11:15 -0400, Eliot Moss m...@cs.umass.edu wrote: Just a quick thought, but I think you may want to run rlwrap within rxvt, something like: rxvt rlwrap cmd.exe Thanks a lot! Indeed, rxvt -e rlwrap cmd Ronald -- Ronald Fischer rona...@eml.cc + If a packet hits a pocket on a socket on a port, + and the bus is interrupted and the interrupt's not caught, + then the socket packet pocket has an error to report. + (cited after Peter van der Linden) -- 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: Does not work well: rlwrap + rxvt + cmd
On Wed, 24 Aug 2011 11:56 -0400, Eliot Moss m...@cs.umass.edu wrote: On 8/24/2011 11:52 AM, Ronald of Steiermark wrote: On Wed, 24 Aug 2011 08:39 -0700, Andrew DeFariaand...@defaria.com wrote: For instance, to test the cruel BAT files which we are going to deliver. You can run .bat files from bash and other Cygwin shells. You can *run* them, but the effect is not always the same. For example, setting an environment variable within a batch file under CMD.EXE results in the environment variable being visible in the calling environment (similar to sourcing a file in bash), while calling the batch file from bash leaves the environment intact. Also, some internal commands (for example COPY) are not present in bash, though this can be easily remedied using an alias or a shell function. Other problems are related to the use of \ as a path separator. Imagine that some of your BATCH files generate environment variables containing a Windows path, and simply because bash command lines are interpreted differently than Windows CMD command line (for example, when it comes to quoting or parameter substitution). The main problem, however, is: If you are going to deliver something, which is supposed to run under CMD.EXE, most customers won't accept it until you really have tested it under CMD.EXE, and for good reason. In fact, even though I got running rxvt with cmd thanks to all the suggestions to my post, I will do some *final* tests still in plain, native Windoze Command-Windows, just for the safe side. Using a bash shell as a main work horse is great, but when you have the pleasure to create and test batch files, you will sooner or later be happy to also have a CMD shell available... In both cases you generally to present Windows paths, of course; cygpath can help with that. I use cygpath in several of my scripts and it's extremely useful, but dealing with the various path representations in interactive work is, for me at least, an annoyance... Thank you for your suggestions, though! Ronald -- Ronald Fischer rona...@eml.cc + If a packet hits a pocket on a socket on a port, + and the bus is interrupted and the interrupt's not caught, + then the socket packet pocket has an error to report. + (cited after Peter van der Linden) -- 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
Does not work well: rlwrap + rxvt + cmd
I would like to run cmd.exe within a rxvt terminal on Windows 7. Problem is that calling the cmd.exe command history does not work (it seems that the cursor keys are not passed properly to cmd.exe). In one thread in this mailing list, it was recommended to wrap the rxvt call by rlwrap: rlwrap rxvt -e cmd.exe However, this doesn't solve the problem. Any other suggestions? Maybe any alternative to the standard Windows console? On Windows XP I used the sourceforge-project Console2, but on Windows 7 it crashes so often, that I am looking for a different solution. In particular, I like with rxvt (and with Console2) the ease of copyiing and pasting text, in particular text spanning more than one line. Ronald -- Ronald Fischer rona...@eml.cc + If a packet hits a pocket on a socket on a port, + and the bus is interrupted and the interrupt's not caught, + then the socket packet pocket has an error to report. + (cited after Peter van der Linden) -- 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
Encoding of German 'umlauts' - please explain
Maybe someone could enlighten me about the following: On Cygwin bash I see $ echo ü | od -cx 000 374 \n 0afc 002 That means, the German letter ü has encoding 0xFC. If I do the same on CMD shell (the 'od' used here comes from the Gnu Utilities for Windows), I see: echo ü | od -cx 000 201 \r \n 2081 0a0d 004 That is, ü is encoded as 0x81. Why is this different? I am aware that, for historic reason, different encodings exist (the old DOS encoding, Windows ANSI encoding etc.). I wouldn't have expected those differences, however, when comparing bash.exe vs. cmd.exe. -- 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
link broken
The FAQ link on http://x.cygwin.com/, pointing to http://x.cygwin.com/docs/faq/, always gives error 504 (gateway timeout). -- Ronald Fischer rona...@eml.cc + If a packet hits a pocket on a socket on a port, + and the bus is interrupted and the interrupt's not caught, + then the socket packet pocket has an error to report. + (cited after Peter van der Linden) -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Problem reports: http://cygwin.com/problems.html Documentation: http://x.cygwin.com/docs/ FAQ: http://x.cygwin.com/docs/faq/
startxwin.bat causes unnecessary configuration issue
Not strictly speaking a bugreport (everything works as described), but a proposal how to make life easier: startxwin.bat currently contains the line SET CYGWIN_ROOT=\cygwin Unless your Cygwin Root happens to be at that location, this has to be edited manually. This would not be necessary in nearly all cases if we observe that (1) CYGWIN_ROOT is very often set system-wide anyway, after Cygwin has been installed, and (2) in the rare cases where it is unset, it is usually the same directory where startxwin.bat is located. Therefore, startxwin.bat can find out by itself where its root is: if defined CYGWIN_ROOT goto :OK set CYGWIN_ROOT=%~dp0\.. :OK Ronald -- Ronald Fischer rona...@eml.cc + If a packet hits a pocket on a socket on a port, + and the bus is interrupted and the interrupt's not caught, + then the socket packet pocket has an error to report. + (cited after Peter van der Linden) -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Problem reports: http://cygwin.com/problems.html Documentation: http://x.cygwin.com/docs/ FAQ: http://x.cygwin.com/docs/faq/
Re: Finding either boot time or login time
Mark J. Reed markjreed at gmail.com writes: One-liner to display the boot time: $ perl -lane 'print ~~localtime(time-$F[0])' /proc/uptime Thanks a lot! This is great! Would you mind explaining the ~~ trick? localtime returns a list, so I would have concluded that applyiing ~ to this list would force it into scalar context, so it would bitwise negate the number of elements in the list. But this is obviously not done, because just by trying out your code, I see that it works. Ronald -- 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/
Finding either boot time or login time
I'm a bit desperate. I'm looking for a way to find EITHER the time the system was booted, OR the time the last user had logged in, OR the time I had logged in (of course it would be great if I could find all of it, but one of this would already be sufficient). From a past posting to this issue, I got the advice to use the 'last' command, but issuing, for instance, last I only get wtmp begins Thu Jan 29 09:22:40 2009 which is the time wtmp has been created (but there was at least one shutdown and startup after this - why doesn't it show up in wtmp?). Then I thought I could get this information by sysctl -a, but had to learn that this is not implemented. Any other idea what I could try? Ronald -- 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: Finding either boot time or login time
Eric Blake ebb9 at byu.net writes: man uptime I have thought of uptime, but this requires doing date calculation (I have to subtract the uptime from the current time), which I wanted to avoid; plus I wanted to have it reproducible (i.e. if I calculate the startup time twice in succession, I wanted to get the same result - using the uptime calculation might well give differences of, say, one, in rare cases 2, seconds for the startup time on repeated calculations. But it seems there is no alternative. I had not expected that Windows would not log such events, like starting up or having some user logged in... Ronald -- 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: Finding out login history
Marco Atzeri marco_atzeri at yahoo.it writes: RTFM man last touch /var/log/wtmp uh - thanks! Ronald -- 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/
/sbin/sysctl question
Is there a way to get /sbin/sysctl -a running on cygwin? I get error: unable to open directory /proc/sys/ and indeed, there is no sys under proc. Under what conditions is /proc/sys created on cygwin? Ronald -- 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: Finding out login history
Marco Atzeri marco_atzeri at yahoo.it writes: OK, now I finally have 'last', there is a usage problem: mucn13154:~ 1 501 $ last last: /var/log/wtmp: No such file or directory Perhaps this file was removed by the operator to prevent logging last info. mucn13154:~ 1 503 $ ls -l /var/log total 6031 -rw-r--r-- 1 fischron mkgroup-l-d 0 Dec 16 10:31 cron.log drwxrwxrwx+ 2 SYSTEM root 0 Jan 20 15:02 exim -rwxrwxrwx+ 1 fischron mkgroup-l-d 285562 Jan 20 15:08 setup.log -rwxrwxrwx+ 1 fischron mkgroup-l-d 5889080 Jan 20 15:08 setup.log.full Seems as if I am out of luck here Ronald -- 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/
Finding out login history
Is it possible to find out the login history, i.e. the exact time on the previous days a user has logged on, respectively the system has been rebooted (though these times are not the same, in my case I would be happy getting either one)? I know that from the data displayed by 'uptime', I can calculate the time since when the PC is running now, but I would also find the time of the previous system startups or user logins. Maybe this is recorded in /var/run/utmp (at least uptime gets is information from there), but I don't know whether this records the history, and it is a binary file anyway. Ronald -- 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: Finding out login history
Morche Matthias Matthias.Morche at P7S1Produktion.de writes: try last, that provides the information, you are looking for. Thank you for helping. Which package do I have to install, to have 'last' available? mucn13154:~ 1 505 $ man last No manual entry for last mucn13154:~ 1 506 $ last bash: last: command not found -- 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: Finding out login history
Andy Koppe andy.koppe at gmail.com writes: Thank you for helping. Which package do I have to install, to have 'last' available? util-linux Thanks a lot! For future reference: http://cygwin.com/packages/ The problem with this page is that if you search the packages for last, you get 140+ matches, where it is easy to overlook the right one ;-) But thank you for pointing this out. Ronald -- 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: Finding out login history
Andy Koppe andy.koppe at gmail.com writes: Thank you for helping. Which package do I have to install, to have 'last' available? util-linux Rerunning setup.exe, it showed me that I *did* have util-linux installed; even the most recent version. Is last supposed to be in /bin or in some other directory? BTW I tried to reinstall, but reinstallation hung after 31% completion. Seems that today is not my day. Ronald -- 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 Mail and Exchange Server
Frank Fesevur ffes at users.sourceforge.net writes: Have you tried the cygwin email package? It talks directly to an SMTP server. Good suggestion. I think I'll stick with this. Ronald -- 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/
wget and HTTP_PROXY question
I can't fetch anything from the web using wget (Connection timed out). My guess is that it has to do with the proxy settings, but: - my environment variable HTTP_PROXY is set, and - from a Windows command line (i.e. outside of Cygwin), tools (such as the package manager of ActiveState Perl) *can* use the proxy specified here, without problems. What can I do to get wget working? Ronald -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Problem reports: http://cygwin.com/problems.html Documentation: http://cygwin.com/docs.html FAQ: http://cygwin.com/faq/
Cygwin Mail and Exchange Server
Hello, at a customer's site, I would like to be able to send email from bash scripts. The setup of the software is pretty standard: Usually mail is sent and read using Outlook, and there is an Exchange server lurking somewhere to do the job. What do I have to do in such an environment in order to be able to send mail from cygwin? I thought this is such a common setup that there must be somewhere a howto for this subject, but I searched the Cygwin FAQ, the Cygwin User Guide, and /usr/doc/cygwin without success. Isn't there a Cygwin utility which simply uses the settings in Outlook to send the mail? Ronald -- 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 Mail and Exchange Server
Dave Korn dave.korn at artimi.com writes: at a customer's site, I would like to be able to send email from bash scripts. The setup of the software is pretty standard: Usually mail is sent and read using Outlook, and there is an Exchange server lurking somewhere to do the job. What do I have to do in such an environment in order to be able to send mail from cygwin? You need to ask your admins for POP and SMTP access details of your exchangeserver, I guess in my case (sending only) I just need SMTP. Or is it necessary that ssmtp.conf always contains POP too? And, AFIK, the access method to the exchange server is not POP, but IMAP... then you'd probably enter those details into your /etc/ssmtp/ssmtp.conf (or equivalent depending what mailer you're using). Is there a simpler command line utility for sending mail - I mean, simpler than ssmtp -, which you could recommend? I thought this is such a common setup that there must be somewhere a howto for this subject, but I searched the Cygwin FAQ, the Cygwin User Guide, and /usr/doc/cygwin without success. Isn't there a Cygwin utility which simply uses the settings in Outlook to send the mail? Nope. It's not like Microsoft have documented how any of that stuff is stored, after all. And since Cygwin is mostly ports of Linux stuff, and Linux doesn't have any such things as outlook or exchange server, none of the linux software that gets ported is written to even consider it. Understandable... Thanks a lot, Ronald Fischer -- 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 Mail and Exchange Server
Andrew DeFaria Andrew at DeFaria.com writes: No need to ask the admins, you can lookup these settings directly in Outlook under Tools: Email accounts. It probably won't say anything about POP/IMAP but you can just do telnet mail server POP or telnet mail server IMAP. If it responds with a server at the other end then you know it's up. Thanks a lot, to all who have helped! Ronald -- 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 IPC::Cmd
I'm using perl 5.8.7 for Solaris perl 5.8.8 for Cygwin perl 5.8.10 for Windows (native) To my surprise, the Cygwin version of Perl does not include the standard module IPC::Cmd, though the other two (in particular, the earlier 5.8.7 Perl) do. Is there a particular reason, why IPC::Cmd is left out from the Cygwin distribution? Ronald -- 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 IPC::Cmd
Sisyphus sisyphus1 at optusnet.com.au writes: I'm using perl 5.8.7 for Solaris perl 5.8.8 for Cygwin perl 5.8.10 for Windows (native) perl 5.8.10 ?? Sorry, I meant 5.10.0 Mind you, they don't need a reason to not include a non-core module - the fact that it's not a core module is, of itself, sufficient reason. I see. I was not aware that this is not a core module. With perl 5.10.0, IPC::Cmd became a core module, so *every* build of perl 5.10.0 ought to include that module. Thanks a lot. Ronald -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Problem reports: http://cygwin.com/problems.html Documentation: http://cygwin.com/docs.html FAQ: http://cygwin.com/faq/
Can't set access rights with chmod
Please have a look at the following transscript: $ ls -l x1.pl -rw-r--r-- 1 fischron mkgroup-l-d 104 May 5 15:54 x1.pl $ chmod 0777 x1.pl $ ls -l x1.pl -rw-r--r-- 1 fischron mkgroup-l-d 104 May 5 15:54 x1.pl $ chmod +x x1.pl $ ls -l x1.pl -rw-r--r-- 1 fischron mkgroup-l-d 104 May 5 15:54 x1.pl The same happens when I try other access right combinations. Somehow, the files get access rights when created (typically 0644, sometimes 0755), but I have no way to change the access right afterwards. This happens only on files stored on my networked drive. In the Cygwin FAQ, I found the following hint: The most common case is that your /etc/passwd or /etc/group files are not properly set up. If ls -l shows a group of mkpasswd or mkgroup, you need to run one or both of those commands. Hmmm... my group is not listed as mkgroup, but as the pretty similar mkgroup-l-d. OTOH, chmod works fine on the non-networked drive (/cygdrive/c), and there ls -l shows mkgroup-l-d as well. Also, neither in the man page of mkgroup, nor on the cygwin FAQ, I could find a hint on how to use the mkgroup program to remedy my situation - if this really is the reason for the problem at all. What could I do to get it working? Ronald -- 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: Can't set access rights with chmod (additional info)
Ronald Fischer fischerr.external at infineon.com writes: In addition to what I wrote in the previous posting, I also tried the following: export CYGWIN=smbntsec Now the behaviour changed in that chmod now works well for *new* files created, but for old files I still can't change anything. This time, I get the error message permission denied: $ ls -l x1.pl -rwx--+ 1 fischron 104 May 5 15:54 x1.pl $ chmod ugo+x x1.pl chmod: changing permissions of `x1.pl': Permission denied $ Ronald -- 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/
Redoing the setup on a different machine
Is there an easy solution to the following problem? From time to time (every couple of weeks or few months) I happen to have to use a different Windows machine on a different customer's site. I always want to use Cygwin there with my favorite packages. This means that every time I have to setup Cygwin (this is OK, not much work) and then go to all the package and manually flag what I want to have included (this *is* much work, and error-prone, since I tend to overlook something). I guess that Cygwin maintains somewhere on the hard disk a file containing a list of all installed packages. Is it possible to save this file on the old machine, and after having setup a minimal Cygwin on the new machine, put that package file on it, call setup again and tell it to reinstall the most recent versions of these packages? (BTW, I wonder whether this would be a good entry in the Cygwin FAQ, since probably many users will have the same problem when moving to a new computer). Ronald -- Ronald Fischer [EMAIL PROTECTED] Phone: +49-89-452133-162 -- 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/
occasional problem: .bash_profile permission denied
I configured my system so that it automatically starts Cygwin during boot time via the Windows autostart feature, by using startxwin and Cygwin/X to start several xterm and rxvt terminals, and also to start one bash shell in plain Cygwin (outside X). Occasionally, one or two of the shells started that way complain bash: /cygdrive/h/.bash_profile: Permission denied Of course there is nothing wrong with my .bash_profile, and if I then do a manual . .bash_profile in these shells, everything works manually. It is certainly not a X specific issue, because it had occured already in the plain Cygwin shell too. My first idea was that perhaps that it could be a race condition between Windows starting the Autostart applications and mounting the network drives, because my $HOME is on a network drive. But this would not explain the following: When I start several xterm's from my startxwin.bat, it happens sometimes that the permission denied error occurs on one of the terminals started *later*, while the earlier started ones don't have this problem. Any idea what could be wrong here? Ronald -- Ronald Fischer [EMAIL PROTECTED] Phone: +49-89-452133-162 -- 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/
Where is evim gone?
The man page for gvim documents evim and eview, but these files are not in /usr/bin. Aren't they part of the regular distribution package of gvim? Ronald -- Ronald Fischer [EMAIL PROTECTED] Phone: +49-89-452133-162 -- 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: RE: RE: RE: Two issues with Xwin
It's not Zsh that's eating my Enter (or Tab) key but X (or maybe the terminal emulator). It doesn't happen all the time but often. I can't find any pattern in this. I sometimes find that I have to wait 10-40 seconds or so until the completions are shown. Or, when I do a ls /usr/bin (for instance), sometimes I see the result immediately, sometimes it takes 10-15 seconds after pressing the enter key, until the files are displayed. Could be attributed in my case to networking issues (my $HOME is on a Samba-mounted netdrive), so it could be a timing/caching issue. But this does, of course, not explain why your two terminals should behave differently. You did not say how frequent this occurs. Could it be that it happens rarely enough, that just by accident you have observed it only with one terminal type, but not with the other? Does the X terminal sometimes eat other keys too when you are typing fast? And I still would find it worth a try - despite what has been suggested earlier in this thread - to see whether the same behaviour exists with bash (or other applications reading keystrokes). Ronald -- Ronald Fischer [EMAIL PROTECTED] Phone: +49-89-452133-162 -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Problem reports: http://cygwin.com/problems.html Documentation: http://x.cygwin.com/docs/ FAQ: http://x.cygwin.com/docs/faq/
[bug?] Directory lister (d) doesn't properly translate drive letters
Please have a look at this: ~/thome $ pwd /cygdrive/h/thome ~/thome $ ls -dl t:/rfischer drwxr-xr-x 1 rfischer mkgroup-l-d 0 Aug 28 23:55 t:/rfischer ~/thome $ d t:/rfischer /cygdrive/h/thome/t:/rfischer doesn't exist! ~/thome $ While ls seems to understand the notion of t:, d does not. ~/thome $ mount C:\cygwin\bin on /usr/bin type user (binmode) C:\cygwin\lib on /usr/lib type user (binmode) C:\cygwin on / type user (binmode) c: on /cygdrive/c type user (binmode,noumount) h: on /cygdrive/h type user (binmode,noumount) i: on /cygdrive/i type user (binmode,noumount) l: on /cygdrive/l type user (binmode,noumount) m: on /cygdrive/m type user (binmode,noumount) t: on /cygdrive/t type user (binmode,noumount) v: on /cygdrive/v type user (binmode,noumount) -- Ronald Fischer [EMAIL PROTECTED] Phone: +49-89-452133-162 cygcheck.out.gz Description: cygcheck.out.gz -- 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: RE: RE: Two issues with Xwin
* Ronald Fischer (Mon, 27 Aug 2007 15:57:34 +0200) This suggest that different dot-files are sourced in the two cases. When I run bash (in my case) either from cmd or started by XWin, I also have differences in which dot-files are sourced, so this is the first place you might want to look. There is just one configuration file in this case: ~/.zshrc. H this should be sourced every time you have an interactive shell. And I don't have any setting that would have the do nothing on the first enter; wait for the second enter effect. I guess you mean: wait for the second *tab* etc. In this case, the correct behaviour should *always* be (I think) to show that part of the completion, which is unique, on the first press of tab, and show a list of all possible completions on the second press of tab. If it is not due to different settings in your shells, I have no idea why anymore why both shells behave different (stupid question: You are sure that you have the same zsh called in both cases? What does echo $ZSH_VERSION say in rxvt, respectively CMD window?) Maybe this is the point where you should repost this problem to the zsh folks. Not only it doesn't look that much like a Cygwin issue to me, but I remember that on the zsh mailing list (http://zsh.dotsrc.org/Doc/Release/zsh_2.html#SEC6), there are also quite a few Cygwin users hanging around, so your problem will for sure be understood there. Ronald -- Ronald Fischer [EMAIL PROTECTED] Phone: +49-89-452133-162 -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Problem reports: http://cygwin.com/problems.html Documentation: http://x.cygwin.com/docs/ FAQ: http://x.cygwin.com/docs/faq/
RE: Two issues with Xwin
* using a terminal and a shell I often have to enter Enter or Tab twice to get the desired effect. How come? Which effect do you desire? (Filename completion, command completion, ...)? Which shell? How did you configure it? (i.e. if you are talking about readline functionality, what's the content of your .inputrc, and did you make sure it gets read?). Ronald -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Problem reports: http://cygwin.com/problems.html Documentation: http://x.cygwin.com/docs/ FAQ: http://x.cygwin.com/docs/faq/
Windows fonts usage?
Is there a way to use/convert the fonts which come with Windows, for usage with Cygwin/X, when running XWin.exe in Multiwindow mode? Ronald -- Ronald Fischer [EMAIL PROTECTED] Phone: +49-89-452133-162 -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Problem reports: http://cygwin.com/problems.html Documentation: http://x.cygwin.com/docs/ FAQ: http://x.cygwin.com/docs/faq/
RE: File creation time oddity (new findings)
So the effect seems to be the same as before: As if a different clock were used when calculating the time stamps for creating a file, or for modifying it. Hmm, could it be that your files reside on a remote mount, and that NFS is reflecting the time of the remote machine (ie. the remote machine leads or lags your machine)? Indeed, this is the case. On the remote (Linux-) machine, ntp was not running. Interestingly, although this is corrected now (the remote machine and my Windows workstation both synchronize to the same time server), the times between the two systems is slightly different (now the remote system being a little bit ahead in time, less than 2 seconds, than my system). From what I can see, the time on the remote system seems to be the correct one, and Windows seems to have trouble staying in sync with the internet time server, although Windows synchronizes every hour. But this is certainly not a problem which belongs to the Cygwin mailing list, and I mention it here only for completeness. Could it be that file creation times are put into the directory in a different way if it is a mapped drive from the network? It is an artifact of how Windows interacts with remote drives in the presence of clock skew between the machines. Thank you for clarification. Ronald -- Ronald Fischer [EMAIL PROTECTED] Phone: +49-89-452133-162 -- 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: shell properties
when I do a startx, I get a new window shell with properties different from the one on which I typed startx. The problem is I want to change the font size on this new window and I do not know how. I guess that in this case, you should put your startup code for the terminals into ~/.xinitrc, where you can then specify the font to be used (man xterm, or whatever terminal you are going to use). Also, is it possibly to directly open x11 without opening normal cygwin first? This is how I am doing it. For this, I copied /usr/bin/X11/startxwin.bat into my autostart folder (I prefered to copy it instead of creating a link, but this is a matter of taste), and modified it. There is already one xterm to be started in startxwin.bat, so you can add/modify yours according to your taste. Ronald -- Ronald Fischer [EMAIL PROTECTED] Phone: +49-89-452133-162 -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Problem reports: http://cygwin.com/problems.html Documentation: http://x.cygwin.com/docs/ FAQ: http://x.cygwin.com/docs/faq/
File creation time oddity
On my system, the initial (creation) time for a file seems to be around 7 minutes shifted to the past. This is reproducible: ~/thome/tmp $ date Thu Aug 16 16:49:18 2007 ~/thome/tmp $ ls -l dummy3 ls: cannot access dummy3: No such file or directory ~/thome/tmp $ echo x dummy3 ~/thome/tmp $ date Thu Aug 16 16:49:35 2007 ~/thome/tmp $ ls -l dummy3 -rw-r--r-- 1 rfischer mkgroup-l-d 2 Aug 16 16:42 dummy3 As you can see, ls -l shows 16:42 for the creation time, when it was actually created around 16:49. This problem does NOT occur with file modification time: ~/thome/tmp $ date Thu Aug 16 16:51:12 2007 ~/thome/tmp $ touch dummy3 ~/thome/tmp $ ls -l dummy3 -rw-r--r-- 1 rfischer mkgroup-l-d 2 Aug 16 16:51 dummy3 Any idea what could possibly be the reason for this oddity? Ronald -- Ronald Fischer [EMAIL PROTECTED] Phone: +49-89-452133-162 -- 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 rename file case-sensitive?
Is there an easy way to rename a file foo to Foo? mv foo Foo complains that they are the same file. From the FAQ I learned that this is due to the limitations of Windows which does not distinguish between case in file names. The FAQ also says that there is a highly experimental case-sensitive file system available. Not being prepared yet to live in a highly experimental way, I'm curious whether there is a simpler solution to the rename problem aside from the obvious hack mv foo bar; mv bar Foo -- Ronald Fischer [EMAIL PROTECTED] Phone: +49-89-452133-162 -- 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/
oclock color bug?
I'm using XWin -multiwindow to run Cygwin/X When I start the oclock with: oclock -minute blue -hour black -bd green -transparent -jewel red -geometry 322x322+500+400 I get a clock with green border, but minute hand, hour hand and jewel all being in blue. Ronald -- Ronald Fischer [EMAIL PROTECTED] Phone: +49-89-452133-162 -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Problem reports: http://cygwin.com/problems.html Documentation: http://x.cygwin.com/docs/ FAQ: http://x.cygwin.com/docs/faq/
Possible bug: d does not seem to read ~/.d.conf
$ d --version d v1.2.0 From info d we can see that /usr/bin/d is supposed to honour a configuration file ~/.d.conf and that in this file, the boolean variable hidden-files-shown corresponds to the --hidden-files flag in the d command line. I have therefore put hidden-files-shown=true into my ~/.d.conf, but when I call d, I do not see the hidden files, but I also do not receive any error message. If I invoke d explicitly with d --hidden-files the hidden files are displayed. -- Ronald Fischer [EMAIL PROTECTED] Phone: +49-89-452133-162 -- 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: mysql.so: Permission denied (Ruby under Cygwin)
Well, Cygwin Ports has MySQL client and server packages so you can use that if you want. But how do I get at it from Ruby? It doesn't seem to be in the Cygwin Ruby package (at least not under the name 'mysql'), and there seems to be no additional MySql Cygwin package available. Ronald -- Ronald Fischer [EMAIL PROTECTED] Phone: +49-89-452133-162 -- 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/
mysql.so: Permission denied (Ruby under Cygwin)
[this message is crossposted to the Cygwin- and RubyTalk mailing lists]. Running Ruby 1.8.6 under Cygwin, i.e. $ /usr/bin/ruby --version ruby 1.8.6 (2007-03-13 patchlevel 0) [i386-cygwin] the statement require 'mysql' raises the following error message: /usr/lib/ruby/gems/1.8/gems/mysql-2.7.3-mswin32/ext/mysql.so: Permission denied - /usr/lib/ruby/gems/1.8/gems/mysql-2.7.3-mswin32/ext/mysql.so (LoadError) from /usr/lib/ruby/site_ruby/1.8/rubygems/custom_require.rb:32:in `require' The access rights to mysql.so are as follows: -rw-r--r-- 1 rfischer mkgroup-l-d 81984 May 21 18:08 /usr/lib/ruby/gems/1.8/gems/mysql-2.7.3-mswin32/ext/mysql.so Using the mysql module with Ruby on Windows outside Cygwin works well. What could be the reason for this problem? Ronald -- Ronald Fischer [EMAIL PROTECTED] Phone: +49-89-452133-162 -- 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: mysql.so: Permission denied (Ruby under Cygwin)
-Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Corinna Vinschen Sent: Monday, June 18, 2007 3:04 PM To: cygwin@cygwin.com Subject: Re: mysql.so: Permission denied (Ruby under Cygwin) On Jun 18 14:57, Ronald Fischer wrote: Finally, I have installed the Ruby mysql module via gem install -r mysql assuming that this would do the right thing anyway. Native Windows gem or Cygwin gem? If you use the native Windows gem you'll get native WIndows packages. I don't even know if a Cygwin gem exists. There is none. I was told by Ruby-Talk people that I should use the Windows gem - it would work fine. Have you checked the library dependencies of mysql.so? This is funny: Although ls shows that mysql.so exists in $PWD, I get /usr/lib/ruby/gems/1.8/gems/mysql-2.7.3-mswin32/ext $ cygcheck mysql.so Error: could not find mysql.so But at least it works when I supply a path: /usr/lib/ruby/gems/1.8/gems/mysql-2.7.3-mswin32/ext $ cygcheck ./mysql.so .\mysql.so c:\ruby185\bin\msvcrt-ruby18.dll C:\WINDOWS\system32\USER32.dll C:\WINDOWS\system32\GDI32.dll C:\WINDOWS\system32\KERNEL32.dll C:\WINDOWS\system32\ntdll.dll C:\WINDOWS\system32\ADVAPI32.dll C:\WINDOWS\system32\RPCRT4.dll C:\WINDOWS\system32\WS2_32.dll C:\WINDOWS\system32\msvcrt.dll C:\WINDOWS\system32\WS2HELP.dll c:\Programme\MySQL\MySQL Server 5.0\bin\LIBMYSQL.dll C:\WINDOWS\system32\WSOCK32.dll So this seems to look well, doesn't it? Ronald -- 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: mysql.so: Permission denied (Ruby under Cygwin)
require 'mysql' raises the following error message: /usr/lib/ruby/gems/1.8/gems/mysql-2.7.3-mswin32/ext/mysql.so: Permission denied - /usr/lib/ruby/gems/1.8/gems/mysql-2.7.3-mswin32/ext/mysql.so (LoadError) from /usr/lib/ruby/site_ruby/1.8/rubygems/custom_require.rb:32:in `require' The access rights to mysql.so are as follows: -rw-r--r-- 1 rfischer mkgroup-l-d 81984 May 21 18:08 /usr/lib/ruby/gems/1.8/gems/mysql-2.7.3-mswin32/ext/mysql.so Using the mysql module with Ruby on Windows outside Cygwin works well. What could be the reason for this problem? The first problem are the access rights. Shared libs must have the execute bits set. chmod +x mysql.so will help. This helped a lot! The second problem is that this shared lib has been created for the native win32 version of ruby, not for the Cygwin version. It *might* work together, but it's neither guaranteed, nor supported. ... which might explain the new behaviour, that the programs starts to run, but at the end gets a ~/thome/importer_tests $ onereq_oneappl.rb /usr/lib/ruby/gems/1.8/gems/mysql-2.7.3-mswin32/ext/mysql.so: [BUG] Segmentation fault ruby 1.8.6 (2007-03-13) [i386-cygwin] I see that I am here still on experimental ground. Maybe the idea of using mysql from within Cygwin-Ruby was really not so good in the first place Ronald -- Ronald Fischer [EMAIL PROTECTED] Phone: +49-89-452133-162 -- 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: mysql.so: Permission denied (Ruby under Cygwin)
Indeed, ugh. Who told you that, some random guy on ruby-talk or somebody who actually knows what (s)he's talking about? Someone at Ruby-Talk. I had a thread running last month under the Subject gem under cygwin - is it supposed to work?, because I already had different problems with using the Windows gem under Cygwin. I then got as an advice to use under cygwin gem install -r (I had left out the -r option before), so I assumed that, if I only get the options right, I can safely use the Windows gem for Cygwin too Ronald -- 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: mysql.so: Permission denied (Ruby under Cygwin)
/usr/lib/ruby/gems/1.8/gems/mysql-2.7.3-mswin32/ext $ cygcheck mysql.so Error: could not find mysql.so cygcheck is designed to check things on the PATH just as you would if you were invoking a command, so unless you have . in PATH it isn't expected to find anything in the PWD. H. But I do have . in the PATH - at the very end: $ echo $PATH /cygdrive/h/bin:/usr/local/bin:/usr/bin:/bin:/usr/X11R6/bin:/cygdrive/c/ Tcl/bin:/cygdrive/c/Programme/Java/jdk1.5.0_11/bin:/cygdrive/h/winbin:/c ygdrive/h/jruby-0.9.9/bin:/cygdrive/c/ruby185/bin:/cygdrive/c/Python24/: /cygdrive/c/Perl/bin/:/cygdrive/c/WINDOWS/system32:/cygdrive/c/WINDOWS:/ cygdrive/c/WINDOWS/System32/Wbem:/cygdrive/c/Programme/Utimaco/SafeGuard Easy/:/cygdrive/c/Programme/jEdit:/cygdrive/c/Programme/MySQL/MySQL Server 5.0/bin:/cygdrive/c/WINDOWS/system32/WindowsPowerShell/v1.0:/cygdrive/c/ jakarta-jmeter-2.2/bin:. You're mixing native win32 stuff with Cygwin stuff. You're trying to load the module into a running copy of a Cygwin ruby but this module imports symbols from the other copy of ruby in in C:\ruby185\. This means it probably expects data structures of the native build, and most likely will crash or act with very unpredictable behavior when used elsewhere. In general this kind of cross-polination is never a good idea. The *right* way to do it is to either stick to the win32 build (only) or to build all the components that you want to use as Cygwin modules. I understand! Thank you for the explanation. Ronald -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Problem reports: http://cygwin.com/problems.html Documentation: http://cygwin.com/docs.html FAQ: http://cygwin.com/faq/
Can not turn off terminal beep for completion
I have set my ~/.inputrc like this: set print-completions-horizontally on set show-all-if-ambiguous on set show-all-if-unmodified on set visible-stats on But still, when I, for example, enter ls TAB the terminal beeps. Even if I set in .inputrc: set bell-style none it beeps. This applies to rxvt and to the standard cygwin command line window. How can I turn off the beep? Ronald -- Ronald Fischer [EMAIL PROTECTED] Phone: +49-89-452133-162 -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Problem reports: http://cygwin.com/problems.html Documentation: http://cygwin.com/docs.html FAQ: http://cygwin.com/faq/
Can not get bash 8-bit-clean
Following the advice in http://cygwin.com/cygwin-ug-net/setup-files.html, I put the following commands into my .inputrc: set meta-flag on set convert-meta off set output-meta on Still, I can not enter 8-bit characters (such as German umlaut characters) in bash shells. What am I missing still? Ronald -- Ronald Fischer [EMAIL PROTECTED] Phone: +49-89-452133-162 -- 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: Can not turn off terminal beep for completion
Make sure your .inputrc is read. Hmmm according to the Cygwin documentation page: .inputrc controls how programs using the readline library (including bash) behave. It is loaded automatically. So, as long as I stick with the default name ($HOME/.inputrc), it should be read without requiring me to do additional actions, isn't it? Ronald -- Ronald Fischer [EMAIL PROTECTED] Phone: +49-89-452133-162 -- 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/
SOLVED: Can not turn off terminal beep for completion [Ruby programmers, read this!]
Theoretically, but there still could be a few things going wrong, one of which being that you and your Cygwin environment have different ideas of what $HOME is. At least, the environment variable HOME is set correctly, and also my ~/.bash_profile is read, so this suggests that bash *does* look for my HOME at the expected place. Try running bind 'set bell-style none' from the bash command line... Indeed, you are right: my .inputrc is not read - but the reason for it is really bizarre: I had installed cygwin together with the Ruby programming language. After this, I decided to also install the pure Windows version of Ruby. This installation, however, had the funny side effect to set on Windows the system-wide environment variable INPUTRC to a file 'c:\ruby185\bin\inputrc.euro'!!! My guess is that they use this file for the interactive Ruby shell (irb), but in any case, it means that when bash is started, it sees INPUTRC pointing to a different file and ignores my $HOME/.inputrc! Ronald -- Ronald Fischer [EMAIL PROTECTED] Phone: +49-89-452133-162 -- 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/
ruby for cygwin comes without gem command
I installed ruby for cygwin, using the cygwin setup program: $ ruby --version ruby 1.8.5 (2006-12-25 patchlevel 12) [i386-cygwin] To my surprise, this does not install the gem command, which is normally part of Ruby 1.8.5: $ which ruby /usr/bin/ruby $ ls /usr/bin/gem ls: cannot access /usr/bin/gem: No such file or directory How can I get the gem command for cygwin? Or can I simply use the gem command from the normal (Windows-) installation of Ruby? Ronald -- Ronald Fischer [EMAIL PROTECTED] Phone: +49-89-452133-162 -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Problem reports: http://cygwin.com/problems.html Documentation: http://cygwin.com/docs.html FAQ: http://cygwin.com/faq/
Error opening script file
I have installed the script language JRuby, which comes with two executables: A binary jruby, and a shell script jirb (for interactive purpose). I can call jruby, but I get an error message when calling jirb: ~/ruby_test $ ls -l $JRUBY_HOME/bin/jirb -rwxr-xr-x 1 rfischer mkgroup-l-d 323 Apr 23 23:30 /cygdrive/h/jruby-0.9.9/bin/jirb ~/ruby_test $ !$ $JRUBY_HOME/bin/jirb Error opening script file: \cygdrive\h\jruby-0.9.9\bin\jirb (Das System kann den angegebenen Pfad nicht finden) ~/ruby_test $ head -n 1 !$ head -n 1 $JRUBY_HOME/bin/jirb #!/usr/bin/env jruby From this dialogue, you can see that jirb has the correct x-permissions, but still the script file can't be opened. My guess is that bash can't load the correct interpreter file, so that's why I also have listed above the first line of the jirb script - but it seems that this is looking fine. Any ideas what is going wrong? (BTW, the German language error message above translates to: The system can't find the specified path. If someone happens to know how to convince Cygwin to use English error messages only, please let me know too (I thought this would depend on the settings of the LANG environment variable, but setting it to en doesn't seem to have any effect.) Ronald -- Ronald Fischer [EMAIL PROTECTED] Phone: +49-89-452133-162 -- 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/
Access of files using absolute path (was: Error opening script file)
Aside from the problem described in my original posting (see the quote at the end of this message), I found a related problem, which has nothing to do with the execution of a script, but which seems to suggest that I have a general problem in opening files by specifying absolute pathes. Here an example: I did a cd to drive C: $ pwd /cygdrive/c and I also have the following jar file: $ ls -l $PWD/jakarta-jmeter-2.2/bin/*jar -rwxrwxrwx+ 1 rfischer 9962 Jun 13 2006 /cygdrive/c/jakarta-jmeter-2.2/bin/ApacheJMeter.jar I can list the content of the jar file using RELATIVE path: /cygdrive/c $ jar tf jakarta-jmeter-2.2/bin/*jar META-INF/ META-INF/MANIFEST.MF org/ org/apache/ org/apache/jmeter/ org/apache/jmeter/DynamicClassLoader.class org/apache/jmeter/NewDriver$1.class org/apache/jmeter/NewDriver.class META-INF/LICENSE META-INF/NOTICE But I can NOT list its contents using absolute path: $ jar tf $PWD/jakarta-jmeter-2.2/bin/*jar java.io.FileNotFoundException: \cygdrive\c\jakarta-jmeter-2.2\bin\ApacheJMeter.jar (Das System kann den angegebenen Pfad nicht finden) at java.io.FileInputStream.open(Native Method) at java.io.FileInputStream.init(FileInputStream.java:106) at java.io.FileInputStream.init(FileInputStream.java:66) at sun.tools.jar.Main.run(Main.java:205) at sun.tools.jar.Main.main(Main.java:1022) Interestingly, I *can* open the file using, for example, od -x: $ od -x $PWD/jakarta-jmeter-2.2/bin/*jar| head -n 2 000 4b50 0403 000a a84a 34cd 020 0009 0004 454d So on this level, it seems that od and jar use different means to open a file. Now to quote my original problem, posted earlier: -Original Message- From: [EMAIL PROTECTED] Sent: Monday, May 07, 2007 3:29 PM To: cygwin@cygwin.com Subject: Error opening script file I have installed the script language JRuby, which comes with two executables: A binary jruby, and a shell script jirb (for interactive purpose). I can call jruby, but I get an error message when calling jirb: ~/ruby_test $ ls -l $JRUBY_HOME/bin/jirb -rwxr-xr-x 1 rfischer mkgroup-l-d 323 Apr 23 23:30 /cygdrive/h/jruby-0.9.9/bin/jirb ~/ruby_test $ !$ $JRUBY_HOME/bin/jirb Error opening script file: \cygdrive\h\jruby-0.9.9\bin\jirb (Das System kann den angegebenen Pfad nicht finden) ~/ruby_test $ head -n 1 !$ head -n 1 $JRUBY_HOME/bin/jirb #!/usr/bin/env jruby From this dialogue, you can see that jirb has the correct x-permissions, but still the script file can't be opened. My guess is that bash can't load the correct interpreter file, so that's why I also have listed above the first line of the jirb script - but it seems that this is looking fine. What is interesting here is that I *can* access jirb by absolute path using programs such as less or head: $ head -n 5 $JRUBY_HOME/bin/jirb #!/usr/bin/env jruby # # irb.rb - intaractive ruby # $Release Version: 0.7.3 $ # $Revision$ but I can not execute it using the jruby interpreter - neither implicitly, as shown above, nor explicitly: $ jruby $JRUBY_HOME/bin/jirb Error opening script file: \cygdrive\h\jruby-0.9.9\bin\jirb (Das System kann den angegebenen Pfad nicht finden) But this *is* possible using relative pathes: $ cd $JRUBY_HOME $ jruby bin/jirb irb(main):001:0 I experimented around with other applications. So far, I found that jar and jruby have the problem that they can't open a file if it is listed absolutely (/cygdrive/...), while for example ruby or zsh do not show this problem. So I first thought that maybe those applications have not been written with cygwin in mind - but then, they would have failed even with relative files - won't they? What is going on here? Ronald -- Ronald Fischer [EMAIL PROTECTED] Phone: +49-89-452133-162 -- 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/