Re: GitForWindows vs. Cygwin
2018-03-20 23:52 GMT+01:00 KARL BOTTS: > Can anyone enlighten me about the relationship of "Git for Windows" to > Cygwin? Depends on how you define "relationship". Tony summed it up very nicely. > I have no intention to use GFW myself: I use Cygwin git. But now other people > around here are discovering GitHub, MSysGit and or GitForWindows. Pretty > soon, we are going to wind up with multiple git flavors installed on the same > host, which worries me. I use the Cygwin based git tools (tig most of the time) as my main client, but also use Git for Windows and its tig, WSL based and real Ubuntu, the builtin git client in Visual Studio and VSCode. I often combine them in one project, for instance use VS for the simple and easy commit, use the Cygwin command line for more advance stuff and to push and pull (because I mainly use SSH). The **real caveat** is to get your line endings right. You need that figured out in any multi platform environment, and combining Windows bases git and Cygwin based git is exactly that. Cygwin and Ubuntu default to LF. Git for Windows and the VS clients default to CRLF. We use "git config --global core.autocrlf false" and combine that with a proper .gitattributes and .editorconfig file. So far that works quite well for us. Hope it helps, Frank -- Problem reports: http://cygwin.com/problems.html FAQ: http://cygwin.com/faq/ Documentation: http://cygwin.com/docs.html Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple
Re: [ANNOUNCEMENT] python-sphinx 1.6.5-1
2017-11-27 7:39 GMT+01:00 Yaakov Selkowitz: > The following packages have been uploaded to the Cygwin distribution: > > * python2-alabaster-0.7.10-1 > * python2-babel-2.5.1-1 > * python2-imagesize-0.7.1-1 > * python2-jinja2-2.9.6-1 > * python2-pytz-2017.3-1 > * python2-snowballstemmer-1.2.1-1 > * python2-sphinx-1.6.5-1 > * python2-sphinxcontrib-websupport-1.0.1-1 > * python2-sphinx_rtd_theme-0.2.4-1 > * python2-sqlalchemy-1.1.15-1 > * python2-typing-3.6.2-1 > * python2-whoosh-2.7.4-1 Sphinx worked fine for many years on my pc, but after upgrading today it is doesn't work anymore. $ make html Makefile:12: *** The 'sphinx-build' command was not found. Make sure you have Sphinx installed, then set the SPHINXBUILD environment variable to point to the full path of the 'sphinx-build' executable. Alternatively you can add the directory with the executable to your PATH. If you don't have Sphinx installed, grab it from http://sphinx-doc.org/. Stop. I tried to reinstall the python2-sphinx package from setup.exe but without any success. Indeed, in /bin there is no sphinx-build or sphinx-quickstart. Any thoughts? Regards, Frank -- 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 alongside WSL
2017-10-23 14:38 GMT+02:00 KARL BOTTS: > Does anybody have any concrete experience using Windows Subsystem for Linux > (hence WSL) on the same machine, alongside Cygwin? I'm using them both without much problems (on Creator Update, not on Fall Creator Update yet). I use them only for the command line. As mentioned the CMD is not the best, but it gets the job done. I am also looking into combining mintty and wsl, which takes some effort. Since the architecture is much different, wsl is much faster and has all the good stuff from the official Ubuntu repositories. But Cygwin is available on Win7 and on servers, and Cygwin has cygrunsrv, which wsl both lacks. And I use 'noacl' on my /cygdrive mounts. WSL lack something like that as well. That is really a big thing to me. I don't want a bash-script to mess up my file permissions, especially not on network drives where permissions can be crucial. WSL cannot mount network drives, at least in the version I'm using. I don't see myself choosing sides any time soon. Cygwin is still my favorite and most used. Regards, Frank -- 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
[ANNOUNCEMENT] Updated: shutdown 2.0-2
Hi, I've just updated the version of shutdown to v2.0-2 and it can be found at a server near you. This release fixes a build issue in the package. The 64-bit package actually contained a 32-bit shutdown.exe https://cygwin.com/ml/cygwin/2017-01/msg00194.html FULL CHANGELOG (since shutdown-1.10-1) == * Added --install to install Windows Updates during shutdown/reboot. The InitiateShutdown() Windows API call is used for this. This function is only available from Windows 6.0 (aka Vista or Server 2008) or higher. To assure backwards compatibility with WinXP and Server 2003, InitiateShutdown() is loaded dynamically at runtime. Since Cygwin 2.6 support for Windows XP and Server 2003 has been dropped, so this backward compatibility will be removed in a future release. * Added --hybrid to shutdown in hybrid mode. Hybrid is the default shutdown method with shutting down with the UI of Windows 8.x and higher. * The default shutdown messages will give more information on what is about to happen. * User can supply his own shutdown message on the command line. Enjoy! Regards, Frank -- Problem reports: http://cygwin.com/problems.html FAQ: http://cygwin.com/faq/ Documentation: http://cygwin.com/docs.html Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple
Re: [ANNOUNCEMENT] Updated: shutdown 2.0-1
2017-01-16 18:52 GMT+01:00 Achim Gratz: > There is a build or packaging error somewhere with the 64bit version: > the shutdown.exe delivered with the x86_64 package is in fact a 32bit > executable that refuses to work in 64bit Cygwin. Can you please correct > and re-release the package? Thanks for spotting. There was a problem in the Makefile. I will re-release the package ASAP. Regards, Frank -- 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
[ANNOUNCEMENT] Updated: shutdown 2.0-1
Hi, I've just updated the version of shutdown to v2.0-1 and it can be found at a server near you. FULL CHANGELOG (since shutdown-1.10-1) == * Added --install to install Windows Updates during shutdown/reboot. The InitiateShutdown() Windows API call is used for this. This function is only available from Windows 6.0 (aka Vista or Server 2008) or higher. To assure backwards compatibility with WinXP and Server 2003, InitiateShutdown() is loaded dynamically at runtime. Since Cygwin 2.6 support for Windows XP and Server 2003 has been dropped, so this backward compatibility will be removed in a future release. * Added --hybrid to shutdown in hybrid mode. Hybrid is the default shutdown method with shutting down with the UI of Windows 8.x and higher. * The default shutdown messages will give more information on what is about to happen. * User can supply his own shutdown message on the command line. Enjoy! Regards, Frank -- Problem reports: http://cygwin.com/problems.html FAQ: http://cygwin.com/faq/ Documentation: http://cygwin.com/docs.html Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple
Re: [ANNOUNCEMENT] Updated: OpenSSH-7.4p1-1
2016-12-20 21:44 GMT+01:00 Corinna Vinschen: > * The next release of OpenSSH will remove support for running sshd(8) >with privilege separation disabled. Just noticed this. Not sure what that means for Cygwin ssh servers. I think I did the right thing when I installed ssh on my servers back in the day, but any advise on how to see what choices I mad? Regards, Frank -- Problem reports: http://cygwin.com/problems.html FAQ: http://cygwin.com/faq/ Documentation: http://cygwin.com/docs.html Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple
Re: [ANNOUNCEMENT] vim 7.4.2367-1
2016-09-20 18:42 GMT+02:00 Yaakov Selkowitz: > The following packages have been uploaded to the Cygwin distribution: > > * vim-7.4.2367-1 Any specific reason why you didn't upgrade to the new 8.0 release? Regards, Frank -- 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
Suggestion for chere
Hi Dave, I have a suggestion for chere. It would be really nice if the Cygwin icon/logo would be shown in front of the menu entry. Right now I only have one "Bash Prompt Here" menu item, but other bash implementations (MSYS2, Windows Git) also have a chere-like feature. They add there icon in front of the menu item. Take a look at this github issue: https://github.com/Microsoft/BashOnWindows/issues/603 It shows two variants of "bash here" in the context menu. Adding the icon is not that hard. See the .reg sample below. Just add an extra entry named "Icon" with a full path to the Cygwin.ico file. [HKEY_CLASSES_ROOT\Directory\Background\shell\cygwin64_bash] @="&Bash Prompt Here" "Icon"="C:\\Cygwin\\Cygwin.ico" If you want to make this optional, the command line flag -I (capital i) is the most logical available letter. Regards, Frank -- Problem reports: http://cygwin.com/problems.html FAQ: http://cygwin.com/faq/ Documentation: http://cygwin.com/docs.html Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple
Re: [ANNOUNCEMENT] Updated: mintty 2.4.3 and test release mintty 2.5.0
2016-08-23 1:29 GMT+02:00 Thomas Wolff: > I have also uploaded mintty 2.5.0 as a test release with the following > change: > > * Revise DPI handling (#470; #492, #487); always consider individual > monitor DPI. > > Note that this release introduces a slightly incompatible change in mintty. > The issue is that the interpretation of font size used to be suitable for > traditional resolution monitors and did not consider higher-DPI monitors or > the Windows monitor "zooming" feature which adjusts a virtual DPI. > As a result, the handling of changed DPI (when moving the window to another > monitor) introduced in 2.2.1 interfered with other aspects, the initial DPI > was not considered, and a number of unpleasant side effects were > occasionally observed. > > I intend to change DPI handling to be consistent with the respective monitor > DPI (as optionally configured by "zooming factor"), and to comply with font > size interpreation of other applications, e.g. notepad. In consequence the > initial font size may be smaller (or larger) than before, depending on the > actual monitor geometry and configuration. Nothing would change on a > "standard" monitor configuration. To compensate, some people may have to > change their font size configuration. I was about to write a bug report that I encountered with a maximized mintty on a 125% secondary screen. When I minimized it to the taskbar it would restore to my primary screen. But that problem is fixed now, so for me 2.5.0 solves that problem even before reporting it. The draft mail is thrown away ;-) Thanks for the fix! Frank -- 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 mintty window position
2016-08-12 6:04 GMT+02:00 Brent: > Thomas Wolff wrote: >>How about mintty -w max or -w full instead? > > Thanks, I am going to try that tomorrow. I'm not use, but I think Thomas meant that as a possible yet to be written command line option. Regards, Frank -- 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
GitHub shutdown repo
Hi, I recently transferred my shutdown repo from my personal github acoount to the cygwin organization. Could anybody with the right permissions rename the repo to just "shutdown"? Regards, Frank -- 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 gem install falis
Hi, I am unable to install a gem: # gem install gollum ERROR: Loading command: install (LoadError) No such process - /usr/lib/ruby/2.2.0/openssl.so ERROR: While executing gem ... (NoMethodError) undefined method `invoke_with_build_args' for nil:NilClass When I try "gem update" the same error occurs. >From what I read on various sites on the internet is that Ruby needs to be rebuild with the latest openssl. A new version of the openssl package was released recently. I have very little experience with Ruby. Just using some software that need to be installed as gems. Is rebuilding something I can do myself or does the Ruby packages needs to be rebuild? Regards, Frank -- Problem reports: http://cygwin.com/problems.html FAQ: http://cygwin.com/faq/ Documentation: http://cygwin.com/docs.html Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple
Re: [ANNOUNCEMENT] Early Deprecation Notice: Windows XP and Server 2003 support
2015-08-26 15:42 GMT+02:00 Andrey Repin: > And since Vista+ doesn't have support for 16-bit subsystem, I need XP VM to > compile my projects. AFAIK the 16-bit subsystem has nothing to do with XP vs Vista+. It has to do with 32-bit OS vs 64-bit OS. Have you tried a 32 bit Win7 (or maybe even a 32-bit Win10)? Regards, Frank -- 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: mintty project
2015-06-04 8:29 GMT+02:00 Thomas Wolff: > I have acquired that account meanwhile but apparently it cannot be turned > into an org. account, rather it would need to be attached to a separate org. > account (weird policy). Does this help? https://help.github.com/articles/converting-a-user-into-an-organization/ > Actually there is also an orphaned github account called "cygwin" which > could be claimed by a cygwin maintainer (Corinna?), maybe as an option to > host cygwin packages. Suggested that as well in my previous mail. > Apart from that, I am still hesitating to go with github.com. What do people > think about gitlab.com instead? It makes a more serious impression and has > some more professional features. Or maybe codebase.com? I cannot tell you anything about the other sites you mention. But I know that the community is at github at the moment. Many examples exist. See the graph Tony posted. I experienced it myself as well. Or see the "Our choice of using GitHub" section on this blogpost of Microsoft http://blogs.msdn.com/b/dotnet/archive/2014/11/12/net-core-is-open-source.aspx I am sure the community will build around mintty, once people start to noticed the move. And for that ask Andy to put a link to the new repo on the Google Code page. Regards, Frank -- 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: mintty project
2015-06-01 10:36 GMT+02:00 Corinna Vinschen: > On May 31 23:15, Thomas Wolff wrote: >> As a contributor to mintty, some sent me a notice discussing the move to >> github >> (http://www.reddit.com/r/cygwin/comments/37vgwi/what_happened_to_minttys_maintainer_andy_kopp/) >> and now there is already a github fork of mintty >> (https://github.com/nowox/mintty/tree/master/src). I see that "nowox" only imported the repo from Google Code very recently, most likely by simply pressing the "Export to GitHub" button on Google Code. And didn't make much "real changes" to his repo so far. >> I'd like to discuss what you (cygwin maintainers and others) think of this >> move, whether it's good for mintty to be hosted on github. Personally I feel >> that a platform like sourceforge provides a more professional project >> environment which would provide more confidence in stable project >> development. >> What do you think? I agree with Tony. Although I am still using the SF alias as one of my email addresses I think at this moment GitHub has the most active community. If you want to have a greater change on others contributing I would really go for GitHub. Seen it happen so many times already, move a project to GH and the PRs start coming. > It's not so much the hosting service providing the upstream repository > which concerns me, it's the lack of development, the lack of a responsive > maintainer, and the lack of a new, stable mintty package. You're in for > one of the newly created pink plush hippos if you're going to take over > mintty maintainership ;) > > Having said that, github is ok. Would it be useful for cygwin to have its own place on GitHub? This could be the place to host the mintty sources and maybe other things as well. There is a user named "cygwin" on github, but it appear very inactive. https://github.com/cygwin GitHub has a policy for that: https://help.github.com/articles/name-squatting-policy/ So if interested, maybe Corinna or Yaakov (being our project leaders) could ask GitHub to hand that account to them. And after that turn it into an organization where projects like this can be hosted. This way the project doesn't depend on one person to have full access when needed to these kind of repos. Just an idea. Regards, Frank -- 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: multitail segfaults
2015-04-23 11:04 GMT+02:00 Dr. Volker Zell: > > Subject: Re: multitail segfaults > > I also have this problem when I use multitail. > > > $ multitail --version > > --*- multitail 6.3 (C) 2003-2014 by folk...@vanheusden.com -*-- > > > The following problem occured: > > - > > [1]10832 segmentation fault (core dumped) multitail --version > > > For me it works on 32bit cygwin, but on 64bit I get an error: > > xclip binary 'xclip' does not extist > > and in fact 32bit has /usr/bin/xclip installed but in 64bit it's missing Manually installing xclip solves the crash for me. So while you are on it, could you please update the dependencies of the multitail package? Regards, Frank -- Problem reports: http://cygwin.com/problems.html FAQ: http://cygwin.com/faq/ Documentation: http://cygwin.com/docs.html Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple
Re: [ANNOUNCEMENT] Updated: vim-7.4.692-1
2015-04-13 17:19 GMT+02:00 Yaakov Selkowitz: > The following packages have been updated in the Cygwin distribution: > > * vim-7.4.692-1 > * vim-common-7.4.692-1 > * vim-minimal-7.4.692-1 > * xxd-7.4.692-1 > * gvim-7.4.692-1 > > Vim is an advanced text editor that seeks to provide the power of the > de-facto Unix editor 'Vi', with a more complete feature set and a choice > of terminal and GTK+ interfaces. > > This is an update to the latest upstream patchset. Is it by design that vim now requires tcsh? tcsh(6.18.01-6) An enhanced version of csh, the C shell Required by: vim-common Regards, Frank -- 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: Clean up /tmp on system reboot [was: Xorg server always starting up on DISPLAY 3.0]
2015-04-10 22:38 GMT+02:00 Andrew DeFaria: >> $ man 5 crontab >> >> See @reboot >> >> Never used it but I assume it will run after cron service is started. > > I haven't used it either, but I saw it there. Makes you wonder what would > happen if you simply restarted the service or stopped it and then started it > again. Have cron installed on my laptop so I just tested. And yes, that is how @reboot works on Cygwin. It runs the job right after the cron daemon is started, regardless how many times you restart the service. On Linux it seems to detect that the system really was rebooted. Regards, Frank -- 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
multitail segfaults
Hi, I'm experiencing a problem with multitail. It always gives a segmentation fault. $ multitail --version --*- multitail 6.3 (C) 2003-2014 by folk...@vanheusden.com -*-- The following problem occured: - Segmentation fault (core dumped) I see this behavior on all my installations. cygcheck -srv doesn't show anything special. After downgrading to the previous version (5.2.12) it works again. Anyone else seeing the same problem? Regards, Frank -- 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 Git thinks files are changed when they aren't
2015-03-24 21:42 GMT+01:00 Chloe: > Cygwin Git always thinks files are changed even when they aren't. After a > commit with a Windows Git, Cygwin Git shows files as modified. > [snip] > $ git diff .project > diff --git a/.project b/.project > old mode 100644 > new mode 100755 Apart from the file mode already mentioned, don't forget that Windows based git uses CRLF as line endings where Cygwin git uses LF as default line ending (like a Linux based git). Could lead to "modified" files as well. I avoid mixed the two as much as possible. I use Cygwin git to do all the real operations and use TortoiseGit (together with Windows based git) just to see in the Windows Explorer what is happening in my directories. There is a tweak introduced in the most recent TortoiseGit to use Cygwin git, but have tried that yet. Regards, Frank -- 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: rsync still broken
2015-03-12 21:34 GMT+01:00 Linda Walsh: > It sounds like the group you are in on cygwin doesn't exist or you are not > in it on your target machine. > > what group are you in on the windows machine? > if you type 'id', the 2nd number should be your primary gid. > > uid=1234(Bliss\law) gid=123(lawgroup) groups=123(lawgroup)... The first gid of the user running the rsyncd service is 512, but... > Then the question is, does your groupname > exist on the server you are transferring it to? (or if you are using > '--numeric-ids, is your > group# (gid) the same on the server you are transferring files to? ... I use --numeric-ids and I have these two lines in the rsyncd.conf uid = 0 gid = 0 If I understand it correctly now rsync sends all files with uid=0 and gid=0. And obviously those uid and gid exist on the Linux machine. > If not, are you using the --usermap and/or > --groupmap options to map your Windows ID's to > your server's ID's? No, I don't use that. > Maybe you have already verified this, but usually > when I get errors in a transfer, it's because the UID's > or user/groupnames on my windows machine don't always match > what is on my server -- they mostly do, but I do see > errors occasionally in it trying to set things. I thought uid=0 and gid=0 would solve that. > You can also try the --fake-super option -- that > might fake the id's enough for it to work... There is a "fake super = yes" in the rsyncd.conf and the --fake-super option is added on the Linux server. But the thing that surpises me is that in 3.0.9 is just worked. Regards, Frank -- 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
rsync still broken
Hi Jari, It looks like rsync is still broken. When you released 3.1.0 it had an upstream bug that made it extremely slow on cygwin. Other then that it also had another problem that I reported here: https://www.cygwin.com/ml/cygwin/2014-08/msg00440.html Yaakov made 3.1.0 test and we all automatically reverted to 3.0.9. Recently 3.1.1 was released leaving the broken test version 3.1.0 as previous. I didn't update my servers yet, The day before yesterday I did, so I went from 3.0.9 to 3.1.1. And yesterday I saw that my backup *completely* failed because of these errors: @ERROR: setgid failed rsync error: error starting client-server protocol (code 5) at main.c(1653) [Receiver=3.1.0] ERROR: /usr/bin/rsync returned 5 while processing rsync://192.168.200.208/backup-d/DataShares/ @ERROR: setgid failed rsync error: error starting client-server protocol (code 5) at main.c(1653) [Receiver=3.1.0] ERROR: /usr/bin/rsync returned 5 while processing rsync://192.168.200.208/backup-d/DataGit/ @ERROR: setgid failed Very similar error as I reported for 3.1.0. FYI, I run the cygwin based rsync daemon on my Windows servers and have a Ubuntu server that backups the data with rsnapshot (which utilizes rsync to do the transfers). The errors above are shown on the Ubuntu server. Luckily I still had a 3.0.9 executable on one machine and I've put that exe on all the updated servers to make sure the backup worked again last night. So those systems new think they have 3.1.1 but the actually have the exe of good old properly working 3.0.9 Note that 3.0.9 is not available on the mirrors anymore. I hope that it can be restored on the mirrors and made current again for the time being and that this you have time to look into this problem. But the bottom line is that 3.1.x breaks my backup. Regards, Frank -- Problem reports: http://cygwin.com/problems.html FAQ: http://cygwin.com/faq/ Documentation: http://cygwin.com/docs.html Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple
Re: [ANNOUNCEMENT] TEST RELEASE: Cygwin 1.7.35-0.4
2015-02-25 13:51 GMT+01:00 Corinna Vinschen: > Another important change in this release is a change to chmod. As many > of you experienced since Cygwin 1.7.34, chmod does not always affect the > POSIX permission mask as returned by stat(2) or printed by ls(1), due to > the improved POSIX ACL handling. As a temporary workaround, chmod now > checks if secondary groups and users in the ACL have more permissions > than the primary group. If so, the permissions of the secondary users > and groups will be reduced according to the mask given by the new > primary group permissions. I.e, chmod 600 will remove all permissions > from the primary group as well as all secondary user and group entries > in the ACL. I have problems running screen on my pc. When I start it, it complains about the mode of the temporary directory. "Directory /tmp/uscreens/S-Frank must have mode 700." With 1.7.35-0.3 I could not chmod the directory manually. I just upgraded to 1.7.35-0.4 and now I can manually chmod the directory to 700 and start screen again. But IFAIK previously (not sure when) screen was able to chmod the directory itself, but now not anymore. Regards, Frank -- 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-host-config script sends /etc/passwd thru awk
2015-02-18 15:00 GMT+01:00 Corinna Vinschen: > > The openssh is the 64-bit version, as in the stackexchange user's case. > > The issue is interesting, though. When I first installed the openssh, it > > offered me "prev" version of the package, even though I was installing from > > the net. Re-running the installer picked the "current" version. > > Setup.exe glitch? > > No idea. Mirror problem? I never encountered the problem myself. Seen this behavior as well last week, when I installed a new package. But didn't take real notice until I read this thread. At this moment I don't have cvs2svn installed. When I select it in setup it will show 2.3.0-1, which is mentioned as [prev] in the downloaded setup.ini. When I click it again it will select 2.4.0-1, the current version in setup.ini Regards, Frank -- 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: RFC: 1.7.33 problem with user's home directory
2014-11-11 1:45 GMT+01:00 Andrey Repin: > I see literally zero reason to maintain separate, cygwin-specific "home" > directory. I think I have to disagree with you. When mixing MSYS, msysGit and Cygwin in the same home directory the dot-files can become a problem. Especially when it comes to line ending in those files and the line ending setting in .gitconfig. Regards, Frank -- 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: vim can't write /etc/hosts
2014-09-07 17:00 GMT+02:00 Andrey Repin: > Adding to what other people said, most self-respecting antivirus applications > explicitly block access to system hosts file. > For obvious reasons. > If you absolutely NEED to modify it, and can't resolve your issues in any > other way, disable hosts file protection first. Just to make sure I just disabled Kaspersky and tested again. That is not the cause of this problem. It would have surprised me a lot, since nano and the echo command work as expected. Regards, Frank -- 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: vim can't write /etc/hosts
2014-09-05 4:33 GMT+02:00 Darik Horn: > On Thu, Sep 4, 2014 at 4:33 PM, Frank Fesevur wrote: >> >> Why can't vim write the file, or even better the symlinked file? I'm >> quite sure editing the symlink works in Win7, but can try tomorrow. > > Starting "C:\Cygwin\bin\mintty.exe" through a "Run As Administrator" > context doesn't produce an elevated bash prompt on my Windows 8 > workstation. > > Starting the "Command Prompt (Admin)" shortcut instead and running > "C:\Cygwin\bin\bash.exe --login" inside should give you the expected > behavior. There is no difference (for me) between starting mintty or cmd as administrator. With Win7 it *has* worked but not anymore. This method is *the* way for me to change the hosts file, because of the short path. "nano /etc/hosts" works without a problem on both Win7 and Win2012R2 (no Win81 at the office). The described echo command works fine. So write access should not be the problem. Only vim has these problems with the hosts file. I don't know if it is relevant, but I've added noacl to the /cygdrive entry of my fstab. Regards, Frank -- Problem reports: http://cygwin.com/problems.html FAQ: http://cygwin.com/faq/ Documentation: http://cygwin.com/docs.html Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple
Re: [ANNOUNCEMENT] Updated: mingw64-{headers,runtime,winpthreads} w32api-* 3.2.0-1
2014-09-01 13:50 GMT+02:00 JonY: > Now released for both 32bit and 64bit Cygwin: > > mingw64-*-headers-3.2.0-1 > mingw64-*-runtime-3.2.0-1 > mingw64-*-winpthreads-3.2.0-1 > w32api-headers-3.2.0-1 > w32api-runtime-3.2.0-1 I see my patch is in included this release. Thanks for updating! Now I have no excuse anymore not to update the shutdown package ;-) Regards, Frank -- 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
vim can't write /etc/hosts
Hi, On my Win81 machine I tried to edit /etc/hosts with vim. When I try to write the file I get this error: "/etc/hosts" E166: Can't open linked file for writing Since /etc/hosts is a symlink to /cygdrive/c/windows/System32/drivers/etc/hosts so I tried to edit the file with the full path but that fails as well: "/cygdrive/c/windows/System32/drivers/etc/hosts" E212: Can't open file for writing I did all this with my mintty started as administrator: uid=1000(Frank) gid=513(Geen) groups=513(Geen),0(root),544(Administrators),545(Gebruikers) I can edit the file starting my Notepad++ as administrator and open file. A bit surprising but this works: Frank@PC7 /cygdrive/c/Windows/System32/drivers/etc # echo "# test" >> hosts Why can't vim write the file, or even better the symlinked file? I'm quite sure editing the symlink works in Win7, but can try tomorrow. Regards, Frank -- 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: rsyncd broken
2014-08-25 9:46 GMT+02:00 Frank Fesevur: > 2014-08-22 14:42 GMT+02:00 Frank Fesevur: >> I will try a self build vanilla rsync.exe 3.1.1 this weekend or early >> next week and see how that works. > > I have tried my own build 3.1.1 last night and it fails with the same > errors. I will investigate this. Made a bit of progress. When I comment out the lines uid = 0 and gid = 0 from my /etc/rsyncd.conf v3.1.1. seems to work again, although I haven't tried on our production server yet. I rather wait with that until the weekend when there is not much to backup. I have not found out why this behavior has changed since v3.0.9. Another thing that surprises me is that the setuid() fails with an errno 5, which is EIO. That error is not mentioned on this man page http://linux.die.net/man/2/setuid What do you think? Is this setuid() error a cygwin specific problem or should I ask upstream? Regards, Frank -- 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: rsyncd broken
2014-08-22 14:42 GMT+02:00 Frank Fesevur: > I will try a self build vanilla rsync.exe 3.1.1 this weekend or early > next week and see how that works. I have tried my own build 3.1.1 last night and it fails with the same errors. I will investigate this. Regards, Frank -- 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
rsyncd broken
Jari, As I reported earlier rsync 3.1.0 is broken on cygwin. http://www.cygwin.com/ml/cygwin/2014-06/msg00212.html http://www.cygwin.com/ml/cygwin/2014-06/msg00442.html Any news on that issue yet? We run cygwin rsync daemons on our Windows servers and have a remote Ubuntu server that backups the important data using rsnapshot. Earlier this week I accidentally upgraded from 3.0.9 to your 3.1.0 on one of our servers and that night the backup failed with these (client side) error. @ERROR: setuid failed rsync error: error starting client-server protocol (code 5) at main.c(1653) [Receiver=3.1.0] ERROR: /usr/bin/rsync returned 5 while processing rsync://192.168.202.230/backup-d/DataWeb/ @ERROR: setuid failed rsync error: error starting client-server protocol (code 5) at main.c(1653) [Receiver=3.1.0] ERROR: /usr/bin/rsync returned 5 while processing rsync://192.168.202.230/backup-d/wwwroot/ I reverted to 3.0.9 and it works as expected again. But these error don't seem to be related to the 3.1.0 performance issues, so do you have any idea why it fails? Could the additional debian patch you've added cause this? I will try a self build vanilla rsync.exe 3.1.1 this weekend or early next week and see how that works. Regards, Frank -- 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
InitiateShutdown() misses in winreg.h
Hi, I want to add support for the hybrid shutdown of Win8 to the shutdown package. I need to use the InitiateShutdown() function and its defines for this: http://msdn.microsoft.com/en-us/library/windows/desktop/aa376872%28v=vs.85%29.aspx But /usr/include/w32api/winreg.h doesn't not have these declarations yet. I see this file is from the mingw-w64 project. What is the best way to get these declarations added to this file? Does our mingw-w64 maintainer has direct access to their git? If so, could he add them? Or should I supply an upstream patch myself? And yes, I am aware that Vista is a minimum requirement for InitiateShutdown(). Regards, Frank -- 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
man doesn't work after update
Hi, Today I updated a server and ran into a problem. $ man shutdown man: can't execute iconv: No such file or directory man: command exited with status 127: iconv -c -f UTF-8 -t ISO-8859-1//TRANSLIT | (cd /home/Administrator && LESS=-ix8RmPm Manual page shutdown(8) ?ltline %lt?L/%L.:byte %bB?s/%s..?e (END):?pB %pB\%.. (press h for help or q to quit)$PM Manual page shutdown(8) ?ltline %lt?L/%L.:byte %bB?s/%s..?e (END):?pB %pB\%.. (press h for help or q to quit)$ MAN_PN=shutdown(8) less -s) After manually installing "libiconv" (libiconv2 was already installed) the problem disappeared, so apparently there is a dependency missing for man-db. Regards, Frank -- 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: Re: [ANNOUNCEMENT] Updated: rsync 3.0.9-1 -- fast, versatile file synchronizing tool
Roland, Please send your replies to the list! 2014-07-28 22:18 GMT+02:00 Roland Kletzing: >>Did you know that 3.1.0 has performance issues on cygwin? See almost >>at the bottom of the "BUG FIXED" at >>http://rsync.samba.org/ftp/rsync/src-previews/rsync-3.1.1pre2-NEWS > > if you refer to > > - Switched Cygwin back to using socketpair "pipes" to try to speed it up. Yes, that is what I was referring to. > then its not a performance issue of 3.1.0 but the issue is much older, see > https://bugzilla.samba.org/show_bug.cgi?id=10322 and > http://git.samba.org/rsync.git/?p=rsync.git&a=search&h=HEAD&st=commit&s=socketpair All I did was: grabbed the 3.0.9 source package from the cygwin mirror. Build it and ran "cygport test" and all test succeeded (some were skipped). After that I updated that cygport file, downloaded and build 3.1.0 and ran "cygport test". Some test failed. With 3.1.1pre1, pre2 and 3.1.1 release it worked again. So for me there was a cygwin related bug in 3.1.0 and was fixed in 3.1.1, just like it says in NEWS. > btw, maybe someone has a clue why cygwin rsync build lost xattr support? > http://marc.info/?l=rsync&m=140653072002534&w=2 ? I don't know. Just used the vanilla build options. So apparently the developers of rsync disabled xattr on cygwin. Regards, Frank -- Problem reports: http://cygwin.com/problems.html FAQ: http://cygwin.com/faq/ Documentation: http://cygwin.com/docs.html Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple
Re: [ANNOUNCEMENT] Updated: rsync 3.0.9-1 -- fast, versatile file synchronizing tool
2014-06-17 14:16 GMT+02:00 Frank Fesevur: > 2014-06-17 10:57 GMT+02:00 Jari Aalto: >> PACKAGE DESCRIPTION >> === >> >> Homepage: http://freecode.com/projects/rsync >> License : GPL-3+ >> >> Fast and versatile file-copying tool which can copy locally and >> to/from a remote host. It offers many options to control its behavior, >> and its remote-update protocol can minimize network traffic to make >> transferring updates between machines fast and efficient. It is widely >> used for backups and mirroring and as an improved copy command for >> everyday use. > > Jari, you announced 3.0.9-1 which was the version already available, > but you uploaded 3.1.0-1. I assume a copy-paste error. > > Did you know that 3.1.0 has performance issues on cygwin? See almost > at the bottom of the "BUG FIXED" at > http://rsync.samba.org/ftp/rsync/src-previews/rsync-3.1.1pre2-NEWS > > I tried to build rsync a while ago myself using cygport (I even > considered to ITA when 3.1.1 would be final). But when I ran "cygport > test" 6 test (batch-mode, chmod-option, exclude, hands, itemize and > symlink-ignore) fail with timeouts. > > The 3.1.1pre1 fixes these issues. All the test that fail with 3.1.0 > pass with 3.1.1pre1. I haven't tried to test your version. > > And why is http://freecode.com/projects/rsync mentioned as homepage > and not http://rsync.samba.org/? > > Regards, > Frank Jari, Any news on the stability-issues in rsync 3.1.0? 3.1.1 has been released a week ago. 3.1.1 passes all the test. If you are interested, this is my cygport-file: https://github.com/ffes/cygwin-pkgs/blob/master/rsync/rsync.cygport Regards, Frank -- Problem reports: http://cygwin.com/problems.html FAQ: http://cygwin.com/faq/ Documentation: http://cygwin.com/docs.html Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple
Re: [ANNOUNCEMENT] Updated: rsync 3.0.9-1 -- fast, versatile file synchronizing tool
2014-06-17 10:57 GMT+02:00 Jari Aalto: > PACKAGE DESCRIPTION > === > > Homepage: http://freecode.com/projects/rsync > License : GPL-3+ > > Fast and versatile file-copying tool which can copy locally and > to/from a remote host. It offers many options to control its behavior, > and its remote-update protocol can minimize network traffic to make > transferring updates between machines fast and efficient. It is widely > used for backups and mirroring and as an improved copy command for > everyday use. Jari, you announced 3.0.9-1 which was the version already available, but you uploaded 3.1.0-1. I assume a copy-paste error. Did you know that 3.1.0 has performance issues on cygwin? See almost at the bottom of the "BUG FIXED" at http://rsync.samba.org/ftp/rsync/src-previews/rsync-3.1.1pre2-NEWS I tried to build rsync a while ago myself using cygport (I even considered to ITA when 3.1.1 would be final). But when I ran "cygport test" 6 test (batch-mode, chmod-option, exclude, hands, itemize and symlink-ignore) fail with timeouts. The 3.1.1pre1 fixes these issues. All the test that fail with 3.1.0 pass with 3.1.1pre1. I haven't tried to test your version. And why is http://freecode.com/projects/rsync mentioned as homepage and not http://rsync.samba.org/? Regards, Frank -- 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: Updated: rsync 3.0.9-1 -- fast, versatile file synchronizing tool
2014-06-17 12:37 GMT+02:00: > Just out of curiosity does 3.1.0 have issues? Yes, it is very slow on cygwin. Various tests fails. 3.1.1pre1 works as expected (haven't tried pre2). But I think Jari wants to wait for the official release of 3.1.1 Regards, Frank -- 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: Change PS1 when running as administrator
2014-06-16 21:06 GMT+02:00 Achim Gratz: > Frank Fesevur writes: >> When I run as administrator I change my PS1 from "$" to "#" with these >> line in ~/.bashrc. >> >> if id -Gn | grep -i Administrators > /dev/null > > If anything I'd check for membership in group 544. "Administrators" > surely is one of these strings that gets localized depending on the > phase of the moon or something. I can't look right now, but I'm pretty > sure it says "Administratoren" in a german Windows version. On all my Dutch Windows all group names are localized apart from 544/Administrators. # id uid=1000(Frank) gid=513(Geen) groups=513(Geen),0(root),544(Administrators),545(Gebruikers) But I agree checking the numeric value is better. >> If more people like this idea, maybe it could included in /etc/bash.bashrc? > > I'll have to think about it, but I lean toward putting it into profile.d > instead. Thanks for considering. The other PS1 setting (user@host dir) is also in bash.bashrc. That's why I suggested bash.bashrc. Regards, Frank -- 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: Change PS1 when running as administrator
2014-06-16 21:00 GMT+02:00 Chris J. Breisch: > You might want to look at this thread: > https://sourceware.org/ml/cygwin/2014-04/msg00256.html Thanks for showing this threads. Missed it back then. > I use the registry test, but the id method would also work. I think the id command is a better way since it tells you that the user is member of the administrator group. That really tells you what you need to know. But the registry trick will work almost always, I sure :-) Regards, Frank -- 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
Change PS1 when running as administrator
Hi, I recently bought a new home computer, so I switched from XP to Win81. With Win81 every now and then I need to start cygwin as administrator (right click shortcut or tile, run as administrator) to do things that I can't do as a normal user. When I run as administrator I change my PS1 from "$" to "#" with these line in ~/.bashrc. if id -Gn | grep -i Administrators > /dev/null then PS1='\[\e]0;\w\a\]\n\[\e[32m\]\u@\h \[\e[33m\]\w\[\e[0m\]\n# ' else PS1='\[\e]0;\w\a\]\n\[\e[32m\]\u@\h \[\e[33m\]\w\[\e[0m\]\n\$ ' fi I don't know if the test can be done a better/easier way, but it works for me on a Dutch Win81. I tested it with both 1.7.30 and a recent AD/SAM snapshot. If more people like this idea, maybe it could included in /etc/bash.bashrc? Regards, Frank -- 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: Testers needed: New passwd/group handling in Cygwin
2014-03-03 10:21 GMT+01:00 Corinna Vinschen: > No, this is not mintty's fault. You have to understand that the > request for information from the DC is called before the actual > application had any chance to initialize, This happens before > the application has, in fact, been called from the Cygwin DLL. Understood. > Therefore, if the three seconds are a burden, there are three choices > going forward: > > - We reduce the timeout to 1 second in general, which could be a problem > when utilizing a slow VPN conncetion to the DC, > > - We allow the user to specify a timeout value and set the default to > 1 second. > > - We stick to the 3 seconds and users should switch to files (/etc/passwd > /etc/group) when being offline from their DC. > > I'm really not sure what the best way is, I guess we as a community have > to dice this out somehow. I think the second one makes most sense. Maybe even keep the default timeout on 3 seconds. When the user can change the value, it is up to them to play with it and figure out what works best for them. I personally would try to set it to 1 second, since I almost never have a slow VPN. Regards, Frank -- 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: Testers needed: New passwd/group handling in Cygwin
2014-02-28 22:08 GMT+01:00 Corinna Vinschen: > That's not really a problem but a case of "it is as it is". To get the > user and group info, Cygwin has to contact the DC and/or GC and then > runs into a timeout. Right now, the LDAP timeout is set to 3 seconds. > I don't know yet if it's such a bright idea to lower this timeout value. I understand why it happens. And three seconds are not the problem. It is just a bit confusing to activate the shortcut and for 3 seconds nothing seems to happen. First time I double-clicked again because I though it wasn't working at all. Obviously a bit later two terminal showed up. If mintty would should up empty and "wait" those three seconds before something happens it is more clear it just takes some startup time. But maybe that is more a mintty problem. Regards, Frank -- 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: Testers needed: New passwd/group handling in Cygwin
2014-02-28 18:14 GMT+01:00 Corinna Vinschen: > I made some tests myself today, while debugging Frank's problem. If I I updated to the snapshot of today (28th) and now the message is not shown anymore. Thanks for the fix. I have yet another observation. When I am not connected with VPN it takes a while (don't know how to time exactly, around 3 seconds) after I double click the shortcut for mintty to show up. When connect it shows up almost instantly. Tested 24th, 27th and 28th snapshots and see the problem with all of them. Regards, Frank -- 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: Testers needed: New passwd/group handling in Cygwin
2014-02-13 15:38 GMT+01:00 Corinna Vinschen: > This is a pretty intrusive change, in need of some serious testing, so > I'd like to ask for volunteers. The latest 2014-02-13 snapshot from > http://cygwin.com/snapshots/ contains the changes, including the latest > bugfix. I noticed another thing. Not sure if I would call it a problem, just an observation or if it is a feature. As said before, my laptop is part of a domain and I have moved the local passwd and group out of the way. When I am not connected to the domain (on the road) I get this error every time I start mintty: "id: kan geen naam vinden bij groeps-ID 1049089" I have an export LANG=en_US.utf8 in my .bashrc so since the text is in Dutch this happens before the .bashrc is executed. It basically translates to "id: unable to find name for group ID 1049089". When I start my vpn and re-open mintty the error doesn't show up anymore, even if I disconnect the vpn again. After rebooting the error message occurs again. The reason for the message seems obvious. The process can't lookup the information. But it can be confusing to users to see an error at startup. Is it error useful to the user? Can I suppress this message? Regards, Frank -- 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: Maintainer for git?
2014-02-21 1:18 GMT+01:00 Adam Dinwoodie: >> - Install git-cvs and the assorted dependencies mentioned in its >> setup.hint, and verify you can clone the Cygwin CVS repository. I've >> not managed to do this without hitting errors, but I suspect that's >> because I'm using the tool incorrectly. > > I've tried this. I have `git cvsimport` seemingly working on the > current Git 1.7.9 build, while my build reports the following SHA1 > error: Probably not going to solve this issue (I can't anything about CVS in the changelog), but you noticed that 1.9.0 had been released recently? Regards, Frank -- 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: Testers needed: New passwd/group handling in Cygwin
2014-02-15 13:52 GMT+01:00 Corinna Vinschen: >> Just tested and copied .bashrc to .profile and that solved the problem. > > Good, so it was really just a shell thingy. > >> I vote[1] for /bin/bash being the default shell. > > Done in CVS. Just downloaded the 2014-02-18 snapshot, deleted that .profile and things works as expected! Regards, Frank -- 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: Testers needed: New passwd/group handling in Cygwin
2014-02-14 11:48 GMT+01:00 Corinna Vinschen: > Oh, hang on. I'm a tcsh gal, so I set /bin/tcsh in my AD domain entry. > However, the default is *not* /bin/bash, but /bin/sh at the moment. I'm > a bit fuzzy on bash, but does bash read the .bachrc file only if it's > called bash and not if it's called sh? What happens if you symlink > your .bashrc to .profile (Not that I suggest this as the ultimate > solution, this is just for testing)? Just tested and copied .bashrc to .profile and that solved the problem. I vote[1] for /bin/bash being the default shell. Regards, Frank [1] not that there is any voting going on ;-) -- 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: Testers needed: New passwd/group handling in Cygwin
2014-02-13 15:38 GMT+01:00 Corinna Vinschen: > This is a pretty intrusive change, in need of some serious testing, so > I'd like to ask for volunteers. The latest 2014-02-13 snapshot from > http://cygwin.com/snapshots/ contains the changes, including the latest > bugfix. I've installed that snapshot on my work laptop, part of AD domain. I moved passwd and group out of the way and noticed my .bashrc is not executed. With 1.7.28: Frank@PC205 ~ $ uname -a CYGWIN_NT-6.1-WOW64 PC205 1.7.28(0.271/5/3) 2014-02-09 21:06 i686 Cygwin Frank@PC205 ~ $ ls -l total 86 -rw--- 1 Frank Domeingebruikers 6759 2014-02-14 09:30 .bash_history -rwxr-xr-x 1 Frank Domeingebruikers 1150 2010-11-17 18:58 .bash_profile* -rwxr-xr-x 1 Frank Domeingebruikers 3814 2013-10-18 12:02 .bashrc* With snapshot without passwd/group: Frank@PC205 ~ $ uname -a CYGWIN_NT-6.1-WOW64 PC205 1.7.29s(0.271/5/3) 20140213 14:06:26 i686 Cygwin Frank@PC205 ~ $ ls -l totaal 19 -rwxr-xr-x 1 Frank Domeingebruikers 98 16 mei 2012 mail-ek.sh -rw-r--r-- 1 Frank Domeingebruikers 811 16 mei 2012 mail-ek.txt -rwxr-xr-x 1 Frank Domeingebruikers 332 12 mei 2013 makeepub.sh drwxrwxrwt+ 1 +Administrators Domeingebruikers 0 24 okt 15:22 python drwxrwxrwt+ 1 +Administrators Domeingebruikers 0 13 feb 17:05 rsync drwxr-xr-x+ 1 Frank Domeingebruikers 0 13 feb 16:44 shutdown-package -rwxr-xr-x 1 Frank Domeingebruikers 38 13 feb 13:57 test.sh Most noticeable difference between the two are in the dates of the files (The months are in Dutch, and not in "long-iso") and not showing the dot-files. Among others, I have set an export LANG=en_US and an alias for "ls" in my bashrc for that. Reverting to 1.7.28 (with passwd/group) solved the problem. Regards, Frank -- 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: Could not resolve hostname
2014-02-14 9:00 GMT+01:00 Tomas Jankovic: > $ cat ~/.ssh/config > Host Example > hotname 127.0.0.1 No ssh expert, but if "hotname" is really in your config file, I would try to add an "s". Regards, Frank -- 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: How big are your /etc/passwd and /etc/group files?
2014-01-31 Corinna Vinschen: > Is anybody here who's using /etc/passwd and/or group files > of more than 16K in size? We don't go over 16K. On our server 101 rows result in 12k in /etc/passwd. Doing the basic math I would say anyone in a AD-environment with over ~135 rows is likely to get over 16K. Regards, Frank -- Problem reports: http://cygwin.com/problems.html FAQ: http://cygwin.com/faq/ Documentation: http://cygwin.com/docs.html Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple
Re: [ANNOUNCEMENT] Updated: vim-7.3.1152-1
2013/12/9 Björn Kautler: > Again, what I talk about is NOT an issue of vi vs. vim. > What I talk about is a breaking change in vim that was introduced > while doing a change for vi. > But it is NOT an issue of vi vs. vim. That patch was introduced when people started to complain that they got errors about commands not recognized in their vimrc. The root cause of this was obviously the whole vi != vim thing. I always use ~/.vimrc so I never ran into your problem. Regards, Frank -- Problem reports: http://cygwin.com/problems.html FAQ: http://cygwin.com/faq/ Documentation: http://cygwin.com/docs.html Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple
Re: [ANNOUNCEMENT] Updated: vim-7.3.1152-1
2013/12/9 Corinna Vinschen: > The new vim layout closely reflects the Fedora packaging. It has a > minimal vi in the vim-minimal package and a full-featured vim in the > vim-enhanced package. I'm using a vi -> vim alias on Fedora for ages. That explains why Yaakov did this. I assume Yaakov is a Fedora user. As a long time vi user (>25 years) and a Debian-based Linux user (Debian uses alternatives) I am used to type "vi", so I added the alias. But on our new server my colleague had to add the alias the other way around because there we have only vim-minimal installed and he is used to type "vim". So we always need an alias ;-) Regards, Frank -- Problem reports: http://cygwin.com/problems.html FAQ: http://cygwin.com/faq/ Documentation: http://cygwin.com/docs.html Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple
Re: [ANNOUNCEMENT] Updated: vim-7.3.1152-1
2013/12/9 Björn Kautler: > I don't have a problem with being mean. > Everyone makes mistakes. > I just wonder that it gets broken silently without obvious (to me) reason > and a question regarding it and with two proposed solutions just stays > ignored while it would be very easy to fix. To me, the best way to fix these problems is simple: start using alternatives again just like before vim-7.3.943-1. It makes everybody happy. You don't need to know if just vim-minimal or the full vim is installed. And whether you are used to typing "vi" or "vim", both commands start the best available version of vim. I don't understand why it was removed anyway. I brought up the question before and never got an answer. Regards, Frank -- Problem reports: http://cygwin.com/problems.html FAQ: http://cygwin.com/faq/ Documentation: http://cygwin.com/docs.html Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple
Re: [ANNOUNCEMENT] Updated: vim-7.3.1152-1
2013/12/7 Björn Kautler: > And it is ok and accepted that such a patch breaks the functionality? Apparently that depends on the maintainer. One maintainer does his best not to break existing installations: http://cygwin.com/ml/cygwin/2013-12/msg00059.html And another introduces a new version http://cygwin.com/ml/cygwin/2013-05/msg00163.html that breaks existing installations (see last line of announcement: removed alternatives) leaving people wonder why their vim doesn't work as expected (search the archives back in May and June). So cgf was right: http://cygwin.com/acronyms/#WJM Regards, Frank -- Problem reports: http://cygwin.com/problems.html FAQ: http://cygwin.com/faq/ Documentation: http://cygwin.com/docs.html Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple
Re: [ANNOUNCEMENT] Updated: inetutils-1.9.1-1; NEW: inetutils-server-1.9.1-1
2013/11/15 Charles Wilson: > CHANGES (since 1.7-2) > > o Updated to latest upstream release > o Rely on cygport to autogenerate setup.hints > o Split package into client and server components. I just tried to install the clients package and got this notification: inetutils-server(1.9.1-1) Common networking clients and servers (servers) Required by: inetutils Why does the "clients" package require the "servers" package? Regards, Frank -- 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: Found out why vim/vundle didn't work
2013/10/14 Andrey Repin: >> The "vim" command is a different "vim" than the "vi" command. Both are >> "vim", but come from different vim packages. In Linux and other *nix >> systems, vi is symbolically linked to vim, but not in this case. > > It is _commonly_ linked to vim, but that really only because most of the > distros you've worked with have full version of vim installed by default. > Cygwin offers vim (full) and vim-minimal packages. No! All distributions I have worked install a minimal version of vim by default as well. And I always manually upgrade to the full version. But all those distributions use alternative to solve the naming problem. Cygwin "vim" used to use alternatives as well and vi == vim. But when vim-minimal was introduced - and alternatives would be *really* useful - Yaakov decided to stop using alternatives for some reason, and now vi != vim. > If you intend to use full one, I suggest you remove vim-minimal and make a > familiar symlink for vi. vim-minimal is in Base. I think it will return every time you run setup. Regards, Frank -- 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: mt and tar fail on LTO-5 drives
2013/8/20 Corinna Vinschen: > This bug is present since 2004 and nobody noticed it. I guess that > means there aren't many people out there actually partitioning their > tape drives... FYI: we use cygwin tar on a daily base to backup one server to LTO2-tapes, but I have never partitioned a tape. Wasn't even aware it could be done. Regards, Frank -- 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: Updated Git build
2013/6/19 Adam Dinwoodie: > I'm not sure who the current maintainer is, or how to find out, This is the list of all packages and their maintainers. http://cygwin.com/cygwin-pkg-maint Not sure where to find a link to this on the cygwin site though. Regards, Frank -- 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: vim-minimal annoyance
2013/6/18 Csaba Raduly: >> If I have the full-featured vim installed, then I expect vi == >> full_featured_vim. This is how it has always been. >> >> I guess I'll just have to resign myself to creating an alias (vi=vim) on >> every install... > > Maybe there should be a "vi-as-vim" package which contains nothing but > the vi->vim symlink. IMHO the real solution would be using alternatives again. I still don't get why Yaakov stopped using it when it was really needed. Regards, Frank -- 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: vim-minimal annoyance
2013/6/17 Shaun Fielder: > We're so used to vi === vim [fully featured] on Cygwin. At the very least - > when the full "vim" package is installed 'vi' should use it. > At the moment, I'm having to get everyone here to uninstall vim-minimal and > manually setup a sym-link (or alias) to get back to the behaviour they've > always had. I have typed "vi" to start the editor for over 25 years now, so it annoys me as well. But does uninstalling vim-minimal help? It is in Base. I guess it keeps coming back. This all happened when vim-minimal was introduced and at the same moment Yaakov stopped using alternatives: http://cygwin.com/ml/cygwin/2013-05/msg00163.html The workaround he suggest is an alias and he created a patch to have vim-minimal use virc-files. He is looking into it a bit further. http://cygwin.com/ml/cygwin/2013-06/msg00273.html Regards, Frank -- Problem reports: http://cygwin.com/problems.html FAQ: http://cygwin.com/faq/ Documentation: http://cygwin.com/docs.html Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple
Re: [ANNOUNCEMENT] Updated: vim-7.3.1152-1
2013/6/11 Yaakov (Cygwin/X): > This is an update to last week's upstream patchset, with the following > packaging changes: > > * The 'vi' binary now uses ~/.virc and /etc/virc instead of vimrc to avoid > errors with configuration options not supported by 'vi'. > > * gvim on x86_64 uses the GTK+ interface. Any reason why you stopped using alternatives? http://cygwin.com/ml/cygwin-apps/2013-05/msg00068.html It was removed when it was really needed with the introduction of vim-minimal. Especially when vim-minimal was added to Base. It solves the vi != vim problem: http://cygwin.com/ml/cygwin-apps/2013-05/msg00068.html Regards, Frank -- 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: ctrl-c to windows program causes mintty to hang [1.7.20 / win7]
2013/6/9 Andrey Repin: > 3. Now, if you Ctrl+C, the console hangs. > If you let it sit down and think a bit, the iterrupt will be delivered to ping > and it get out of the lockup. > > Going to grab a snapshot and see if it affect anything. I ran into the same problem today, grabbed the latest snapshot (8-Jun) and that fixes the problem. Regards, Frank -- 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: VI problem with latest update
2013/6/9 Corinna Vinschen: > So vi complains about extended vim features in ~/.vimrc. The workaround > is to have a shell alias vi->vim or a matching symlink in a bin directory > preceeding /usr/bin in $PATH. I suggested a proper solution, but there was no response yet: http://cygwin.com/ml/cygwin-apps/2013-05/msg00068.html Regards, Frank -- 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
[ANNOUNCEMENT] Updated: shutdown 1.10-1
A new version of the Cygwin shutdown 1.10-1 has been released and can be found at a server near you. BACKWARD COMPATIBILITY NOTE === Cygwin shutdown gives a POSIX/Linux-like shutdown experience and tries to mimic the common Linux shutdown command line options as much as possible. Therefore the short option for --hibernate has been changed from -h to -b and -h is now the short for --halt. FULL CHANGELOG (from shutdown-1.9-1) * Changed the short option for hibernate from -h to -b. * Added -h, --halt as additional option for shutdown and -c, --cancel as additional option for abort. * Updated shutdown.8 man pages to reflect these changes. * Fixed typo: changed text InitateSystemShutdown to InitiateSystemShutdownEx in the two usage() functions in shutdown.c and in shutdown.8 and reboot.8 Regards, Frank *** CYGWIN-ANNOUNCE UNSUBSCRIBE INFO *** If you want to unsubscribe from the cygwin-announce mailing list, look at the "List-Unsubscribe: " tag in the email header of this message. Send email to the address specified there. It will be in the format: cygwin-announce-unsubscribe-you=yourdomain@cygwin.com If you need more information on unsubscribing, start reading here: http://sourceware.org/lists.html#unsubscribe-simple Please read *all* of the information on unsubscribing that is available starting at this URL. -- 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: Patch for shutdown
2013/5/22 Corinna Vinschen: > After that, checking out the project is done using > > $ cvs -d :ext:@sourceware.org:/cvs/cygwin-apps co shutdown The code is in CVS. Since this is my first package and it uses the CVS I have a question about the next steps. If I understand things correctly, these are the steps needed: - add tag "rel1-10" to CVS - use cygport to generate the bin packages - "cygport --32 shutdown.cygport download prep compile package" - "cygport --64 shutdown.cygport download prep compile package" - I assume these commands will also generate a src package >From there I follow the normal steps (ITA, RFU and announcement) as described on http://cygwin.com/setup.html Did I miss anything? Regards, Frank -- 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: Patch for shutdown
2013/5/21 Corinna Vinschen: > Uhm... I would prefer if we had the cygwin-specific tools in a single > repository, if it's not asked too much. I'm sure we could add git > access as well, if it's not already available. I can continue to use CVS, no problem. No need to use git, just for the sake of git ;-) But I guess then I'll need write access or you must still review and commit the patches I write. Regards, Frank -- 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: Patch for shutdown
2013/5/21 Corinna Vinschen: > I'm a bit reluctant as of the backward compatibility breakage. What > if somebody uses shutdown in a script? You know, starting a backup > in the evening and the last action of the script is to hibernate the > machine or something like that... That's why I sent my email in March in the first place. But I really think having -h for halt is better for a POSIX/Linux-like shutdown. And "shutdown -h now" will now halt the machine instead of hibernate. Although I understand they definitely are not the same, it won't leave the machine turned on. It will be in a "form of off". A proper announcement is required. The backward compatibility breakage was the reason I thought about 2.x vs 1.x. > Say, do you want to take over shutdown > maintainership? It's an easy enough package to start with, it > builds fine on 32 and 64 bit, and you get the cygport configuration > "for free". What do you say? Anything "for free" must be good ;-) I see the cygport file is in src archive. It has been very long since I have played with cygport. And I have not looked at cygwin64, although I use Win7-64. I had no real need for cygwin64 so far, so I wanted to wait for it to be officially released. I just ran the setup64.exe found at a nearby mirror, installed cygport and gcc/g++ and shutdown compiles under 32 and 64 bit. So back to the question... why not take over? I will read http://cygwin.com/setup.html thoroughly, create the new packages and send the ITA any time soon. You keep the sources in CVS right now. But when I take over, I assume it is ok I put them at my github. Regards, Frank -- 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: Patch for shutdown
2013/5/20 Jeffrey Altman: > I believe it is very important that the Cygwin shutdown not alter the > meaning of command line parameters such that they are different from the > Windows native version. The various options are already too confusing > to remember. Typing the right option value into wrong shell should not > result in the wrong behavior if we can help it. But why do you install the cygwin shutdown package when you want to use the native windows shutdown command line options? The windows shutdown.exe work just fine when it is run from cygwin (mintty, rxvt, ssh). When you de-install the cygwin package, you can use the windows shutdown command. The cygwin shutdown tries to give a POSIX/Linux-like shutdown experience and therefore should mimic the common Linux command line options as good as possible. That's the reason I install the shutdown package. In cygwin I type "ls", "less", etc. It feels like Linux, so I want the shutdown to feel like Linux as well and use -h for halt just like on any real Linux system. And remember that the cygwin shutdown has long options and the "halt", "reboot" and "hibernate" commands. Regards, Frank -- 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
Patch for shutdown
Hi Corinna, Since nobody made real objections about changing the short flag for hibernate from -h to -b to make room for -h for halt [1], I created a patch to change the shutdown program. The patch was created back in March, but with all your work being done on cygwin64, your holiday and myself being very busy with life it was held back. There were no change to the shutdown CVS since then so here is that patch, including a changelog. Note that I didn't change the programs version number in this patch. I don't know if changing an existing option would require/justify to change the version from 1.9 to 2.0 instead of simply to 1.10? Regards, Frank [1] http://cygwin.com/ml/cygwin/2013-03/msg00354.html CHANGELOG Description: Binary data shutdown.patch 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: vim-7.3.943-1 missing command 'let g:colors_name = "elflord"' found in vim-common-7.3.943-1
2013/5/17 Gary Johnson wrote: > This is not a bug. See Yaakov's announcement in the list on May 12, > "[ANNOUNCEMENT] Updated: vim-7.3.943-1". He explains that the > packaging scheme has been changed and that /usr/bin/vi is now Vim > compiled with the "small" feature set. The "small" feature set does > not include the +syntax or +eval feature and does not support either > the :syntax or :let command. > > If you want to use those commands, run vim and not vi, or alias vi > to vim. If you want to use the "small" vi, you'll have to adjust > your ~/.vimrc to avoid using commands that are not supported. See The reason that it occurs now is that vim-minimal has been added to Base recently. That results in the situation you describe. It is discussed on the cygwin-apps mailing list as well [1]. It probably can be fixed by using alternatives, but Yaakov is AFK so he has not been able to respond yet. Regards, Frank [1] http://cygwin.com/ml/cygwin-apps/2013-05/msg00045.html and follow ups -- 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: docbook2pdf errors
2013/4/12 Markus Hoenicka: > In order to set up your XML toolchain, please peruse the excellent > instructions here: > > http://www.sagehill.net/docbookxsl/ I will leave docbook2pdf for what it is and dig into the XSL stuff. Many new stuff to learn ;-) Still a bit surprised though that docbook2pdf (and docbook2html as well) give those error out of the box. Regards, Frank -- 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: docbook2pdf errors
2013/4/12 Markus Hoenicka: > I have never used the docbook2pdf tool, but these messages indicate that it > attempts to transform an XML document using Jade and the DocBook DSSSL > stylesheets. While you may be able to get this to work with a little effort, > I'd recommend to use an XSLT-based toolchain (e.g. xslt and fop) and the > DocBook XSL stylesheets for XML documents. I am a docbook newbie so I just wanted to try docbook2pdf to see what the generated pdf looks like. Regards, Frank -- 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: docbook2pdf errors
2013/4/12 Paul Allen: >> "1D6C2" is not a character number in the document character set > > I'd put money on that being unicode character "mathematical bold small > alpha". What windoze code page are you using? One that can handle > utf-8 or not. I created my book.xml with a simple copy-paste. I never set any code page. vim opens it correctly, notepad++ says it is "ANSI". There isn't any need to set any code page, because only ascii characters are used. The file "isogrk4.ent" contains 40 lines (so all lines in the file give the error) like this: Regards, Frank -- 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
docbook2pdf errors
Hi, I want convert some documention I wrote to DocBook, but first I want to have my environment setup correctly. So I installed all the docbook packages and created a book.xml from the sample at http://www.docbook.org/tdg/en/html/book.html and did some minor changes. This document validates properly with these commands: $ export SGML_CATALOG_FILES=/etc/xml/catalog $ xmllint --valid --noout --catalogs book.xml $ But when I try to convert it to a pdf I get a lot of errors: $ docbook2pdf book.xml Using catalogs: /etc/sgml/xml-docbook-4.5.cat Using stylesheet: /usr/share/sgml/docbook/utils-0.6.14/docbook-utils.dsl#print Working on: /cygdrive/c/Users/Frank/Dropbox/DocBook/book.xml jade:/usr/share/sgml/docbook/xml-dtd-4.5/ent/isogrk4.ent:42:30:E: "1D6C2" is not a character number in the document character set jade:/usr/share/sgml/docbook/xml-dtd-4.5/ent/isogrk4.ent:43:30:E: "1D6C3" is not a character number in the document character set jade:/usr/share/sgml/docbook/xml-dtd-4.5/ent/isogrk4.ent:44:30:E: "1D6D8" is not a character number in the document character set Those "not a character number in the document character set" lines are shown 40 times with different 1D6xx characters. Did I do something wrong in this very basic setup, or is there something wrong with a docbook related package? Regards, Frank http://www.oasis-open.org/docbook/xml/4.5/docbookx.dtd";> Example Book Example http://creativecommons.org/licenses/by-nc-sa/3.0/";>CC-BY-NC-SA FrankFesevur This book is dedicated to you. Foreword Some content is always required. A Chapter Content is required in chapters too. Optional Appendix Appendixes are optional. -- 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: Fwd: reboot command behaves different on Linux
2013/3/25 Earnie Boyd: >> I have given it a thought over the weekend and since the -H conflicts >> with -H of the Linux shutdown commands, I think I prefer the -b as >> short for hibernate. > > To me -b sounds like 'b;inary how about -s for 's'leep since sleep is > synonymous with hibernate. -s is already used for --shutdown. I like to keep it there because of the compatibilty with the Windows shutdown.exe. And what does sleep mean, hibernate to disk or to RAM? There is a lot of confusing about the terms hibernate. sleep, suspend and standy. If I understand it correctly, hibernate is to disk and the others are to RAM. But I can be wrong. Regards, Frank -- 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: Fwd: reboot command behaves different on Linux
2013/3/23 David T-G: > % This would still conflict with the -H of the ones above, but I have no > % problem with it. Anyone against changing hibernate to -H? > > What about 'b' for hi'b'ernate? That was my original suggestion, but Anthony liked the -H better. I have given it a thought over the weekend and since the -H conflicts with -H of the Linux shutdown commands, I think I prefer the -b as short for hibernate. Regards, Frank -- 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: Fwd: reboot command behaves different on Linux
2013/3/23 Anthony Geoghegan: > I thought about it for a while myself before posting but I concluded your > choice was a good one: the usefulness of -h for hibernate probably > outweighed the benefits of retaining compatibility with a more traditional > (BSD) Unix shutdown. I checked to see if POSIX had anything specified but > it's not concerned with the shutdown command. It seems there is not such thing as a *general* shutdown command. "Every" distribution has its own. Just picked three: http://linuxmanpages.net/manpages/fedora18/man8/shutdown.8.html http://manpages.ubuntu.com/manpages/precise/man8/shutdown.8.html http://manpages.debian.net/cgi-bin/man.cgi?query=shutdown&apropos=0&sektion=8&manpath=Debian+6.0+squeeze&format=html&locale=en Although they all agree on -r -h -H -P -k and -c. Also noticed that the Fedora shutdown doesn't require the time option. It defaults to 1 minute. > Having thought about it bit more, I'd like to suggest an upper case -H as > the option for hibernate. This would still conflict with the -H of the ones above, but I have no problem with it. Anyone against changing hibernate to -H? Regards, Frank -- 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: Fwd: reboot command behaves different on Linux
2013/3/22 Thorsten Kampe: >> > And does anybody ever use that reason thing on the windows shutdown? >> I know it is used by server versions of Windows. When you request >> shutdown/reboot you must enter a reason, and it is logged in system logs >> (don't know exactly where, i guess you can find this in Event viewer). >> Looks like it's ignored by desktop versions (XP/7/home/whatever). > > This is called the shutdown tracker and it's on by default on server > systems (non core). Most people simply disable it. I know that, but I was wondering if anybody ever really uses this feature from the command line. And to be more specific, should the cygwin shutdown have an command line option to give the reason for shutdown. Now it is always "Other (Planned)". Regards, Frank -- 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: Fwd: reboot command behaves different on Linux
2013/3/21 Anthony Geoghegan: > Nice work, Frank. I took a quick look at the man pages. The only improvement > I'd suggest is that the first sentence of the Description for reboot.8 would > read better by adding "the user" like so: > > Change > "These programs allow to reboot, halt, poweroff, hibernate or suspend the > system." > to > "These programs allow the user to reboot, halt, poweroff, hibernate or > suspend the system." Sounds good. I guess Corinna will fix this in the CVS for a next version. > I also noticed that "shutdown -h" acts differently on Linux. :) Yes, that bugs my for quite some time too, is -h for halt or hibernate? Now the -s is the same as the Windows shutdown.exe. The changes are really straight forward. -b could be the new short option for hibernate, doesn't interfere with the main linux shutdown options or the windows shutdown. Leaving -s as it is for backward/windows compatibility reasons and adding -h, --halt for shutdown and -P, --poweroff. But then, having three options that actually don't do anything, just for the sake of compatibility? EWX_POWEROFF is the default action already. That's why I left those shutdown options as they are. But I gladly write the patch if nobody has objections against changing -h. I'm also considering adding possibility to customize the shutdown message: shutdown -rf 22:00 "Rebooting because of Windows Updates". Who knows... And does anybody ever use that reason thing on the windows shutdown? Regards, Frank -- 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: Fwd: reboot command behaves different on Linux
2013/3/20 Corinna Vinschen: > After applying your changes you can then generate your patch via > `cvs diff -up', ideally combined with a description of your changes. I have attached a tarball with the patch against the cvs. It also includes a changelog. > I like the idea to get man pages, btw... They are in the tarball as well. As said, they are basic man pages, nothing fancy. Please know that English is not my native tongue. Regards, Frank shutdown.tar.gz Description: GNU Zip compressed 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: Fwd: reboot command behaves different on Linux
2013/3/20 Larry Hall (Cygwin): > Did you get a bounce message? Did it describe the problem? Nope, never saw a bounce. > Assuming there was no bounce, I'd suggest trying again. The Cygwin site was > getting an upgrade over the last few days and was less "capable" than usual > as a result. Here is the attached file again. Regards, Frank shutdown.c.gz Description: GNU Zip compressed 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
Fwd: reboot command behaves different on Linux
The message below never made it through to the list, according to <http://cygwin.com/ml/cygwin/2013-03/>, probably because of the attached file. What is the best way to share the code I've written for the shutdown package??? Regards, Frank -- Forwarded message -- From: Frank Fesevur Date: 2013/3/19 14:02 Subject: Re: reboot command behaves different on Linux To: "x...@.zzz" 2013/3/19 marco atzeri: > reboot on cygwin is just a link to shutdown I know. But the symlinks "reboot", "hibernate" and "suspend" don't react as I would have expected. I have attached a patched/rewritten version of the shutdown command. It also adds support for a symlink named "halt" and "poweroff". It is up to Corinna if she likes my version or not. $ ./halt --help Usage: halt [OPTION]... Bring the system down. -f, --force Forces the execution. -x, --exitex Use ExitWindowsEx rather than InitateSystemShutdown. --help Display this help and exit. --versionOutput version information and exit. If wanted I'm willing to create basic shutdown.8 and reboot.8 man pages. Regards, Frank -- 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
reboot command behaves different on Linux
Hi, I noticed that the cygwin reboot works different then the reboot command on my (debian based) Linux machines. The cygwin reboot requires a time on the command line while the reboot on Linux doesn't accept a time and reboots immediately. Is there a reason why this is? I can create a patch, if wanted/needed. Regards, Frank -- 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: Howto compile package
2013/2/17 Matthias Meyer: > I would like to patch and compile rsync. Why do you want to patch rsync? Is it related my question of some days ago? http://cygwin.com/ml/cygwin/2013-02/msg00021.html Regards, Frank -- 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
Rsync errors
Hi, A while ago we upgraded our Ubuntu server to 12.04LTS and it now runs rsync 3.0.9. We use rsnapshot (and thus rsync) to backup a part of our Windows server. There is a default cygwin rsyncd running on that Windows server (not cwRsync). After this upgrade we always get a lot of these errors in the rsync log un the Ubuntu server: uid 4294967295 (-1) is impossible to set on "/var/backup/daily.0/server1/d/Software/ADMIN" There is > 200kb of these lines, mentioning both files and directories. It doesn't affect the backup itself. But because of these lines any real error become sort of invisible. rsync now always returns an error. I did a google search and found that there are more people with these error occur, and often cygwin rsyncd is in their setup. I tried the "fake super" suggestion mentioned in http://digitaldj.net/2011/04/07/rsync-3-0-8-windows-and-chown/ but that didn't help. The fstab solution to disable ACL mentioned in the comments didn't help either (I did restart the rsyncd service). Does anybody have a clue how to solve this problem? Regards, Frank /etc/rsyncd.conf: id = 0 gid = 0 use chroot = yes max connections = 5 fake super = yes syslog facility = local3 pid file = /var/run/rsyncd.pid secrets file = /etc/rsyncd.secrets [backup-d] path = /cygdrive/d/ read only = yes dont compress = *.zip *.gz *.rar *.7z *.jpg *.gif *.png *.JPG exclude = Thumbs.db .DS_Store .TemporaryItems .apdisk outgoing chmod = D775,F664 -- Problem reports: http://cygwin.com/problems.html FAQ: http://cygwin.com/faq/ Documentation: http://cygwin.com/docs.html Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple
Re: [ANNOUNCEMENT] New package: cloc 1.55-1 -- Statistics utility to count lines of code.
2012/2/26 Jari Aalto: > > PACKAGE DESCRIPTION > === > > Homepage: http://freshmeat.net/projects/cloc > License : GPL > > Count physical lines of source code in the given files (may be > archives such as compressed tarballs or zip files) and/or > recursively below the given directories. I just installed cloc and tried in on a small project I do, but I can't get it to work: Frank@PC205 /cygdrive/c/Source $ cloc NppSnippets/ Can't open perl script "perl": No such file or directory I do have Perl installed: Frank@PC205 /cygdrive/c/Source $ type perl perl is gehasht (/usr/bin/perl) Did I miss something or is there an error in the package? Regards, Frank -- 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: cygrunsrv doesn't stop service during reboot
2012/2/21 Frank Fesevur: > I will update the cygrunsrv tomorrow and reboot that server tomorrow > evening and let you know. Tested it and it works as expected with the preshutdown flag. Thanks again for the fix. Regards, Frank -- 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: cygrunsrv doesn't stop service during reboot
2012/2/21 Corinna Vinschen: > I tested that now and found that the preshutdown control message was > never sent to cygrunsrv's service handler function. > > [snip] > > I just uploaded a new cygrunsrv version with this fix. Whow!!! That is a quick fix. Thanks a lot. Very much appreciated! I will update the cygrunsrv tomorrow and reboot that server tomorrow evening and let you know. Regards, Frank -- 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: cygrunsrv doesn't stop service during reboot
2012/2/20 Corinna Vinschen: > Something else occured to me. You didn't specify a pidfile on the > cygrunsrv -I command line, so rsyncd will be run by cygrunsrv without > a pidfile. So, where is the pidfile coming from? Does rsync create > it by itself in daemon mode? I just tried this and the answer is no. > Again, from where do you get the pidfile in this scenario? Took a while to find that one, but the pid file is specified in the rsyncd.conf Regards, Frank -- 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: cygrunsrv doesn't stop service during reboot
2012/2/20 Corinna Vinschen: > Did you check your log? Do you see any of these messages? If not, > I assume that the shutdown kills the service process so fast that it > has no chance for the cleanup. Which is kind of weird in case of > preshutdown, given that you're supposed to have 3 minutes, at least > by default... I check the System log and found this error-line: The CYGWIN rsyncd service did not shut down properly after receiving a preshutdown control. > Interesting. Given that 2003 doesn't support the control message > SERVICE_CONTROL_PRESHUTDOWN, it's kind of strange that it works on 2003 > but not on 2008R2. Did you try to reinstall your rsyncd service without > the -O option, so that the service acts on the SERVICE_CONTROL_SHUTDOWN > message instead? Given the error above, I will try to install the service without the -O. Should I replace it with a -o or is that default behavior? The cygrunsrv --help is a bit confusing to me. Another thing that I thought of was that maybe the -f of the shutdown command is affecting the process. I will try to test that. But since this is a production server, I have to wait for the evening to be able to reboot that server. Regards, Frank -- 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
cygrunsrv doesn't stop service during reboot
Hi, I have a annoying problem with rsyncd running as a service using cygsunsrv. When I reboot the server running Win2008R2 the service is not properly stopped. Therefore the .pid file stays in /var/run and when the server starts again, the rsync daemon not started because it finds a .pid file. When I manually stop the service (net stop rsyncd) it works as expected. We don't have this problem on our Win2003 server. The cygrunsrv command is the same on both servers: cygrunsrv -I rsyncd -d "CYGWIN rsyncd" -f "Rsync file transfer daemon" -p /bin/rsync.exe -a "--daemon --no-detach" -O The reboot is done with a schedule task running the windows native shutdown command: "shutdown -r -f -t 0" Do I overlook something? Are other people having similar problem with cygrunsrv with win2008R2? Do you need more information? If so, how can I use cygcheck with a service? Regards, Frank -- 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: Best way to backup 1.5 to go to 1.7
2010/1/21 Brian Keener: > I want to upgrade to 1.7 but would like to get a backup of the full 1.5 > install before hand. I know in the past just doing copies some files > didn't or couldn't get copied. Also in the unix world seems as though > I recall tar and cpio have difference in terms of what they will and > won't backup. > > What the best way to get a good copy of my 1.5 in case I need/want to > get it back. I have made a backup of 1.5 by 7-Zipping the entire directory and also backup the "mount v2" tree of "Cygnus Solutions" in the registry. I have had problems upgrading to 1.7 on one pc and could successfully restore my 1.5 installation. Regards, Frank -- 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: 1.7.1 hangs on 000-cygwin-post-install.sh
2010/1/15 Corinna Vinschen: > On Jan 15 11:03, Frank Fesevur wrote: >> 2010/1/14 David Sherrets: >> > I have a newer Dell machine. The hardware encryption API DLL >> > (wxvault.dll) interferes with many Cygwin packages. >> > This can be fixed stopping this DLL from loading at startup. >> > (use Autoruns from Microsoft Sysinternals at >> > http://www.microsoft.com/technet/sysinternals) >> >> Maybe it is an idea to put this on the BLODA list? > > It's already in the list: > > http://cygwin.com/faq/faq.using.html#faq.using.bloda I don't have the mentioned fingerprint reader software, so therefore I overlooked this. I have Embassy Security Center also by Wave Systems Corp. This also uses this wxvault.dll. I would suggest to change this line to something like: Various programs by Wave Systems Corp using wxvault.dll, including Embassy Trust Suite and Embassy Security Center. Since I found this on all Dell workstations (not on servers) I have checked here at the office, maybe even add that it is pre-installed on many Dell systems. Regards, Frank -- 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: 1.7.1 hangs on 000-cygwin-post-install.sh
2010/1/14 David Sherrets: > I too experienced the same problem. > The fix for me was this... > > I have a newer Dell machine. The hardware encryption API DLL > (wxvault.dll) interferes with many Cygwin packages. > This can be fixed stopping this DLL from loading at startup. > (use Autoruns from Microsoft Sysinternals at > http://www.microsoft.com/technet/sysinternals) > > I can't take credit for this, as it was my co-workers in Sweden who > found the fix, but I though there are many here who might benefit! YES!!! A *BIG* thank you to your Swedish co-worker, and to you for telling here! This solved the problem for me as well. I have a Dell as well, my is almost three years old. That dll was on the AppInit tab and it was used by docmgr.exe that can be found as "Document Manager" on the Logon tab. I disabled them both and made a backup of my cygwin15 installation (including the mount keys in the registry). After all of this I restarted my Windows, run the setup and upgraded to 1.7 without any problem. Once again a big thank you! Maybe it is an idea to put this on the BLODA list? Regards, Frank -- 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: 1.7.1-1 Install freeze of Cygwin post install.sh
2009/12/28 Brian Wilson: > I have no choice but to cancel the install and retry; but it never completes > and always fails at the same point. Does anyone know what this means and how > to fix the problem? If it's something stupid I've done; please point out the > issue. I'm experiencing exactly the same problem on my laptop at work: http://www.mail-archive.com/cygwin@cygwin.com/msg103719.html As mentioned in that thread, I disabled everything that I could think of as BLODA but it still does not work. At home my pc upgraded without any problem. There is only one cygwin1.dll on my system and when I run cygcheck from a ash from a command prompt I get the same "couldn't allocate heap" error. Regards, Frank -- 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: setup 1.7.1 hangs on 000-cygwin-post-install.sh
2009/12/23 Charles Wilson: > I saw something similar a while back. I "fixed" it by doing the following: > > 1) launch an ash shell from a cmd window > 2) run rebaseall (google for more instructions on this). > 3) re-run setup (this will attempt again to run any uncompleted > postinstall scripts from the previous attempt). Didn't help either. I upgraded at home without any problem. I haven't got a clue how to get cygwin back on my system :-( Regards, Frank -- 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: setup 1.7.1 hangs on 000-cygwin-post-install.sh
2009/12/23 Corinna Vinschen : > http://cygwin.com/faq/faq.using.html#faq.using.bloda ? > > Personally I'm running MSFT Security Essentials with real-time protection > turned on on that machine and it works still as expected. No, I don't run any of the mentioned applications. I tried disabling Kasperky, without any luck. Tried closing all other application, still without luck. Regards, Frank -- 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: setup 1.7.1 hangs on 000-cygwin-post-install.sh
2009/12/23 Corinna Vinschen : > Works fine for me. You should examine the /var/log/setup.log and > /var/log/setup.log.full files if you can find any hint. Thanks for the reply. Here is the content of setup.log.postinstallXa05832. 5 [main] bash 2832 C:\Cygwin\bin\bash.exe: *** fatal error - couldn't allocate heap, Win32 error 487, base 0x6D, top 0x73, reserve_size 389120, allocsize 393216, page_const 4096 31 [main] bash 5568 child_info::sync: wait failed, pid 2832, Win32 error 0 50513 [main] bash 5568 fork: child -1 - died waiting for longjmp before initialization, retry 0, exit code 0x100, errno 11 5 [main] bash 3988 C:\Cygwin\bin\bash.exe: *** fatal error - couldn't allocate heap, Win32 error 487, base 0x6D, top 0x73, reserve_size 389120, allocsize 393216, page_const 4096 302192511 [main] bash 5568 child_info::sync: wait failed, pid 3988, Win32 error 0 302240495 [main] bash 5568 fork: child -1 - died waiting for longjmp before initialization, retry 0, exit code 0x100, errno 11 5 [main] bash 5940 C:\Cygwin\bin\bash.exe: *** fatal error - couldn't allocate heap, Win32 error 487, base 0x6D, top 0x73, reserve_size 389120, allocsize 393216, page_const 4096 605358747 [main] bash 5568 child_info::sync: wait failed, pid 5940, Win32 error 0 605407711 [main] bash 5568 fork: child -1 - died waiting for longjmp before initialization, retry 0, exit code 0x100, errno 11 5 [main] bash 992 C:\Cygwin\bin\bash.exe: *** fatal error - couldn't allocate heap, Win32 error 487, base 0x6D, top 0x73, reserve_size 389120, allocsize 393216, page_const 4096 910591220 [main] bash 5568 child_info::sync: wait failed, pid 992, Win32 error 0 910623935 [main] bash 5568 fork: child -1 - died waiting for longjmp before initialization, retry 0, exit code 0x100, errno 11 5 [main] bash 1796 C:\Cygwin\bin\bash.exe: *** fatal error - couldn't allocate heap, Win32 error 487, base 0x6D, top 0x73, reserve_size 389120, allocsize 393216, page_const 4096 Don't understand why there is a "couldn't allocate heap". The system run fine with more the 800mb memory available and not much applications running. I forgot the mention that I run Windows XP. Regards, Frank -- 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
